Explanation:
The correct approach involves using kubectl commands because Kubernetes configurations are managed by kubectl, not gcloud. Option A correctly uses kubectl config use-context to switch to the desired Kubernetes context and kubectl config view to display the configuration details. Other options either use gcloud commands, which do not provide Kubernetes configuration details, or only list contexts without showing configuration details. Remember, kubectl is for Kubernetes configurations, and gcloud is for GCP infrastructure.
Ultimate access to all questions.
No comments yet.
You are managing multiple GCP projects and have set up separate gcloud configurations in your CLI for each project. There's an inactive configuration with a configured Kubernetes Engine cluster. What is the most efficient way to review this Kubernetes configuration?
A
Execute kubectl config use-context followed by kubectl config view to examine the output.
B
Use gcloud config configurations describe to inspect the output.
C
Activate the configuration with gcloud config configurations activate and then list the configuration with gcloud config list.
D
Run kubectl config get-contexts to check the output.