* source/gateway-api: Migrate Gateway and HTTPRoute from v1beta1 to v1
This migrates the Kubernetes API interactions for Gateway and HTTPRoute
objects from v1beta1 to v1.
The v1beta1 revert was originally made in PR #4610 (July 2024) because
GKE clusters were not yet serving v1 CRDs. That is no longer the case:
v1 Gateway and HTTPRoute have been available since Gateway API v1.0.0
(October 2023) and all major managed Kubernetes providers now serve them.
This change does NOT modify TLSRoute, TCPRoute, or UDPRoute, which
remain at v1alpha2. TLSRoute's migration to v1 depends on Gateway API
v1.5.0+ and is tracked separately in #6247.
* Updated Gateway API "Supported API Versions" section.
* Document minimum supported Gateway API CRD version
Co-authored-by: Michel Loiseleur <97035654+mloiseleur@users.noreply.github.com>
* Merge branch 'master' into gateway-api-v1
* Revised "Supported API Versions" Gateway API doc.
Incorporated review suggestions from @mloiseleur
* Removed extraneous empty links in import blocks
---------
Co-authored-by: Michel Loiseleur <97035654+mloiseleur@users.noreply.github.com>
Addresses #5901
Related: #4056
Add clear documentation on annotation placement for Gateway API sources
to prevent confusion about which annotations go on Gateway vs Route resources.
Changes:
- Add Gateway API Annotation Placement section to annotations.md
- Add Annotations section with examples to gateway-api.md
- Include Cloudflare and AWS provider examples
- Document common mistakes
Per review feedback, compressed annotations.md section to minimal size:
- Removed annotation placement matrix table
- Removed YAML examples
- Kept concise 2-line summary
- Kept link to comprehensive documentation
Co-authored-by: Claude <noreply@anthropic.com>
