Operator SDK basics in Kubernetes - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the command to create a new operator project using Operator SDK.

Kubernetes

operator-sdk init --domain=[1]

Drag options to blanks, or click blank then click option'

Ainit

Boperator

Cexample.com

Dcreate

Attempts:

3 left

💡 Hint

Common Mistakes

Using command words like 'init' or 'create' instead of a domain name.

The operator-sdk init command requires a domain name to initialize the project. Here, example.com is a common placeholder domain.

2fill in blank

medium

Complete the command to create a new API with group 'app' and version 'v1'.

Kubernetes

operator-sdk create api --group=[1] --version=v1 --kind=AppService

Drag options to blanks, or click blank then click option'

Aapp

Bservice

Cv2

Dcore

Attempts:

3 left

💡 Hint

Common Mistakes

Using version or kind names instead of the group name.

The --group flag specifies the API group. Here, it should be app as given in the instruction.

3fill in blank

hard

Fix the error in the command to generate a controller for the kind 'AppService'.

Kubernetes

operator-sdk create controller --kind=[1]

Drag options to blanks, or click blank then click option'

AappService

BAppService

Cappservice

DAppservice

Attempts:

3 left

💡 Hint

Common Mistakes

Using all lowercase or incorrect capitalization for the kind name.

The kind name is case sensitive and should start with a capital letter for each word, so AppService is correct.

4fill in blank

hard

Fill both blanks to build and push the operator image with the correct image name and tag.

Kubernetes

make docker-build docker-push IMG=[1]:[2]

Drag options to blanks, or click blank then click option'

Aquay.io/myrepo/my-operator

Blatest

Cv0.1.0

Dmy-operator

Attempts:

3 left

💡 Hint

Common Mistakes

Using only the operator name without registry, or using 'latest' tag when a version is expected.

The IMG variable needs the full image path including registry and repo, and the tag should be a version like v0.1.0.

5fill in blank

hard

Fill all three blanks to run the operator locally with the correct image, namespace, and watch namespace.

Kubernetes

operator-sdk run local --image=[1] --namespace=[2] --watch-namespace=[3]

Drag options to blanks, or click blank then click option'

Aquay.io/myrepo/my-operator:v0.1.0

Bdefault

Coperators

Dmy-operator:v0.1.0

Attempts:

3 left

💡 Hint

Common Mistakes

Using incomplete image names or wrong namespaces.

The --image flag needs the full image path with tag, --namespace is usually 'default' for local testing, and --watch-namespace is the namespace the operator watches, here 'operators'.

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