Red Hat Operators

The Cloud Credential Operator manages cloud provider credentials as Kubernetes custom resource definitions (CRDs).

openshift-cloud-credential-operator

No configuration required.

The Cluster Authentication Operator installs and maintains the Authentication Custom Resource in a cluster and can be viewed with:

cluster-authentication-operator

The Cluster Autoscaler Operator manages deployments of the OpenShift Cluster Autoscaler using the cluster-api provider.

cluster-autoscaler-operator

The Cluster Image Registry Operator manages a singleton instance of the OpenShift Container Platform registry. It manages all configuration of the registry, including creating storage.

On initial start up, the Operator creates a default image-registry resource instance based on the configuration detected in the cluster. This indicates what cloud storage type to use based on the cloud provider.

If insufficient information is available to define a complete image-registry resource, then an incomplete resource is defined and the Operator updates the resource status with information about what is missing.

The Cluster Image Registry Operator runs in the openshift-image-registry namespace and it also manages the registry instance in that location. All configuration and workload resources for the registry reside in that namespace.

cluster-image-registry-operator

The Cluster Monitoring Operator manages and updates the Prometheus-based cluster monitoring stack deployed on top of OpenShift Container Platform.

openshift-monitoring

The Cluster Network Operator installs and upgrades the networking components on an OpenShift Kubernetes cluster.

The OpenShift Controller Manager Operator installs and maintains the OpenShiftControllerManager Custom Resource in a cluster and can be viewed with:

The Custom Resource Definition openshiftcontrollermanagers.operator.openshift.io can be viewed in a cluster with:

cluster-openshift-controller-manager-operator

The Cluster Samples Operator manages the sample imagestreams and templates stored in the openshift namespace, and any container credentials, stored as a secret, needed for the imagestreams to import the images they reference.

On initial start up, the Operator creates the default samples resource to initiate the creation of the imagestreams and templates. The imagestreams are the Red Hat Enterprise Linux CoreOS (RHCOS)-based OpenShift Container Platform imagestreams pointing to images on registry.redhat.io. Similarly, the templates are those categorized as OpenShift Container Platform templates.

The Cluster Samples Operator, along with its configuration resources, are contained within the openshift-cluster-samples-operator namespace. On start up, it will copy the pull secret captured by the installation into the openshift namespace with the name samples-registry-credentials to facilitate imagestream imports. An administrator can create any additional secrets in the openshift namespace as needed. Those secrets contain the content of a container config.json needed to facilitate image import.

The image for the Cluster Samples Operator contains imagestream and template definitions for the associated OpenShift Container Platform release. Each sample includes an annotation that denotes the OpenShift Container Platform version that it is compatible with. The Operator uses this annotation to ensure that each sample matches it’s release version. Samples outside of its inventory are ignored, as are skipped samples. Modifications to any samples that are managed by the Operator are reverted automatically. The jenkins images are part of the image payload from the installation and are tagged into the imagestreams directly.

The samples resource includes a finalizer, which cleans up the following upon its deletion:

Upon deletion of the samples resource, the Cluster Samples Operator recreates the resource using the default configuration.

cluster-samples-operator

The Cluster Storage Operator sets OpenShift Container Platform cluster-wide storage defaults. It ensures a default storage class exists for OpenShift Container Platform clusters.

cluster-storage-operator

No configuration is required.

The Cluster SVCAT API Server Operator installs and maintains a singleton instance of the OpenShift Service Catalog on a cluster. Service Catalog is comprised of an aggregated API server and a controller manager; this Operator only deals with the API server portion of Service Catalog. See cluster-svcat-controller-manager-operator for the Operator responsible for the controller manager component of Service Catalog.

cluster-svcat-apiserver-operator

The Cluster SVCAT Controller Manager Operator installs and maintains a singleton instance of the OpenShift Service Catalog on a cluster. Service Catalog is comprised of an aggregated API server and a controller manager; this Operator only deals with the Controller Manager portion of Service Catalog. See the cluster-svcat-apiserver-operator for the Operator responsible for the API Server component of Service Catalog.

cluster-svcat-controller-manager-operator

cluster-version-operator

The Console Operator installs and maintains the OpenShift Container Platform web console on a cluster.

console-operator

The DNS Operator deploys and manages CoreDNS to provide a name resolution service to pods that enables DNS-based Kubernetes Service discovery in OpenShift Container Platform.

The Operator creates a working default deployment based on the cluster’s configuration.

The DNS Operator manages CoreDNS as a Kubernetes daemon set exposed as a service with a static IP. CoreDNS runs on all nodes in the cluster.

cluster-dns-operator

The etcd cluster Operator automates etcd cluster scaling, enables etcd monitoring and metrics, and simplifies disaster recovery procedures.

cluster-etcd-operator

The Ingress Operator configures and manages the OpenShift Container Platform router.

openshift-ingress-operator

The Ingress Operator sets up the router in the openshift-ingress project and creates the deployment for the router:

The Ingress Operator uses the clusterNetwork[].cidr from the network/cluster status to determine what mode (IPv4, IPv6, or dual stack) the managed ingress controller (router) should operate in. For example, if clusterNetwork contains only a v6 cidr, then the ingress controller will operate in v6-only mode. In the following example, ingress controllers managed by the Ingress Operator will run in v4-only mode because only one cluster network exists and the network is a v4 cidr:

The Kubernetes API Server Operator manages and updates the Kubernetes API server deployed on top of OpenShift Container Platform. The Operator is based on the OpenShift library-go framework and it is installed using the Cluster Version Operator (CVO).

openshift-kube-apiserver-operator

The Kubernetes Controller Manager Operator manages and updates the Kubernetes Controller Manager deployed on top of OpenShift Container Platform. The Operator is based on OpenShift library-go framework and it is installed via the Cluster Version Operator (CVO).

It contains the following components:

By default, the Operator exposes Prometheus metrics through the metrics service.

cluster-kube-controller-manager-operator

The Kubernetes Scheduler Operator manages and updates the Kubernetes Scheduler deployed on top of OpenShift Container Platform. The operator is based on the OpenShift Container Platform library-go framework and it is installed with the Cluster Version Operator (CVO).

The Kubernetes Scheduler Operator contains the following components:

By default, the Operator exposes Prometheus metrics through the metrics service.

cluster-kube-scheduler-operator

The configuration for the Kubernetes Scheduler is the result of merging:

All of these are sparse configurations, invalidated JSON snippets which are merged in order to form a valid configuration at the end.

The Machine API Operator manages the lifecycle of specific purpose CRDs, controllers, and RBAC objects that extend the Kubernetes API. This declares the desired state of machines in a cluster.

machine-api-operator

The Machine Congig Operator manages and applies configuration and updates of the base operating system and container runtime, including everything between the kernel and kubelet.

There are four components:

openshift-machine-config-operator

The Marketplace Operator is a conduit to bring off-cluster Operators to your cluster.

operator-marketplace

The Node Tuning Operator helps you manage node-level tuning by orchestrating the Tuned daemon. The majority of high-performance applications require some level of kernel tuning. The Node Tuning Operator provides a unified management interface to users of node-level sysctls and more flexibility to add custom tuning specified by user needs. The Operator manages the containerized Tuned daemon for OpenShift Container Platform as a Kubernetes daemon set. It ensures the custom tuning specification is passed to all containerized Tuned daemons running in the cluster in the format that the daemons understand. The daemons run on all nodes in the cluster, one per node.

Node-level settings applied by the containerized Tuned daemon are rolled back on an event that triggers a profile change or when the containerized Tuned daemon is terminated gracefully by receiving and handling a termination signal.

The Node Tuning Operator is part of a standard OpenShift Container Platform installation in version 4.1 and later.

cluster-node-tuning-operator

The OpenShift API Server Operator installs and maintains the openshift-apiserver on a cluster.

openshift-apiserver-operator

The Prometheus Operator for Kubernetes provides easy monitoring definitions for Kubernetes services and deployment and management of Prometheus instances.

Once installed, the Prometheus Operator provides the following features:

prometheus-operator