NGF: Update Gateway compatibility and secure traffic guide for GWAPI v1.4.0 #1443
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
documentation
ciarams87
changed the title
ciarams87
changed the title
ciarams87
changed the title
ciarams87
force-pushed
the
ngf/gw-1.4.0-updates
branch
from
bdf03cf to
a0ee4dc
Compare
ciarams87
changed the title
sjberman
approved these changes
Nov 14, 2025
Member
|
PR build failure can be ignored: it's a go mod dependency issue. I will get the release branch reconciled with main. |
✅ Deploy Preview will be available once build job completes!
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed changes
Update NGF documentation to reflect the changes brought in as part of supporting Gateway API v1.4.0
Checklist
Before sharing this pull request, I completed the following checklist:
Footnotes
Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content. ↩