ingress-controller
ingress-controller copied to clipboard
[P3] validate Ingress parameter combination
Is your feature request related to a problem? Please describe.
Not all combinations of parameters are compatible, i.e.
- TCP routes do not support certain annotations such as
secure_upstream
-
prefix_rewrite
would only affect routes that havepathType: Prefix
- there's likely more
It is relatively easy to make a mistake (i.e. when starting from a template or example), and may be impossible to debug or figure out what is wrong.
We currently only detect certain obviously invalid parameter combinations, and validate the configuration via Envoy.
Describe the solution you'd like
- add validation to parameter values
- add validation for parameter compatibility
- do not reconcile Ingress resources that are incorrect / invalid.
Describe alternatives you've considered
Explain any additional use-cases
Additional context