You are a developer at a large corporation. You manage three Google Kubernetes Engine clusters on Google Cloud. Your team’s developers need to switch from one cluster to another regularly without losing access to their preferred development tools. You want to configure access to these multiple clusters while following Google-recommended best practices. What should you do?
The best practice for managing access to multiple Kubernetes clusters on Google Cloud is to use the gcloud CLI. By installing the gcloud CLI on their workstations and running the command gcloud container clusters get-credentials, developers can easily switch between clusters. This method ensures that the kubectl configuration is updated with the correct credentials for the specified cluster, allowing seamless access without changing their preferred development tools.
https://kubernetes.io/docs/tasks/access-application-cluster/configure-access-multiple-clusters/ Command used: kubectl config use-context
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.
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>
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/
Typo - B*
B 100% https://kubernetes.io/docs/tasks/access-application-cluster/configure-access-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.