DevFW-CICD/ingress-nginx-helm
14
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

fix typo

Browse source
This commit is contained in:
Tony Li 2017-08-12 03:14:08 -04:00
parent 91e75457c4
commit 6602b2f0d8
No known key found for this signature in database
GPG key ID: E73DA11CDB50D072
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/annotations.md
View file

@ -63,7 +63,7 @@ Key:
| `session-cookie-hash` | When `affinity` is set to `cookie`, the hash algorithm used: `md5`, `sha`, `index`. (nginx) | `session-cookie-hash` | When `affinity` is set to `cookie`, the hash algorithm used: `md5`, `sha`, `index`. (nginx)
| `proxy-body-size` | Maximum request body size. (nginx, haproxy) | `proxy-body-size` | Maximum request body size. (nginx, haproxy)
| `follow-redirects` | Follow HTTP redirects in the response and deliver the redirect target to the client. (trafficserver) | `follow-redirects` | Follow HTTP redirects in the response and deliver the redirect target to the client. (trafficserver)
| `kubernetes.io/ingress.global-static-ip-name` | Name of the static global IP address in GCP to use when provisioning the HTTPS load balanver. (gce) | `kubernetes.io/ingress.global-static-ip-name` | Name of the static global IP address in GCP to use when provisioning the HTTPS load balancer. (gce)
[1] The documentation for the `nginx` controller says that only one of `limit-connections` or `limit-rps` may be specified; it's not clear why this is. [1] The documentation for the `nginx` controller says that only one of `limit-connections` or `limit-rps` may be specified; it's not clear why this is.