Update USP docs to match change to default keepalive#2160
Merged
Conversation
✅ Deploy Preview will be available once build job completes!
|
y82
approved these changes
Jul 21, 2026
JTorreG
approved these changes
Jul 21, 2026
sjberman
reviewed
Jul 21, 2026
sjberman
left a comment
Contributor
There was a problem hiding this comment.
Be sure to target the ngf-release-2.7 branch instead of main for this
Morgan-P-04
force-pushed
the
ngf/usp-keepalive-default
branch
from
July 22, 2026 08:49
c8f2abf to
7e492ab
Compare
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
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
This PR updates the default keepalive connections value for the Upstream Settings Policy API, to match recent changes. The change removes the outdated default previously used and updates the configuration examples to reflect the new changes.
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. ↩