Impossible to modify nginx parameter client_max_body_size
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Kubernetes API Load Balancer |
Fix Released
|
Medium
|
Mateo Florido |
Bug Description
Hello,
Problem:
Trying to install helm chart stable/
"Error: create: failed to create: the server responded with the status code 413 but did not return more information (post secrets)"
Description:
Nginx service on kubeapi-
/var/log/
"2020/08/31 16:06:14 [error] 20918#20918: *10354770 client intended to send too large body: 1054818 bytes, client: 10.100.251.5, server: _, request: "POST /api/v1/
/var/log/
10.100.251.5 - admin [31/Aug/
Changed in charm-kubeapi-load-balancer: | |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in charm-kubeapi-load-balancer: | |
status: | Triaged → In Progress |
assignee: | nobody → Mateo Florido (mateoflorido) |
milestone: | none → 1.28+ck1 |
Changed in charm-kubeapi-load-balancer: | |
status: | In Progress → Fix Committed |
tags: | added: backport-needed |
Changed in charm-kubeapi-load-balancer: | |
status: | Fix Committed → Fix Released |
Changed in charm-kubeapi-load-balancer: | |
status: | Fix Committed → Fix Released |
I just wanted to confirm that this is indeed still a problem, and that setting client_ max_body_ size to 10M or so (and running helm very quickly before it gets reverted) is the only workaround I've found so far.
It's one of the only manual steps in my cluster onboarding process and a real pain to work around.
Also, the OP states that this is about secrets, but more precisely it's the total manifest size that helm renders out of the kube-prometheus -stack chart.