Skip to content

OCPBUGS-91952: Clarify GWAPI configuration requirements and correct example syntax - #117251

Open
jab-rh wants to merge 1 commit into
openshift:mainfrom
jab-rh:OCPBUGS-91952
Open

OCPBUGS-91952: Clarify GWAPI configuration requirements and correct example syntax#117251
jab-rh wants to merge 1 commit into
openshift:mainfrom
jab-rh:OCPBUGS-91952

Conversation

@jab-rh

@jab-rh jab-rh commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

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.

  • Ports the enterprise-4.21 fix from cf93e21 to main after the module rename (nw-ingress-gateway-api-deployment-topologies.adocgateway-api-deployment-topologies.adoc).
  • Corrects Gateway hostname wildcards (*.example.com), broken YAML indentation (broken-bar characters), and HTTPRoute apiVersion values.

Version(s): 4.20+ TBD

Issue:

https://redhat.atlassian.net/browse/OCPBUGS-87011

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:

Refs #113967.

…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>
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Aug 4, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@jab-rh: This pull request references Jira Issue OCPBUGS-91952, which is invalid:

  • expected the sub-task to target the "5.0.0" version, but no target version was set
  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is MODIFIED instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Summary

  • Ports the enterprise-4.21 fix from cf93e21 to main after the module rename (nw-ingress-gateway-api-deployment-topologies.adocgateway-api-deployment-topologies.adoc).
  • Corrects Gateway hostname wildcards (*.example.com), broken YAML indentation (broken-bar characters), and HTTPRoute apiVersion values.

Test plan

  • Confirm examples in modules/gateway-api-deployment-topologies.adoc render valid YAML
  • After merge, cherry-pick to enterprise-4.22 and enterprise-5.0

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.

@openshift-ci openshift-ci Bot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Aug 4, 2026
@ocpdocs-previewbot

Copy link
Copy Markdown

@openshift-ci

openshift-ci Bot commented Aug 4, 2026

Copy link
Copy Markdown

@jab-rh: all tests passed!

Full PR test history. Your PR dashboard.

Details

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. I understand the commands that are listed here.

@jab-rh

jab-rh commented Aug 4, 2026

Copy link
Copy Markdown
Contributor Author

@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!

@jab-rh jab-rh added this to the Continuous Release milestone Aug 4, 2026
@rhamini3

rhamini3 commented Aug 4, 2026

Copy link
Copy Markdown

@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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

branch/enterprise-4.22 branch/enterprise-5.0 jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants