Red Hat SummitDieser Inhalt ist in der von Ihnen ausgewählten Sprache nicht verfügbar.
Chapter 3. Cluster capabilities
Cluster administrators can use cluster capabilities to enable or disable optional components prior to installation. Cluster administrators can enable cluster capabilities at anytime after installation.
Cluster administrators cannot disable a cluster capability after it is enabled.
3.1. Selecting cluster capabilities
You can select cluster capabilities by following one of the installation methods that include customizing your cluster, such as "Installing a cluster on AWS with customizations" or "Installing a cluster on GCP with customizations".
During a customized installation, you create an
install-config.yamlIf you customize your cluster by enabling or disabling specific cluster capabilities, you are responsible for manually maintaining your
install-config.yamlinstall-config.yamlinstall-config.yamlYou can use the following configuration parameters to select cluster capabilities:
capabilities:
baselineCapabilitySet: v4.11
additionalEnabledCapabilities:
- CSISnapshot
- Console
- Storage- 1
- Defines a baseline set of capabilities to install. Valid values are
None,vCurrentandv4.x. If you selectNone, all optional capabilities will be disabled. The default value isvCurrent, which enables all optional capabilities.Noterefers to any value up to and including the current cluster version. For example, valid values for a OpenShift Container Platform 4.12 cluster arev4.xandv4.11.v4.12 - 2
- Defines a list of capabilities to explicitly enable. These will be enabled in addition to the capabilities specified in
baselineCapabilitySet.NoteIn this example, the default capability is set to
. Thev4.11field enables additional capabilities over the defaultadditionalEnabledCapabilitiescapability set.v4.11
The following table describes the
baselineCapabilitySet| Value | Description |
|---|---|
|
| Specify this option when you want to automatically add new, default capabilities that are introduced in new releases. |
|
| Specify this option when you want to enable the default capabilities for OpenShift Container Platform 4.11. By specifying |
|
| Specify this option when you want to enable the default capabilities for OpenShift Container Platform 4.12. By specifying |
|
| Specify when the other sets are too large, and you do not need any capabilities or want to fine-tune via |
3.2. Optional cluster capabilities in OpenShift Container Platform 4.12
Currently, cluster Operators provide the features for these optional capabilities. The following summarizes the features provided by each capability and what functionality you lose if it is disabled.
3.2.1. Bare-metal capability
The Cluster Baremetal Operator provides the features for the
baremetalThe Cluster Baremetal Operator (CBO) deploys all the components necessary to take a bare-metal server to a fully functioning worker node ready to run OpenShift Container Platform compute nodes. The CBO ensures that the metal3 deployment, which consists of the Bare Metal Operator (BMO) and Ironic containers, runs on one of the control plane nodes within the OpenShift Container Platform cluster. The CBO also listens for OpenShift Container Platform updates to resources that it watches and takes appropriate action.
The bare-metal capability is required for deployments using installer-provisioned infrastructure. Disabling the bare-metal capability can result in unexpected problems with these deployments.
It is recommended that cluster administrators only disable the bare-metal capability during installations with user-provisioned infrastructure that do not have any
BareMetalHostIf the bare-metal capability is disabled, the cluster cannot provision or manage bare-metal nodes. Only disable the capability if there are no
BareMetalHost3.2.2. Cluster storage capability
The Cluster Storage Operator provides the features for the
StorageThe Cluster Storage Operator sets OpenShift Container Platform cluster-wide storage defaults. It ensures a default
storageclassIf the cluster storage capability is disabled, the cluster will not have a default
storageclassstorageclassNotes
- The storage class that the Operator creates can be made non-default by editing its annotation, but this storage class cannot be deleted as long as the Operator runs.
3.2.3. Console capability
The Console Operator provides the features for the
ConsoleThe Console Operator installs and maintains the OpenShift Container Platform web console on a cluster. The Console Operator is installed by default and automatically maintains a console.
3.2.4. CSI snapshot controller capability
The Cluster CSI Snapshot Controller Operator provides the features for the
CSISnapshotThe Cluster CSI Snapshot Controller Operator installs and maintains the CSI Snapshot Controller. The CSI Snapshot Controller is responsible for watching the
VolumeSnapshot3.2.5. Insights capability
The Insights Operator provides the features for the
InsightsThe Insights Operator gathers OpenShift Container Platform configuration data and sends it to Red Hat. The data is used to produce proactive insights recommendations about potential issues that a cluster might be exposed to. These insights are communicated to cluster administrators through the Insights advisor service on console.redhat.com.
Notes
Insights Operator complements OpenShift Container Platform Telemetry.
3.2.6. Marketplace capability
The Marketplace Operator provides the features for the
marketplaceThe Marketplace Operator simplifies the process for bringing off-cluster Operators to your cluster by using a set of default Operator Lifecycle Manager (OLM) catalogs on the cluster. When the Marketplace Operator is installed, it creates the
openshift-marketplaceopenshift-marketplaceIf you disable the
marketplaceopenshift-marketplaceopenshift-marketplaceopenshift-openshift-marketplaceIf you enable the
marketplace3.2.7. OpenShift samples capability
The Cluster Samples Operator provides the features for the
openshift-samplesThe Cluster Samples Operator manages the sample image streams and templates stored in the
openshiftOn initial start up, the Operator creates the default samples configuration resource to initiate the creation of the image streams and templates. The configuration object is a cluster scoped object with the key
clusterconfigs.samplesThe image streams are the Red Hat Enterprise Linux CoreOS (RHCOS)-based OpenShift Container Platform image streams pointing to images on
registry.redhat.ioIf you disable the samples capability, users cannot access the image streams, samples, and templates it provides. Depending on your deployment, you might want to disable this component if you do not need it.
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}