Improvement for k8s.io/docs/concepts/services-networking/gateway/

[TheMarkGx]

AllowedRoutes usage/example could be included

[k8s-ci-robot]

This issue is currently awaiting triage.

SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[lmktfy]

We should probably simplify https://k8s.io/docs/concepts/services-networking/gateway/ to make it clear that people should read the documentation for Gateway, at https://gateway-api.sigs.k8s.io/

---

If you're then thinking "let's merge https://gateway-api.sigs.k8s.io/ into the main documentation", it's a nice idea but unless a project manager steps forward to drive the change / KEP to completion, it isn't likely to happen.

[TheMarkGx]

By my interpretation (I am a CKA amateur), even the docs @ the gateway-api site lacked an easy to read description for demonstrating its use (AllowedRoutes, that is).

Is it possible one could say AllowedRoutes is common enough of a Field to justify including it on the k8s .io site?

Edit: To clarify a little, I’m not suggesting expanding the kubernetes.io page beyond its current level of detail, just sharing the thought that allowedRoutes might be foundational and common enough to be included alongside the minimal example under the Gateway section already. Might improve sharpness a bit at the overview level? Without it, even simple cross-namespace routing fails silently in practice.

A lot of blogs and training material highlight cross-namespace routing as one of Gateway API’s major new strengths, but since that feature is disabled by default, it ends up being surprisingly easy to miss.