Skip to content

docs: Use kustomize overlay for Nginx GW API #769

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

Merged
merged 1 commit into from
Feb 7, 2025

Conversation

LukeRepko
Copy link
Contributor

There is a patch in the base overlay which modifies proxy_buffers to account for large headers which is common in our envioronment and ultimately results in Nginx throwing a 502 and logging an error like, "upstream sent too big header while reading response header from upstream".

This update also includes the latest changes to the nginx.conf as obtained from a fresh install.

Starting in v1.5.0, the SnippetsFilterAPI was added which can be used in lieu of this configuration override, though it has to be enabled manually, and more testing is needed to implement the same.

Jira: OSPC-990
PR: #463

There is a patch in the `base` overlay which modifies proxy_buffers to
account for large headers which is common in our envioronment and
ultimately results in Nginx throwing a 502 and logging an error like,
"upstream sent too big header while reading response header from upstream".

This update also includes the latest changes to the nginx.conf as
obtained from a fresh install.

Starting in v1.5.0, the SnippetsFilterAPI was added which can be used in
lieu of this configuration override, though it has to be enabled
manually, and more testing is needed to implement the same.

Jira: OSPC-990
PR: rackerlabs#463
@cloudnull cloudnull merged commit 4c3daca into rackerlabs:main Feb 7, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants