Exam Professional Cloud Developer topic 1 question 258 discussion

Sharing a file is error-prone. Much better to use gcloud command to get the credentials than sharing a file (that could also be a security problem)

C. Ask the developers to install the gcloud CLI on their workstation and run gcloud container clusters get-credentials to switch to another cluster. This approach allows developers to easily switch between clusters while maintaining access to their preferred development tools. The gcloud container clusters get-credentials command updates the kubeconfig file, enabling seamless access to the specified cluster. It is a widely used method that aligns with best practices for managing Kubernetes contexts and simplifies the workflow for developers.

The other options are incorrect because: A: Using Cloud Shell is not a scalable solution for multiple developers who need to switch between clusters regularly. B: While defining clusters, users, and contexts in a configuration file can be helpful, it's not the most efficient or secure way to manage access to multiple clusters. Sharing the configuration file with developers can also pose security risks. D: Opening three terminals for each cluster is cumbersome and not recommended. It's better to use a single tool like the gcloud CLI to manage multiple clusters.

We are talking about an easy way and GKE. Not K8s self-managed. A question detail is that users don't want to change the tolls they use. So C is the right.

B 100% https://kubernetes.io/docs/tasks/access-application-cluster/configure-access-multiple-clusters/

D 100% https://kubernetes.io/docs/tasks/access-application-cluster/configure-access-multiple-clusters/

This approach allows developers to switch between different Google Kubernetes Engine clusters directly from their local workstation1. The gcloud container clusters get-credentials command configures kubectl with the credentials of the specified cluster1, making it easy for developers to switch contexts and interact with different clusters.

https://kubernetes.io/docs/tasks/access-application-cluster/configure-access-multiple-clusters/ Command used: kubectl config use-context

https://kubernetes.io/docs/tasks/access-application-cluster/configure-access-multiple-clusters/

Option B is the best solution because it is secure, convenient, and time-efficient. By using a configuration file, you can define the clusters, users, and contexts that you want to use. You can then share the file with the developers, who can use it to add the cluster, user, and context details to their kubeconfig file. Once the developers have added the cluster, user, and context details to their kubeconfig file, they can switch to another cluster by using the following command: kubectl config use <context-name>