Multi-cluster management concept in Kubernetes - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to list all contexts in your kubeconfig file.

Kubernetes

kubectl config get-contexts [1]

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

A--no-headers

B--list

C--contexts

D--all

Attempts:

3 left

💡 Hint

Common Mistakes

Using --all which is not a valid option here

Using --contexts which is not recognized

Using --list which is not a valid flag for this command

The --no-headers option lists contexts without headers, showing all available contexts clearly.

2fill in blank

medium

Complete the command to switch to a specific cluster context named 'cluster-2'.

Kubernetes

kubectl config [1] cluster-2

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

Aswitch-context

Bset-context

Cchange-context

Duse-context

Attempts:

3 left

💡 Hint

Common Mistakes

Using set-context which configures but does not switch

Using switch-context which is not a kubectl command

Using change-context which is invalid

The use-context command switches your kubectl to the specified cluster context.

3fill in blank

hard

Fix the error in the command to apply a deployment to a specific cluster context.

Kubernetes

kubectl --context=[1] apply -f deployment.yaml

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

Acontext1

Bmy-cluster

Cdefault

Dcluster1

Attempts:

3 left

💡 Hint

Common Mistakes

Using cluster names instead of context names

Using 'default' which may not be the correct context

Using generic names not in kubeconfig

The --context flag requires the exact context name from your kubeconfig, such as 'context1'.

4fill in blank

hard

Fill in the blank to create a kubeconfig file that merges two cluster configs.

Kubernetes

kubectl config [1] --kubeconfig=config1.yaml --kubeconfig=config2.yaml --flatten > merged-config.yaml

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

Aset

Bview

Cget

Duse

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'get' instead of 'view'

Using 'use' which switches context, not merges

Using 'set' which modifies specific config elements

The view command merges multiple kubeconfigs specified via repeated --kubeconfig flags (later files override earlier), and with --flatten outputs a flat config to stdout, redirected to create the merged file.

5fill in blank

hard

Fill all three blanks to create a context named 'prod' for cluster 'cluster-prod' with user 'admin'.

Kubernetes

kubectl config [1] prod --cluster=[2] --user=[3]

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

Aset-context

Bcluster-prod

Cadmin

Duse-context

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'use-context' which switches context but does not create

Mixing cluster and user names

Omitting required flags

The set-context command creates or modifies a context. You specify the cluster and user names accordingly.

Practice

1. What is the main purpose of multi-cluster management in Kubernetes?

easy

A. To control multiple Kubernetes clusters from a single place

B. To create a single large cluster from many nodes

C. To run only one application on a cluster

D. To replace Kubernetes with another system

Solution

1. Step 1: Understand multi-cluster management

   It means managing many Kubernetes clusters together, not just one.

2. Step 2: Identify the main goal

   The goal is to control and coordinate multiple clusters easily from one place.

3. Final Answer:

   To control multiple Kubernetes clusters from a single place -> Option A

4. Quick Check:

   Multi-cluster management = centralized control [OK]

Hint: Think: managing many clusters from one dashboard [OK]

Common Mistakes:

• Confusing multi-cluster with a single large cluster
• Thinking it runs only one app
• Believing it replaces Kubernetes

2. Which kubectl command option lets you switch between clusters in multi-cluster management?

easy

A. kubectl config use-context

B. kubectl switch-cluster

C. kubectl change-cluster

D. kubectl set-cluster

Solution

1. Step 1: Recall kubectl context usage

   Contexts define which cluster and user kubectl talks to.

2. Step 2: Identify correct command to switch context

   kubectl config use-context switches the active cluster context.

3. Final Answer:

   kubectl config use-context -> Option A

4. Quick Check:

   Switch cluster = use-context [OK]

Hint: Use 'kubectl config use-context' to switch clusters [OK]

Common Mistakes:

• Using non-existent commands like switch-cluster
• Confusing set-cluster with switching context
• Trying to change cluster without context

3. Given two clusters with contexts 'cluster1' and 'cluster2', what is the output of this command sequence?

kubectl config use-context cluster2
kubectl get pods

medium

A. Lists pods from cluster1

B. Lists pods from cluster2

C. Shows an error about unknown context

D. Deletes pods from cluster2

Solution

1. Step 1: Switch context to cluster2

   The first command sets the active cluster to cluster2.

2. Step 2: Run 'kubectl get pods'

   This command lists pods in the current active cluster, which is cluster2.

3. Final Answer:

   Lists pods from cluster2 -> Option B

4. Quick Check:

   Context switch affects pod listing cluster [OK]

Hint: After 'use-context', commands run on that cluster [OK]

Common Mistakes:

• Assuming pods list from previous cluster
• Expecting error if context exists
• Thinking get pods deletes pods

4. You try to run kubectl config use-context cluster3 but get an error: "error: no context exists with the name: cluster3". What is the likely cause?

medium

A. kubectl is not installed

B. You need to delete cluster3 first

C. The cluster3 context is not defined in kubeconfig

D. You must restart the Kubernetes cluster

Solution

1. Step 1: Understand the error message

   The error says no context named cluster3 exists in the config file.

2. Step 2: Identify cause

   This means cluster3 was never added or is missing from kubeconfig.

3. Final Answer:

   The cluster3 context is not defined in kubeconfig -> Option C

4. Quick Check:

   Missing context = error on use-context [OK]

Hint: Check kubeconfig for context before switching [OK]

Common Mistakes:

• Assuming kubectl is not installed
• Trying to delete a non-existent context
• Restarting cluster unnecessarily

5. You manage three Kubernetes clusters in different regions. You want to deploy the same app to all clusters and keep configurations consistent. Which approach best fits multi-cluster management?

hard

A. Deploy only to the nearest cluster and ignore others

B. Manually run kubectl commands on each cluster separately

C. Create one huge cluster combining all nodes from regions

D. Use a multi-cluster management tool to deploy and sync configs centrally

Solution

1. Step 1: Understand the goal

   You want consistent app deployment and config across multiple clusters.

2. Step 2: Evaluate options

   Manual commands are error-prone and slow. Combining clusters is not practical. Ignoring clusters misses the goal.

3. Step 3: Identify best practice

   Using a multi-cluster management tool automates deployment and keeps configs synced centrally.

4. Final Answer:

   Use a multi-cluster management tool to deploy and sync configs centrally -> Option D

5. Quick Check:

   Central tool = consistent multi-cluster deployment [OK]

Hint: Automate multi-cluster deploys with management tools [OK]

Common Mistakes:

• Doing manual deploys to each cluster
• Trying to merge clusters into one
• Ignoring clusters outside local region