1
0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-07 00:48:01 +01:00
Files
openshift-docs/modules/olm-why-use-operators.adoc
Alex Dellapenta a9f40e53a9 Lowercase CRD
2020-11-06 12:33:34 -07:00

40 lines
1.7 KiB
Plaintext
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
// Module included in the following assemblies:
//
// * operators/understanding/olm-what-operators-are.adoc
[id="olm-why-use-operators_{context}"]
= Why use Operators?
Operators provide:
--
- Repeatability of installation and upgrade.
- Constant health checks of every system component.
- Over-the-air (OTA) updates for OpenShift components and ISV content.
- A place to encapsulate knowledge from field engineers and spread it to all
users, not just one or two.
--
Why deploy on Kubernetes?::
Kubernetes (and by extension, {product-title}) contains all of the primitives
needed to build complex distributed systems secret handling, load balancing,
service discovery, autoscaling that work across on-premise and cloud
providers.
Why manage your app with Kubernetes APIs and `kubectl` tooling?::
These APIs are feature rich, have clients for all platforms and plug into the
clusters access control/auditing. An Operator uses the Kubernetes' extension
mechanism, custom resource definitions (CRDs), so your custom object,
link:https://marketplace.redhat.com/en-us/products/mongodb-enterprise-advanced-from-ibm[for
example `MongoDB`], looks and acts just like the built-in, native Kubernetes
objects.
How do Operators compare with Service Brokers?::
A Service Broker is a step towards programmatic discovery and deployment of an
app. However, because it is not a long running process, it cannot execute Day 2
operations like upgrade, failover, or scaling. Customizations and
parameterization of tunables are provided at install time, versus an Operator
that is constantly watching your cluster's current state. Off-cluster services
continue to be a good match for a Service Broker, although Operators exist for
these as well.