mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
39 lines
2.1 KiB
Plaintext
39 lines
2.1 KiB
Plaintext
// Module included in the following assemblies:
|
|
//
|
|
// * architecture/control-plane.adoc
|
|
// * operators/index.adoc
|
|
|
|
|
|
ifeval::["{context}" == "operators-overview"]
|
|
:index:
|
|
endif::[]
|
|
|
|
:_mod-docs-content-type: CONCEPT
|
|
ifndef::index[]
|
|
[id="operators-overview_{context}"]
|
|
= Operators in {product-title}
|
|
endif::[]
|
|
|
|
Operators are among the most important components of {product-title}. They are the preferred method of packaging, deploying, and managing services on the control plane. They can also provide advantages to applications that users run.
|
|
|
|
Operators integrate with Kubernetes APIs and CLI tools such as `kubectl` and the {oc-first}. They provide the means of monitoring applications, performing health checks, managing over-the-air (OTA) updates, and ensuring that applications remain in your specified state.
|
|
|
|
ifndef::index[]
|
|
Operators also offer a more granular configuration experience. You configure each component by modifying the API that the Operator exposes instead of modifying a global configuration file.
|
|
|
|
Because CRI-O and the Kubelet run on every node, almost every other cluster function can be managed on the control plane by using Operators. Components that are added to the control plane by using Operators include critical networking and credential services.
|
|
endif::[]
|
|
|
|
ifdef::index[]
|
|
Operators are designed specifically for Kubernetes-native applications to implement and automate common Day 1 operations, such as installation and configuration. Operators can also automate Day 2 operations, such as autoscaling up or down and creating backups. All of these activities are directed by a piece of software running on your cluster.
|
|
endif::index[]
|
|
|
|
While both follow similar Operator concepts and goals, Operators in {product-title} are managed by two different systems, depending on their purpose:
|
|
|
|
Cluster Operators:: Managed by the Cluster Version Operator (CVO) and installed by default to perform cluster functions.
|
|
Optional add-on Operators:: Managed by Operator Lifecycle Manager (OLM) and can be made accessible for users to run in their applications. Also known as _OLM-based Operators_.
|
|
|
|
ifeval::["{context}" == "operators-overview"]
|
|
:!index:
|
|
endif::[]
|