Skip to content

docs: Add guidance preferring GRPCRoute for gRPC - #4513

Merged
k8s-ci-robot merged 1 commit into
kubernetes-sigs:mainfrom
kahirokunn:docs/grpcroute-intro-guidance
May 8, 2026
Merged

k8s-ci-robot merged 1 commit into
kubernetes-sigs:mainfrom
kahirokunn:docs/grpcroute-intro-guidance

Conversation

@kahirokunn

Copy link
Copy Markdown
Member

/kind documentation

What type of PR is this?
/kind documentation

What this PR does / why we need it:

  • Adds a short note at the top of the GRPCRoute documentation clarifying that if you know you’re working with gRPC, you should prefer using a GRPCRoute.
  • Notes that an HTTPRoute may be sufficient for basic routing/load balancing, but GRPCRoute makes intent clearer and can enable more gRPC-specific functionality (with a link to the detailed guidance section).

Which issue(s) this PR fixes:
None

Does this PR introduce a user-facing change?:
No

Added documentation guidance recommending GRPCRoute for gRPC traffic.

Signed-off-by: kahirokunn <okinakahiro@gmail.com>
@k8s-ci-robot k8s-ci-robot added release-note Denotes a PR that will be considered when it comes time to generate release notes. kind/documentation Categorizes issue or PR as related to documentation. labels Feb 7, 2026
@k8s-ci-robot k8s-ci-robot added size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Feb 7, 2026
@k8s-triage-robot

Copy link
Copy Markdown

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

  • Mark this PR as fresh with /remove-lifecycle stale
  • Close this PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 8, 2026
@kahirokunn

Copy link
Copy Markdown
Member Author

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 8, 2026
@youngnick

Copy link
Copy Markdown
Contributor

/approve
/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label May 8, 2026
@k8s-ci-robot

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kahirokunn, youngnick

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 8, 2026
@kahirokunn

Copy link
Copy Markdown
Member Author

Thanks for your review 😭

@k8s-ci-robot
k8s-ci-robot merged commit c433998 into kubernetes-sigs:main May 8, 2026
20 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/documentation Categorizes issue or PR as related to documentation. lgtm "Looks good to me", indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants