Operator pattern overview in Kubernetes - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the Operator pattern in Kubernetes?

The Operator pattern is a way to automate the management of complex applications on Kubernetes by encoding operational knowledge into software that runs inside the cluster.

intermediate

How does an Operator extend Kubernetes functionality?

An Operator uses Custom Resource Definitions (CRDs) to add new types to Kubernetes and controllers to manage the lifecycle of these resources automatically.

beginner

What real-life role does an Operator play in Kubernetes?

An Operator acts like a human operator who knows how to install, configure, and maintain an application, but it does this automatically inside the cluster.

intermediate

What are Custom Resource Definitions (CRDs) in the Operator pattern?

CRDs are extensions to Kubernetes that let you define new resource types, which Operators use to represent and manage complex applications.

beginner

Why is the Operator pattern useful for managing stateful applications?

Because it automates tasks like backups, upgrades, and scaling, which are usually complex and error-prone when done manually.

What does an Operator primarily use to add new resource types in Kubernetes?

A ConfigMaps

B Pods

C Custom Resource Definitions (CRDs)

D Namespaces

Operators use CRDs to define new resource types that Kubernetes does not have by default.

Which component in an Operator watches and manages resources automatically?

A Controller

B Scheduler

C API Server

D Ingress

The controller is the part of an Operator that monitors resources and takes actions to keep them in the desired state.

What is the main benefit of using an Operator for application management?

A Automates complex operational tasks

B Creates new Kubernetes clusters

C Replaces Kubernetes API Server

D Manages user authentication

Operators automate tasks like installation, upgrades, and backups, reducing manual work.

Which of these best describes an Operator's role?

A A tool to create Kubernetes clusters

B A software agent that manages applications like a human operator would

C A replacement for Kubernetes scheduler

D A database management system

Operators encode human operational knowledge to manage applications automatically.

What kind of applications benefit most from Operators?

A Command line tools

B Simple static websites

C Single container apps without storage

D Stateful and complex applications

Stateful and complex apps need careful management, which Operators automate.

Explain the Operator pattern and how it helps manage applications in Kubernetes.

Think about how a human operator manages apps and how software can do the same.

Describe the role of Custom Resource Definitions (CRDs) and controllers in the Operator pattern.

CRDs add new objects; controllers keep them healthy.

Practice

1. What is the main purpose of the Kubernetes Operator pattern?

easy

A. To replace Kubernetes core components

B. To automate application management tasks on Kubernetes

C. To manually configure pods and services

D. To monitor network traffic between nodes

Solution

1. Step 1: Understand the Operator pattern role

   The Operator pattern automates tasks like deployment, scaling, and updates for applications on Kubernetes.

2. Step 2: Compare options with the pattern's purpose

   Only To automate application management tasks on Kubernetes describes automation of app management, which matches the Operator's goal.

3. Final Answer:

   To automate application management tasks on Kubernetes -> Option B

4. Quick Check:

   Operator automates app management = A [OK]

Hint: Operators automate apps, not replace Kubernetes core [OK]

Common Mistakes:

• Thinking Operators replace Kubernetes components
• Confusing manual config with automation
• Assuming Operators handle network monitoring

2. Which Kubernetes resource is essential for an Operator to manage custom application logic?

easy

A. Pod

B. Service

C. Custom Resource Definition (CRD)

D. ConfigMap

Solution

1. Step 1: Identify resource for extending Kubernetes

   Operators use Custom Resource Definitions (CRDs) to add new resource types representing app-specific data.

2. Step 2: Match resource with Operator management

   CRDs enable Operators to watch and act on custom resources, unlike Pods, Services, or ConfigMaps.

3. Final Answer:

   Custom Resource Definition (CRD) -> Option C

4. Quick Check:

   CRD extends Kubernetes for Operators = B [OK]

Hint: CRDs define custom resources Operators manage [OK]

Common Mistakes:

• Choosing Pod or Service which are standard resources
• Confusing ConfigMap with custom resource definitions
• Not knowing CRD extends Kubernetes API

3. Given this Operator controller snippet watching a custom resource, what will happen when a new resource instance is created?

func (r *MyOperatorReconciler) Reconcile(ctx context.Context, req ctrl.Request) (ctrl.Result, error) {
    var app MyApp
    if err := r.Get(ctx, req.NamespacedName, &app); err != nil {
        return ctrl.Result{}, client.IgnoreNotFound(err)
    }
    // Logic to create or update deployment based on app spec
    return ctrl.Result{}, nil
}

medium

A. The Operator will crash due to missing deployment code

B. The Operator will delete the custom resource immediately

C. The Operator will ignore the new resource and do nothing

D. The Operator will create or update a deployment matching the custom resource spec

Solution

1. Step 1: Analyze Reconcile function behavior

   The function fetches the custom resource and applies logic to create or update a deployment accordingly.

2. Step 2: Understand Operator reaction to resource creation

   When a new resource instance is created, the Operator reconciles state by creating/updating deployments to match spec.

3. Final Answer:

   The Operator will create or update a deployment matching the custom resource spec -> Option D

4. Quick Check:

   Reconcile creates/updates deployment = A [OK]

Hint: Reconcile syncs resources to desired state [OK]

Common Mistakes:

• Thinking Operator deletes resource on creation
• Assuming Operator ignores new resources
• Believing missing code causes crash here

4. You wrote an Operator but it never reacts to changes in your custom resource. What is the most likely cause?

medium

A. The Operator's controller is not watching the Custom Resource Definition

B. The Kubernetes cluster is down

C. The custom resource YAML is invalid and rejected

D. The Operator is missing RBAC permissions for Pods

Solution

1. Step 1: Identify why Operator ignores resource changes

   If the controller does not watch the custom resource, it won't get events to trigger reconciliation.

2. Step 2: Compare other options

   Cluster down or invalid YAML would cause errors, not silent ignoring. Missing Pod RBAC affects pod actions, not event watching.

3. Final Answer:

   The Operator's controller is not watching the Custom Resource Definition -> Option A

4. Quick Check:

   Controller watch missing = no reactions = D [OK]

Hint: Ensure controller watches CRD to react to changes [OK]

Common Mistakes:

• Assuming cluster down without checking logs
• Blaming YAML without validation errors
• Confusing RBAC for Pods with watching permissions

5. You want to build an Operator that manages a database cluster with automatic backups and scaling. Which two Kubernetes concepts must you combine to implement this Operator effectively?

hard

A. Custom Resource Definitions and Controllers

B. ConfigMaps and Secrets

C. Ingress and Network Policies

D. DaemonSets and StatefulSets

Solution

1. Step 1: Identify core Operator components

   Operators use Custom Resource Definitions (CRDs) to define new resource types and Controllers to manage their lifecycle.

2. Step 2: Evaluate other Kubernetes concepts

   ConfigMaps and Secrets store config data, Ingress and Network Policies manage traffic, DaemonSets and StatefulSets manage pods but don't implement custom logic.

3. Final Answer:

   Custom Resource Definitions and Controllers -> Option A

4. Quick Check:

   CRDs + Controllers build Operators = C [OK]

Hint: Operators = CRDs + Controllers for custom logic [OK]

Common Mistakes:

• Confusing config storage with Operator logic
• Mixing networking resources with Operator pattern
• Thinking pod controllers alone build Operators