Multi-cluster management concept in Kubernetes - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is the primary benefit of using a multi-cluster management tool in Kubernetes?

Choose the main advantage of managing multiple Kubernetes clusters with a dedicated multi-cluster management tool.

A It replaces the need for namespaces within a single cluster.

B It automatically upgrades all clusters to the latest Kubernetes version without manual intervention.

C It allows centralized control and consistent policy enforcement across all clusters.

D It eliminates the need for kubeconfig files on client machines.

💡 Hint

Think about how managing many clusters can be simplified.

Multi-cluster management tools provide a central place to control and apply policies consistently across clusters, improving operational efficiency.

💻 Command Output

intermediate

Output of kubectl config get-contexts with multiple clusters

What is the output of the command kubectl config get-contexts when you have two clusters named cluster1 and cluster2 configured?

Kubernetes

kubectl config get-contexts

A

CURRENT   NAME        CLUSTER     AUTHINFO    NAMESPACE
*         cluster2    cluster2    user2       default
          cluster1    cluster1    user1       default

B

NAME        CLUSTER     AUTHINFO    NAMESPACE
cluster1    cluster1    user1       default
cluster2    cluster2    user2       default

C Error: no contexts found

D

CURRENT   NAME        CLUSTER     AUTHINFO    NAMESPACE
*         cluster1    cluster1    user1       default
          cluster2    cluster2    user2       default

💡 Hint

Look for the current context marked with an asterisk (*) and the order of contexts.

The output lists all contexts with the current one marked by '*'. The order usually shows the current context first.

❓ Configuration

advanced

Correct YAML snippet for deploying a multi-cluster service mesh

Which YAML snippet correctly configures a service mesh control plane to manage multiple Kubernetes clusters?

A

apiVersion: install.istio.io/v1alpha1
kind: IstioOperator
spec:
  meshConfig:
    enableAutoMtls: true
  components:
    pilot:
      enabled: true
  values:
    global:
      multiCluster:
        clusterName: cluster1

B

apiVersion: v1
kind: Service
metadata:
  name: multi-cluster-mesh
spec:
  type: LoadBalancer
  ports:
  - port: 15012
    targetPort: 15012

C

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: multi-cluster-ingress
spec:
  rules:
  - host: cluster1.example.com
    http:
      paths:
      - path: /
        pathType: Prefix
        backend:
          service:
            name: mesh-control-plane
            port:
              number: 80

D

apiVersion: apps/v1
kind: Deployment
metadata:
  name: multi-cluster-controller
spec:
  replicas: 1
  selector:
    matchLabels:
      app: controller
  template:
    metadata:
      labels:
        app: controller
    spec:
      containers:
      - name: controller
        image: controller:latest

💡 Hint

Look for a configuration that enables multi-cluster in a service mesh control plane.

Option A shows an IstioOperator resource enabling multi-cluster features, which is correct for service mesh multi-cluster setup.

❓ Troubleshoot

advanced

Troubleshooting failed multi-cluster kubeconfig context switch

You try to switch context to a remote cluster using kubectl config use-context remote-cluster but get the error error: context "remote-cluster" does not exist. What is the most likely cause?

A The current user does not have permission to switch contexts.

B The kubeconfig file does not have a context named "remote-cluster" defined.

C The kubectl version is incompatible with the remote cluster version.

D The remote cluster is down and unreachable.

💡 Hint

Check if the context is defined in your kubeconfig file.

The error means the context name is not found in the kubeconfig file, so kubectl cannot switch to it.

🔀 Workflow

expert

Correct order to deploy a multi-cluster application with centralized config

Arrange the steps in the correct order to deploy an application across multiple Kubernetes clusters using a centralized configuration management tool.

A 1,2,3,4

B 2,1,3,4

C 3,2,1,4

D 1,3,2,4

💡 Hint

Think about defining config first, then setting access, then deploying sync, then verifying.

You first define what to deploy, then set up access, then deploy the sync tool, and finally check the results.