-
Bug
-
Resolution: Done-Errata
-
Critical
-
4.16.0
-
None
Description of problem:
If I use custom CVO capabilities via the install config, I can create a capability set that disables the Ingress capability.
However, once the cluster boots up, the Ingress capability will always be enabled.
This creates a dissonance between the desired install config and what happens.
It would be better to fail the install at install-config validation to prevent that dissonance.
Version-Release number of selected component (if applicable):
4.16
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
- clones
-
OCPBUGS-33793 Cluster Install with disabled Ingress capability does not disable Ingress
-
- Closed
-
- depends on
-
OCPBUGS-33793 Cluster Install with disabled Ingress capability does not disable Ingress
-
- Closed
-
- links to
-
RHEA-2024:0041
OpenShift Container Platform 4.16.z bug fix update