2.4.2. Operator Lifecycle Manager architecture

This guide outlines the component architecture of Operator Lifecycle Manager (OLM) in OpenShift Dedicated.

Operator Lifecycle Manager (OLM) is composed of two Operators: the OLM Operator and the Catalog Operator.

The OLM and Catalog Operators are responsible for managing the custom resource definitions (CRDs) that are the basis for the OLM framework:

Expand

表 2.3. CRDs managed by OLM and Catalog Operators
Resource	Short name	Owner	Description
`ClusterServiceVersion` (CSV)	`csv`	OLM	Application metadata: name, version, icon, required resources, installation, and so on.
`InstallPlan`	`ip`	Catalog	Calculated list of resources to be created to automatically install or upgrade a CSV.
`CatalogSource`	`catsrc`	Catalog	A repository of CSVs, CRDs, and packages that define an application.
`Subscription`	`sub`	Catalog	Used to keep CSVs up to date by tracking a channel in a package.
`OperatorGroup`	`og`	OLM	Configures all Operators deployed in the same namespace as the `OperatorGroup` object to watch for their custom resource (CR) in a list of namespaces or cluster-wide.

Each of these Operators is also responsible for creating the following resources:

Expand

表 2.4. Resources created by OLM and Catalog Operators
Resource	Owner
`Deployments`	OLM
`ServiceAccounts`
`(Cluster)Roles`
`(Cluster)RoleBindings`
`CustomResourceDefinitions` (CRDs)	Catalog
`ClusterServiceVersions`	Catalog