![]() It is possible to change this behavior on an ingress level, which works well when you only have a few of them. When running several dozen ingress and with a high change rate of running pods it makes it easier to define this configuration on a global level. This change is completely backwards compatible, only adding the possibility of defining a new key in the configmap. |
||
---|---|---|
.. | ||
nginx-configuration | ||
third-party-addons | ||
basic-usage.md | ||
cli-arguments.md | ||
convert_arguments_to_doc.py | ||
custom-errors.md | ||
default-backend.md | ||
exposing-tcp-udp-services.md | ||
external-articles.md | ||
fcgi-services.md | ||
ingress-path-matching.md | ||
miscellaneous.md | ||
monitoring.md | ||
multiple-ingress.md | ||
tls.md |