-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
options using byte-size unit "g" not honored after upgrading to 0.21.0 #3468
Comments
@RutledgePaulV this seems to have been introduced as part of #3409. For now you can use If you look at logs you will see something like cc @wayt |
Thanks! |
Indeed I'll make a change for that. |
NGINX Ingress controller version:
Kubernetes version:
Environment:
What happened:
We have a few custom settings for ingress in our configmap. After upgrading from 0.18.0 to 0.21.0 we discovered that the proxy-body-size wasn't having the desired effect (uploads were capped too low). I grepped the nginx.conf file from inside the container and found that
client_max_body_size
was set at"10m"
despite our custom setting being"5g"
. I confirmed that some of the configmap settings were still being used (proxy-request-buffering: off
). Our only change was to the ingress image tag.What you expected to happen:
client_max_body_size
to be set at5g
when my config map definesproxy-body-size: 5g
How to reproduce it (as minimally and precisely as possible):
Our config map:
Our startup args:
We don't have per-ingress configuration options with annotations.
Anything else we need to know:
I'm happy to gather more diagnostic information if necessary. My hope is this is easily reproducible and related to recent changes but I haven't yet tried a minimal example. I was able to reproduce it in two different clusters.
The text was updated successfully, but these errors were encountered: