-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.16
-
None
-
False
-
Description of problem:
OpenShift 4.16 installer documentation does not indicate that the Ingress capability is now required.
Version-Release number of selected component (if applicable):
4.16
How reproducible:
Always
Steps to Reproduce:
Follow documentation steps for deploying a cluster with the "None" capabilities set.
Actual results:
Cluster installs fail, with indication that the Ingress capability must be enabled.
Expected results:
Documentation should reflect that the Ingress capability must be added as an "additional capability" when failing to do so leads to the installer failing its pre-check validations.
Additional info:
See OCPBUGS-33793, OCPBUGS-35250.
- is related to
-
OCPBUGS-34384 Default Rolebindings Created on OCP 4.16 with No Capabilities
- Closed
- relates to
-
OCPBUGS-35250 Cluster-bot cannot launch `no-capabilities` clusters
- New
-
OCPBUGS-33793 Cluster Install with disabled Ingress capability does not disable Ingress
- Closed