Skip to content

Operators

What is an Operator?📜

A Kubernetes Operator is a software program designed to automate tasks performed by Human IT Operations personnel.

Kubernetes operators automate human IT operator knowledge and experience by running as a systemd service or pod on the cluster, using Custom Resources to configure their desired end state.

Comparison to Controllers📜

The Kubernetes Controller Manager runs as a pod or systemd service. It acts as a reconciliation loop that ensures the actual state is the desired state. Kubernetes deployment declaratively defines the desired number of replicas. The Kubernetes Controller Manager brings that desired state into reality and ensures it stays true over time. The controller manager spins up the pods associated with a deployment.

Difference between a Kubernetes Controller and a Kubernetes Operator:

Controller: Uses built in objects like pod, deployment, statefulset, ingress, etc. to define the desired end state.

Operator: Uses Custom Resources like GitRepository, HelmRelease, Kustomization etc. to define the desired state.

Custom Resources use Custom Resource Definitions to extend the Kubernetes API to create newly recognized Kubernetes YAML object types.

The Operator Pattern📜

Kubernetes Operator Pattern:

  • A CRD (Custom Resoruce Definitiion) defines a new configuration API.

  • A CR (Custom Resource), acts as the Declarative Configuration (governed by the CRD) that defines the desired end state.

  • An Operator (software program running as a pod on Kubernetes or systemd service), acts as the abstraction layer necessary to achieve the desired end state, as defined by the CR.

Definition from the official docs: The Operator pattern aims to capture the key aim of a human operator who is managing a service or set of services. Human operators who look after specific applications and services have deep knowledge of how the system ought to behave, how to deploy it, and how to react if there are problems.

../images/k8s/k8s-operator.webp Source: https://www.cncf.io/blog/2022/06/15/kubernetes-operators-what-are-they-some-examples

Big Bang Examples📜

  • Flux (GitRepository, HelmRelease, Kustomization),
  • ArgoCD (AppProject, Application),
  • Istio (Gateway, VirtualService, DestinationRule, EnvoyFilter),
  • Prometheus Operator Stack (Prometheus, ServiceMonitor), and
  • ECK: Elastic Cloud on Kubernetes (ElasticSearch).

Quiz Questions📜

What is an Operator?

A Kubernetes Operator is a software program designed to automate tasks performed by Human IT Operations personnel.

Kubernetes operators automate human IT operator knowledge and experience by running as a systemd service or pod on the cluster, using Custom Resources to configure their desired end state.

What is the difference between a Kubernetes Controller and a Kubernetes Operator?

A Kubernetes Controller: Uses built in objects like pod, deployment, statefulset, ingress, etc. to define the desired end state.

A Kubernetes Operator: Uses Custom Resources like GitRepository, HelmRelease, Kustomization etc. to define the desired state.