Add Gateway API version supportability matrix - #117520
Conversation
Document which Gateway API version OpenShift supports so users can plan deployments before enabling Gateway API with the Ingress Operator. Co-authored-by: Cursor <cursoragent@cursor.com>
|
Hi @atpatil-sketch. Thanks for your PR. I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with Regular contributors should join the org to skip this step. Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions 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. |
|
Ready for docs review. Note: the Gateway API version cell is currently a placeholder ( |
Document the OpenShift-to-Gateway-API version mapping so users can identify the supported Gateway API version for each release. Co-authored-by: Cursor <cursoragent@cursor.com>
|
Updated the supportability matrix with the approved OpenShift ↔ Gateway API version mapping (4.19–5.0). |
Keep the supportability table limited to the declared Gateway API version for each OpenShift release. Co-authored-by: Cursor <cursoragent@cursor.com>
Summary
Test plan
TBDGateway API version cell with the approved supportability data before mergeingress-gateway-apiassemblyMade with Cursor