Automatic merge from submit-queue
Make map_hash_bucket_size configurable
I was getting an error while trying to run the nginx controller in minikube. This allows this nginx configuration option to be passed in through a configmap.
The default value depends on the processor's cache line size (32 | 64 | 128), however ServerNameHashBucketSize is determined similarly, so I've set it to the same default (64).
Fixes#1817
ref https://github.com/kubernetes/minikube/issues/611
cc @bprashanth
Automatic merge from submit-queue
ingress/controllers/nginx: WebSocket documentation
For those that do not understand the default way in which nginx proxies
requests not containing a "Connection" header, the approach for enabling
WebSocket support might not make sense. This commit adds documentation
that explains why things are done this way.
For those that do not understand the default way in which nginx proxies
requests not containing a "Connection" header, the approach for enabling
WebSocket support might not make sense. This commit adds documentation
that explains why things are done this way.
Automatic merge from submit-queue
Allow customisation of the nginx proxy_buffer_size directive via ConfigMap
I'm opening a new PR with the same changes as #1693 because I pushed the latter with an email address that can't be used to sign the CLA. Description from the previous PR:
When using nginx as a proxy we can run into the following error:
```
upstream sent too big header while reading response header from upstream
```
In order to fix this, we need to be able to configure the proxy_buffer_size nginx directive to increase its value. This PR updates the nginx-ingress-controller to allow that.
Automatic merge from submit-queue
[nginx-ingress-controller]: Adapt nginx hash sizes to the number of ingress
This change allows the tuning of 2 important NGINX variables:
- server_names_hash_max_size
- server_names_hash_bucket_size
The default values should be enough for most of the users but after +300 Ingress rules or long hostnames as FQDN NGINX requires tuning of this values or it will not start.
The introduced change allows the self-tuning using the Ingress information
Using `--v=3` it's possible to see the changes:
```
...
I0822 21:42:10.517778 1 template.go:84] adjusting ServerNameHashMaxSize variable from 4096 to 16384
...
```
fixes#1487
