1cd17cd12c
In case some ingress have a syntax error in the snippet configuration, the freshly generated configuration will not be reloaded to prevent tearing down existing rules. Although, once inserted, this configuration is preventing from any other valid configuration to be inserted as it remains in the ingresses of the cluster. To solve this problem, implement an optional validation webhook that simulates the addition of the ingress to be added together with the rest of ingresses. In case the generated configuration is not validated by nginx, deny the insertion of the ingress. In case certificates are mounted using kubernetes secrets, when those changes, keys are automatically updated in the container volume, and the controller reloads it using the filewatcher. Related changes: - Update vendors - Extract useful functions to check configuration with an additional ingress - Update documentation for validating webhook - Add validating webhook examples - Add a metric for each syntax check success and errors - Add more certificate generation examples |
||
|---|---|---|
| .. | ||
| 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 | ||
| ingress-path-matching.md | ||
| miscellaneous.md | ||
| monitoring.md | ||
| multiple-ingress.md | ||
| tls.md | ||