Kubectl configuration for GKE in GCP - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Configuration

intermediate

Understanding the kubectl context after GKE cluster creation

After creating a new GKE cluster, you run kubectl config get-contexts. What does the output show?

A An error saying no contexts are configured yet

B Only the new GKE cluster context without any other contexts

C A list of all Kubernetes contexts including the new GKE cluster context with its cluster and user info

D A list of all pods running in the default namespace

💡 Hint

Think about what kubectl config get-contexts shows in general.

The command kubectl config get-contexts lists all contexts in your kubeconfig file, including the new GKE cluster context after configuration.

❓ service_behavior

intermediate

Effect of running 'gcloud container clusters get-credentials' on kubectl

What happens when you run gcloud container clusters get-credentials my-cluster --zone us-central1-a --project my-project?

A It updates your kubeconfig file to add credentials and context for the specified GKE cluster

B It creates a new GKE cluster named 'my-cluster' in the specified zone

C It deletes the kubeconfig file and resets kubectl configuration

D It lists all running pods in the 'my-cluster' cluster

💡 Hint

Consider what the command name suggests about credentials and configuration.

This command fetches cluster credentials and updates your local kubeconfig so kubectl can communicate with the GKE cluster.

❓ security

advanced

Identifying security risks in kubeconfig file sharing

You share your kubeconfig file with a colleague. What is a potential security risk of this action?

A The colleague can access your GKE cluster with your permissions, possibly causing unintended changes

B The kubeconfig file will automatically expire and become unusable after 24 hours

C Sharing kubeconfig files is safe because they contain only public information

D The colleague can only view cluster metadata but cannot make changes

💡 Hint

Think about what credentials and permissions kubeconfig files hold.

Kubeconfig files contain credentials and tokens that allow full access to the cluster as per your permissions, so sharing them can lead to unauthorized access.

❓ Architecture

advanced

How kubectl communicates with a GKE cluster

Which component does kubectl communicate with directly to manage resources in a GKE cluster?

A The Google Cloud Storage bucket linked to the cluster

B The Google Cloud Console web interface

C The GKE master node's operating system shell

D The Kubernetes API server running inside the GKE cluster

💡 Hint

Consider what kubectl commands like kubectl get pods interact with.

Kubectl sends requests to the Kubernetes API server, which manages the cluster state and resources.

✅ Best Practice

expert

Best practice for managing multiple GKE cluster contexts in kubectl

You manage multiple GKE clusters across projects and regions. What is the best practice to avoid confusion when switching between clusters using kubectl?

A Manually edit the kubeconfig file to remove unused clusters each time

B Use descriptive context names and switch contexts explicitly with <code>kubectl config use-context</code>

C Delete all other contexts except the one you are currently using

D Always run <code>gcloud container clusters get-credentials</code> before every kubectl command

💡 Hint

Think about how kubectl manages multiple cluster connections.

Using clear context names and switching contexts explicitly helps avoid mistakes and keeps your workflow organized.