-
Notifications
You must be signed in to change notification settings - Fork 100
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
Add guide for UpstreamSettingsPolicy #2987
base: main
Are you sure you want to change the base?
Conversation
6206c93
to
e3a865e
Compare
Nothing is coming to mind for me.
I like what you have right now, I think going beyond checking the status and actually showing the nginx configuration change is helpful especially since it'd be difficult (i'm not so sure how to maybe its easy lol) to actually show the working changes through curls to the services (like what we do with other guides). |
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.
good job I like the guide!
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.
Looks great !
cf6c497
to
53dc2f7
Compare
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.
One comment about formatting but looks good to me
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.
LGTM!
Remove unnecessary comma Co-authored-by: bjee19 <[email protected]>
571ad71
to
0b1e851
Compare
Proposed changes
Problem: As a user, I want an example of how to configure upstream settings for my application.
Solution: Add a how-to guide describing how to configure upstream zone size and keepalives for services. Also adds UpstreamSettingsPolicy to the table in the custom policies document and moves the custom policies document closer to the top of the overview page to increase visibility.
Testing: Ran through the steps in the guide and verified they work.
Please focus on: The "verification" portion of the guide where we exec into the NGINX container and check the upstream blocks for the appropriate directives. Is there a better way to verify the settings? Do we need to verify them beyond checking the status?
Closes #2369
Checklist
Before creating a PR, run through this checklist and mark each as complete.
Release notes
If this PR introduces a change that affects users and needs to be mentioned in the release notes,
please add a brief note that summarizes the change.