Description of problem:
No field on a clusteringress resource is subject to any API validation whatsoever. There is also no reporting (on status) of any post-admission validation errors. Field content requirements should be articulated in the API docs, enforced in validation/admission/operator, and reported (as necessary) through status.
Today, setting invalid data on the clusteringress will simply cause a variety of things to go wrong rolling out the various pieces of a deployment, and the problems will only surface as generic availability status info and operator log messages.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Multiple PR's are in queue to address this bug:
Adds IngressController CRD Validation & Generation: https://github.com/openshift/cluster-ingress-operator/pull/183
Dep bump for the above PR: https://github.com/openshift/cluster-ingress-operator/pull/185
Post admission Ingress validation: https://github.com/openshift/cluster-ingress-operator/pull/187
Dep bump for the above PR: https://github.com/openshift/cluster-ingress-operator/pull/186
The last outstanding item from the bug description is:
There is also no reporting (on status) of any post-admission validation errors.
Going to call this one resolved by https://github.com/openshift/cluster-ingress-operator/pull/183 for basic openapi validation and we'll open more BZs for specific field validations as necessary.
verified with 4.0.0-0.nightly-2019-04-03-202419 and "validation" has been added to CRD of IngressController.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.