This reference guide indexes the cluster Operators shipped by Red Hat that serve as the architectural foundation for {product-title}. Cluster Operators are installed by default, unless otherwise noted, and are managed by the Cluster Version Operator (CVO). For more details on the control plane architecture, see Operators in {product-title}.
Cluster administrators can view cluster Operators in the {product-title} web console from the Administration → Cluster Settings page.
|
Note
|
Cluster Operators are not managed by Operator Lifecycle Manager (OLM) and OperatorHub. OLM and OperatorHub are part of the Operator Framework used in {product-title} for installing and running optional add-on Operators. |
Some of the following cluster Operators can be disabled prior to installation. For more information see cluster capabilities.
|
Note
|
The following sections pertain to {olmv0-first} that has been included with {product-title} 4 since its initial release. For {olmv1}, see {olmv1-first} Operators. |
In {product-title}, OLM functionality is provided across a set of cluster Operators:
operator-lifecycle-manager-
Provides the OLM Operator. Also informs cluster administrators if there are any installed Operators blocking cluster upgrade, based on their
olm.maxOpenShiftVersionproperties. For more information, see "Controlling Operator compatibility with {product-title} versions". operator-lifecycle-manager-catalog-
Provides the Catalog Operator.
operator-lifecycle-manager-packageserver-
Represents an API extension server responsible for collecting metadata from all catalogs on the cluster and serves the user-facing
PackageManifestAPI.