Skip to content
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

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

kate-osborn
Copy link
Contributor

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.

  • I have read the CONTRIBUTING doc
  • I have added tests that prove my fix is effective or that my feature works
  • I have checked that all unit tests pass after adding my changes
  • I have updated necessary documentation
  • I have rebased my branch onto main
  • I will ensure my PR is targeting the main branch and pulling from my branch from my own fork

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.

Add how-to guide for configuring upstream settings for services using the UpstreamSettingsPolicy API

@kate-osborn kate-osborn requested review from a team as code owners January 7, 2025 20:35
@github-actions github-actions bot added the documentation Improvements or additions to documentation label Jan 7, 2025
@bjee19
Copy link
Contributor

bjee19 commented Jan 7, 2025

Is there a better way to verify the settings?

Nothing is coming to mind for me.

Do we need to verify them beyond checking the status?

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).

Copy link
Contributor

@bjee19 bjee19 left a 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!

Copy link
Contributor

@salonichf5 salonichf5 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great !

Copy link
Contributor

@salonichf5 salonichf5 left a 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

Copy link
Contributor

@ADubhlaoich ADubhlaoich left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation release-notes
Projects
Status: 🆕 New
Development

Successfully merging this pull request may close these issues.

Guide for Upstream Settings Policy
4 participants