OCPBUGS-91952: Clarify GWAPI configuration requirements and correct example syntax - #117251
OCPBUGS-91952: Clarify GWAPI configuration requirements and correct example syntax#117251jab-rh wants to merge 1 commit into
Conversation
…xample syntax Port the enterprise-4.21 fix to main after the module rename: correct hostname wildcards, YAML indentation, and HTTPRoute apiVersion values. Co-authored-by: Cursor <cursoragent@cursor.com>
|
@jab-rh: This pull request references Jira Issue OCPBUGS-91952, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
|
🤖 Tue Aug 04 17:47:08 - Prow CI generated the docs preview: |
|
@jab-rh: all tests passed! Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
|
@rhamini3, this change didn't make it into our other branches, but it looks like it is valid for OCP 5 and 4.22 is well. Can you confirm? Thanks! |
yes this is valid for both releases |
Align assembly intro and path-based routing title with user tasks, drop an incorrect cluster-admin prerequisite, remove the RegularExpression implementation note, and stop listing re-encrypt TLS as routes-only.
mainafter the module rename (nw-ingress-gateway-api-deployment-topologies.adoc→gateway-api-deployment-topologies.adoc).*.example.com), broken YAML indentation (broken-bar characters), andHTTPRouteapiVersionvalues.Version(s): 4.20+ TBD
Issue:
https://redhat.atlassian.net/browse/OCPBUGS-87011
Link to docs preview:
QE review:
Additional information:
Refs #113967.