Review KIC GWAPI docs for cross-namespace route references

[rainest]

Where is the problem?

Kong/kubernetes-ingress-controller#4142

What happened?

The Gateway API standard was previously ambiguous about or did not strictly enforce rules about Routes attaching to Gateways in another namespace. As of 0.7 (maybe a bit earlier, but whatever), the spec now enforces a requirement that a ReferenceGrant permit this access.

As the controller did not enforce this requirement as of 2.10, if we wrote docs using cross-namespace route->gateway references, those examples will break.

What did you expect to happen?

Prior to KIC 2.11, review docs for Routes that reference Gateways in another namespace. If any are found, either move the Route into the Gateway namespace or add a ReferenceGrant that allows the reference.

This is a documentation task for the Kubernetes team and should not require Docs team action.

Code of Conduct and Community Expectations

• I agree to follow this project's Code of Conduct
• I agree to abide by the Community Expectations

[rainest]

This was a misread of the spec. Route/Gateway cross-namespace association is handled via a separate allowedRoutes mechanism within Listener.