-
Notifications
You must be signed in to change notification settings - Fork 212
Conformance report for NGINX Gateway Fabric #2023
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: sjberman The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Welcome @sjberman! |
|
Hi @sjberman. Thanks for your PR. I'm waiting for a github.com member to verify that this patch is reasonable to test. If it is, they should reply with 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. |
✅ Deploy Preview for gateway-api-inference-extension ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
| apiVersion: gateway.networking.k8s.io/v1 | ||
| date: "2025-12-18T16:59:22Z" | ||
| gatewayAPIChannel: experimental | ||
| gatewayAPIVersion: v1.4.1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just noticed that the GAIE version isn't generated in this report. Does it need to exist? Manually added?
What type of PR is this?
/kind documentation
What this PR does / why we need it:
Adding conformance report for NGINX Gateway Fabric
Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?: