FAQs about Operator design, CRDs, and APIs
These questions cover information about an Operator's design, including approaches to developing an Operator and how Operators can function within a Kubernetes cluster. The topics in this section were introduced in Chapter 2, Understanding How Operators Interact with Kubernetes, and Chapter 3, Designing an Operator – CRD, API, and Target Reconciliation.
How does an Operator interact with Kubernetes?
Operators interact with Kubernetes through event-triggered continuous monitoring of the cluster's state, wherein the Operator attempts to reconcile the current state with the desired state as specified by a user. From a technical standpoint, it does so through a standard set of Kubernetes client libraries that allow it to list, get, watch, create, and update Kubernetes resources.
What cluster resources does an Operator act on?
An Operator can act on any resource that is accessible through the Kubernetes API (and that...