Operator SDK basics in Kubernetes - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Operator SDK: Initializing a new operator project

What is the output when you run operator-sdk init --domain=example.com --repo=github.com/example/memcached-operator in an empty directory?

A Creates a new operator project with Go modules initialized and a basic directory structure including API and controllers folders.

B Throws an error because the --repo flag is missing a version number.

C Initializes a Helm chart inside the directory instead of a Go operator project.

D Outputs a warning that the domain is invalid and aborts the initialization.

💡 Hint

The init command sets up the project structure and Go modules for a new operator.

The operator-sdk init command creates a new operator project with the specified domain and repository path. It initializes Go modules and creates folders like api and controllers for further development.

🧠 Conceptual

intermediate

Understanding Operator SDK project structure

Which folder in an Operator SDK Go project contains the Custom Resource Definitions (CRDs) and API types?

A controllers

B api

C config

D build

💡 Hint

Think about where you define the schema and types for your custom resources.

The api folder contains the API definitions and Custom Resource Definitions (CRDs) for the operator. It holds the Go structs that define the custom resource schema.

🔀 Workflow

advanced

Operator SDK: Adding a new API version

You want to add a new version v2 to your existing API group memcached.example.com. Which command correctly adds this new version?

A operator-sdk generate api --group memcached --version v2 --kind Memcached

B operator-sdk add api --group memcached --version v2 --kind Memcached

C operator-sdk init --group memcached --version v2 --kind Memcached

D operator-sdk create api --group memcached --version v2 --kind Memcached --resource --controller

💡 Hint

Use the command that creates API and controller code for a new version.

The create api command adds a new API version and generates resource and controller code. The init command is for project creation, and generate api is not a valid command.

❓ Troubleshoot

advanced

Operator SDK: Debugging a failed operator build

You run make docker-build but get an error: cannot find module providing package sigs.k8s.io/controller-runtime. What is the most likely cause?

A The Go modules are not properly initialized or dependencies are missing in go.mod.

B Docker daemon is not running, so the build cannot access the network.

C The operator-sdk CLI version is outdated and incompatible with the project.

D The Kubernetes cluster is not reachable, causing the build to fail.

💡 Hint

Check if your Go dependencies are correctly set up before building.

The error indicates missing Go dependencies. This usually happens if go.mod or go.sum files are missing or if 'go mod tidy' was not run to fetch dependencies.

✅ Best Practice

expert

Operator SDK: Recommended way to test your operator locally

Which approach is the best practice to test your Operator SDK Go operator locally before deploying to a Kubernetes cluster?

A Build the operator image and push it to Docker Hub, then deploy it to a remote cluster.

B Use <code>operator-sdk test local</code> to run end-to-end tests against a live cluster.

C Run the operator binary locally with <code>make run</code> and connect to a local kind cluster.

D Manually apply CRDs and resources using kubectl without running the operator binary.

💡 Hint

Local testing usually involves running the operator process directly connected to a test cluster.

Running the operator binary locally with 'make run' allows you to debug and test your operator against a local Kubernetes cluster like kind or minikube before building and deploying images.

Practice

1. What is the primary purpose of the Operator SDK in Kubernetes?

easy

A. To monitor network traffic in Kubernetes

B. To replace Kubernetes API server

C. To help automate application management on Kubernetes clusters

D. To create Kubernetes clusters automatically

Solution

1. Step 1: Understand Operator SDK's role

   The Operator SDK is designed to simplify building and managing Kubernetes operators, which automate app lifecycle tasks.

2. Step 2: Compare options

   Options A, B, and C describe unrelated Kubernetes functions, while D correctly states the SDK's purpose.

3. Final Answer:

   To help automate application management on Kubernetes clusters -> Option C

4. Quick Check:

   Operator SDK automates app management = D [OK]

Hint: Remember: Operator SDK automates app tasks on Kubernetes [OK]

Common Mistakes:

• Confusing Operator SDK with Kubernetes cluster creation tools
• Thinking Operator SDK replaces core Kubernetes components
• Assuming it monitors network traffic

2. Which command initializes a new Operator SDK project?

easy

A. operator-sdk create api

B. operator-sdk start

C. kubectl init operator

D. operator-sdk init

Solution

1. Step 1: Identify the command to start a project

   The operator-sdk init command sets up a new operator project structure.

2. Step 2: Eliminate incorrect commands

   create api adds resources, kubectl init operator is invalid, and start is not a recognized init command.

3. Final Answer:

   operator-sdk init -> Option D

4. Quick Check:

   Init command for project setup = B [OK]

Hint: Use 'init' to start your operator project [OK]

Common Mistakes:

• Confusing 'create api' with project initialization
• Using kubectl commands instead of operator-sdk
• Trying 'start' instead of 'init'

3. What will happen if you run operator-sdk create api --group=app --version=v1 --kind=AppService?

medium

A. It creates a new API and resource type named AppService in group app/v1

B. It deletes the existing AppService resource

C. It initializes a new operator project

D. It runs the operator locally

Solution

1. Step 1: Understand the create api command

   The command operator-sdk create api adds a new API resource to the operator project with specified group, version, and kind.

2. Step 2: Analyze the command parameters

   Here, group is 'app', version is 'v1', and kind is 'AppService', so it creates that resource type.

3. Final Answer:

   It creates a new API and resource type named AppService in group app/v1 -> Option A

4. Quick Check:

   Create API command adds resource = A [OK]

Hint: Create API adds resource with group, version, kind [OK]

Common Mistakes:

• Thinking it deletes resources
• Confusing create api with init
• Assuming it runs the operator

4. You ran operator-sdk init --domain=example.com app-operator but got an error. What is a common cause?

medium

A. Missing Go module initialization before running init

B. Using an invalid domain format

C. Not having Kubernetes cluster running

D. Running create api before init

Solution

1. Step 1: Check prerequisites for operator-sdk init

   The Operator SDK requires a Go module initialized (via go mod init) before running init.

2. Step 2: Evaluate other options

   Domain format is usually flexible, Kubernetes cluster is not needed for init, and create api must come after init, not before.

3. Final Answer:

   Missing Go module initialization before running init -> Option A

4. Quick Check:

   Go module must be ready before init = C [OK]

Hint: Always run 'go mod init' before 'operator-sdk init' [OK]

Common Mistakes:

• Ignoring Go module setup
• Assuming cluster must be running for init
• Running create api before init

5. You want to test your operator locally before deploying. Which command should you run?

hard

A. operator-sdk deploy cluster

B. operator-sdk up local

C. kubectl apply -f deploy.yaml

D. operator-sdk create api

Solution

1. Step 1: Identify command for local testing

   The operator-sdk up local command runs the operator locally on your machine for testing.

2. Step 2: Compare other options

   deploy cluster deploys to cluster, kubectl apply applies manifests, and create api adds resources, none run locally.

3. Final Answer:

   operator-sdk up local -> Option B

4. Quick Check:

   Run local command tests operator locally = A [OK]

Hint: Use 'up local' to test operator on your machine [OK]

Common Mistakes:

• Trying to deploy before local testing
• Confusing create api with running operator
• Using kubectl instead of operator-sdk for local run