NGF release 2.0 #645
Merged
NGF release 2.0 #645
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
Includes changes to the NginxProxy API for the 2.0 release.
The control plane will no longer need permissions to reload nginx, so this troubleshooting step no longer applies.
Updates the Gateway API Compatibility doc to list Gateway Infrastructure field as partially supported. Also, updates the data plane configuration how-to to describe how to attach NginxProxy resources to Gateways and GatewayClasses. Co-authored-by: Saylor Berman <[email protected]>
* Add information on confuring NginxProxy resource for dashboard * Replace api.md file with file on main * Add small feedback and use document address blocks
Add documentation for regex matching
NGF now supports the ability to configure a BackendTLSPolicy with a Secret containing the CA certificate.
NGF is adding the capability for users to configure request mirroring. This adds a guide explaining how a user can set this up.
NGF: Update documentation for control plane/data plane separation feature for the 2.0 release. Includes upgrade docs, new configurations, and new architecture. --------- Co-authored-by: bjee19 <[email protected]> Co-authored-by: Ciara Stacke <[email protected]> Co-authored-by: salonichf5 <[email protected]> Co-authored-by: Alan Dooley <[email protected]>
Add allowedListeners to gateway api compatability doc.
Update installation document with 2.x upgrade information
This commit adds a release banner for NGINX Gateway Fabric 2.0, using the new banner mechanism added to the documentation theme. It cascades from the index page, appearing at the top of all pages.
This commit partially restructures the NGINX Gateway Fabric documentation to flatten the folder structure, reducing the amount of steps a reader must navigate to get to useful instructions. The majority of the effort is concentrated on the Install section, simplifying the URL structure and creating logical links in the sequence of pages presented and the linear connection of pre-requisites and next steps when a user is onboarding a cluster. Additional work will follow this effort, once identifying more common user journeys and how individual documents can be grouped together logically. --------- Co-authored-by: Saylor Berman <[email protected]>
github-actions
bot
added
documentation
✅ Deploy Preview will be available once build job completes!
|
ADubhlaoich
approved these changes
Jun 5, 2025
y82
approved these changes
Jun 5, 2025
Co-authored-by: yar <[email protected]>
Co-authored-by: yar <[email protected]>
Co-authored-by: yar <[email protected]>
Co-authored-by: yar <[email protected]>
Co-authored-by: yar <[email protected]>
ciarams87
approved these changes
Jun 5, 2025
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
Release docs for NGF 2.0.
Checklist
Before merging a pull request, run through this checklist and mark each as complete.
README.mdandCHANGELOG.mdFootnotes
Potentially sensitive changes include anything involving code, personally identify information (PII), live URLs or significant amounts of new or revised documentation. Please refer to our style guide for guidance about placeholder content. ↩