-
Feature Request
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
None
-
None
-
Product / Portfolio Work
-
None
-
False
-
-
None
-
None
-
None
-
-
None
-
None
-
None
-
None
-
None
1. Proposed title of this feature request
Provide the ability to disable Cluster Capabilities after initial deployment of the cluster.
2. What is the nature and description of the request?
Composable Openshift feature provides the ability to customize ( enable/disable ) the Cluster capabilities during the cluster installation.
Cluster capabilities can also be enabled at anytime after the cluster installation. However, there is no option to disable cluster capabilities that are currently active without re deployment of the cluster. This RFE is a request to provide the ability to disable cluster capabilities after initial deployment.
3. Why does the customer need this? (List the business requirements here)
For Telco customers to take advantage of the reduction in platform footprint provided by the composable openshift feature, they need the ability to disable existing cluster capabilities as part of an upgrade or a config update to the cluster. re deploying 100's/1000's of clusters is not a viable option.
- blocks
-
RFE-8702 After removing `image-registry` Investigate alternative methods to disable or suppress the `node-ca` daemonset without compromising cluster functionality.
-
- Waiting
-