-
Notifications
You must be signed in to change notification settings - Fork 140
Comparing changes
Open a pull request
base repository: nginx/nginx-gateway-fabric
base: v2.1.1
head repository: nginx/nginx-gateway-fabric
compare: v2.1.2
- 8 commits
- 34 files changed
- 5 contributors
Commits on Sep 17, 2025
-
Improve connection reset handling during ServiceAccountToken rotation (…
…#3905) (#3932) Problem: During ServiceAccountToken rotation, nginx-gateway-fabric was sometimes experiencing deadlocks due to the Subscribe method incorrectly intercepting initial configuration operations after a ServiceAccountToken rotation and incorrect signaling broadcast completion Solution: Implemented a pendingRequest tracking mechanism to distinguish between initial setup operations and broadcast operations.
Configuration menu - View commit details
-
Copy full SHA for 39a3878 - Browse repository at this point
Copy the full SHA 39a3878View commit details
Commits on Sep 18, 2025
-
Update dependency nginx/agent to v3.3.1 (#3934) (#3935)
* Update dependency nginx/agent to v3.3.1 | datasource | package | from | to | | ----------- | ----------- | ------ | ------ | | github-tags | nginx/agent | v3.3.0 | v3.3.1 | * Update all agent version refs --------- Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for c68b52a - Browse repository at this point
Copy the full SHA c68b52aView commit details
Commits on Sep 19, 2025
-
Remove error condition on httproute when nginx reload fails (#3936) (#…
…3938) Problem: When nginx reload fails, all routes are marked invalid Solution: Remove adding GatewayNotProgrammed condition to routes since the error should only be reflected on Gateway Listener conditions
Configuration menu - View commit details
-
Copy full SHA for f76e38f - Browse repository at this point
Copy the full SHA f76e38fView commit details -
Revert agent reload backoff settings (#3937) (#3939)
Revert changes to agent reload backoff settings due to a fix added in Agent v3.3.1. Tested SnippetsFilter Functional on NGINX Plus test to ensure changes work.
Configuration menu - View commit details
-
Copy full SHA for 4b7ff0e - Browse repository at this point
Copy the full SHA 4b7ff0eView commit details
Commits on Sep 24, 2025
-
Move certs job service account token (#3951) (#3952)
Problem: For security reasons, it's best practice to not have automountServiceToken on the ServiceAccount, and instead set in directly on the workloads that need the token. Solution: Set this field on the Pods instead of the ServiceAccounts. This was missed as part of the original PR.
Configuration menu - View commit details
-
Copy full SHA for 1d3ce3a - Browse repository at this point
Copy the full SHA 1d3ce3aView commit details -
Add nginx image version validation during agent connections (#3928) (#…
…3953) Problem: During an NGF upgrade, the new version of the control plane will send a configuration to the old version of the nginx data plane, before the nginx data plane is updated to the new version. This can cause incompatibility issues for a brief amount of time, which could cause disruptions. Solution: Implement version validation by ensuring the pod image matches the image in the current deployment/ daemonset spec to prevent configuration from being sent to nginx data plane pods still running the previous image version during upgrades. Co-authored-by: Ciara Stacke <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 936fc8e - Browse repository at this point
Copy the full SHA 936fc8eView commit details
Commits on Sep 25, 2025
-
Configuration menu - View commit details
-
Copy full SHA for da050bc - Browse repository at this point
Copy the full SHA da050bcView commit details -
Configuration menu - View commit details
-
Copy full SHA for 877c415 - Browse repository at this point
Copy the full SHA 877c415View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v2.1.1...v2.1.2