-
Notifications
You must be signed in to change notification settings - Fork 2k
Labels
bugAn issue reporting a potential bugAn issue reporting a potential bug
Milestone
Description
I want NIC to provide safety around the relationship of proxy_buffers and proxy_buffer_size
Since modifying one of these settings impacts the other, the system should automatically adjust the 'other' setting to ensure that any new pods can start.
Explore how ingress-nginx solved this problem, the solution does not need to be more complicated nor precise.
This is about ensuring out of the box success and not expecting deep knowledge with NGINX.
Things to do:
- Setting nginx 'proxy-buffer-size' to 16k causes nginx config error kubernetes/ingress-nginx#363 needs to be implemented in NIC
- a new annotation, VS and configmap option needs to be exposed for proxy_busy_buffers_size, see nginx validation here
- "there must be at least 2 "proxy_buffers""); setting 1 proxy buffer results in nginx reload error: verify if this is the case and if yes put validation for corresponding annotation, vs and cm option
- Upgrade tests
- Docs
nginx.org/proxy-buffer-size: "5m"
nginx.org/proxy-buffers: "8 1m"
LeMace and pakahermes
Sub-issues
Metadata
Metadata
Assignees
Labels
bugAn issue reporting a potential bugAn issue reporting a potential bug
Type
Projects
Status
In Progress 🛠