// Module included in the following assemblies:
//
// * architecture/control-plane.adoc

:_mod-docs-content-type: CONCEPT
[id="olm-operators_{context}"]
= Add-on Operators

[role="_abstract"]
Operator Lifecycle Manager (OLM) and the software catalog are default components in {product-title} that help manage Kubernetes-native applications as Operators. 

Together they provide the system for discovering, installing, and managing the optional add-on Operators available on the cluster.

Using the software catalog in the {product-title} web console,
ifndef::openshift-dedicated,openshift-rosa[]
cluster administrators
endif::openshift-dedicated,openshift-rosa[]
ifdef::openshift-dedicated,openshift-rosa[]
administrators with the `dedicated-admin` role
endif::openshift-dedicated,openshift-rosa[]
and authorized users can select Operators to install from catalogs of Operators. 
After installing an Operator from the software catalog, you can make the Operator available globally or in specific namespaces to run in user applications.

Default catalog sources are available that include Red Hat Operators, certified Operators, and community Operators.
ifndef::openshift-dedicated,openshift-rosa[]
Cluster administrators
endif::openshift-dedicated,openshift-rosa[]
ifdef::openshift-dedicated,openshift-rosa[]
Administrators with the `dedicated-admin` role
endif::openshift-dedicated,openshift-rosa[]
can also add their own custom catalog sources, which can contain a custom set of Operators.

ifdef::openshift-dedicated,openshift-rosa[]
[NOTE]
====
All Operators listed in the Operator Hub marketplace should be available for installation. Red Hat considers these Operators as customer workloads, and are not monitored by Red Hat Site Reliability Engineering (SRE).
====
endif::openshift-dedicated,openshift-rosa[]

[NOTE]
====
OLM does not manage the cluster Operators that comprise the {product-title} architecture.
====
