You are using multiple configurations for gcloud. You want to review the configured Kubernetes Engine cluster of an inactive configuration using the fewest possible steps. What should you do?
You are using multiple configurations for gcloud. You want to review the configured Kubernetes Engine cluster of an inactive configuration using the fewest possible steps. What should you do?
To review the configured Kubernetes Engine cluster of an inactive configuration using the fewest possible steps, you should use the gcloud command-line tool. The command 'gcloud config configurations describe' allows you to directly review the details of a specific configuration, including the Kubernetes Engine cluster configuration, without needing to activate the configuration or switch contexts. This approach is the most efficient and accurate, avoiding unnecessary steps.
D is correct
https://medium.com/google-cloud/kubernetes-engine-kubectl-config-b6270d2b656c explains it well
C is correct , Use kubectl config get-contexts to review the output : shows the clusters and the configurations and based on the output we can identify the inactive configurations
This is wrong get-contexts does not show clusters it only shows contexts.
True . Will give only below results kubectl config get-contexts CURRENT NAME CLUSTER AUTHINFO NAMESPACE * white white dazwilkin black black dazwilkin
kubectl config get-contexts displays a list of contexts as well as the clusters that use them. Here's a sample output.
if anyone need full qtn pdf ping me 2 <a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="4d342c3e253a2c2339253f2c2474790d2a202c2421632e2220">[email protected]</a>
Hi Raikar123 , can you please send me the pdf to <a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="f2999380869a9b99dc81dc82809d949781819b9d9c939eb2959f939b9edc919d9f">[email protected]</a>
Hi Raikar ,please send me the pdf to <a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="f9979a9198979e8f98959580b99e94989095d79a9694">[email protected]</a> thanks in advance
Hello Raikar. Please send me the pdf to <a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="e192808a9289d8d4d0a1868c80888dcf828e8c">[email protected]</a> . Thanks in advance...
Hello Yashwanth, could you please send me the pdf to <a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="1f717e7b7e6d3174316976697a745f78727e7673317c7072">[email protected]</a>
I think is C, due to "using the fewest possible steps". In the D option we have 2 steps. Both C and D are valid, but C is shorter.
A. If we look at B: https://cloud.google.com/sdk/gcloud/reference/config/list - gcloud config list will show name of Kubernetes cluster used by default when working with a profile. https://cloud.google.com/sdk/gcloud/reference/config/configurations/activate - to switch to another profile you need to run gcloud config configurations activate. However, knowing the name of the gcloud profile, we can directly query it using "gcloud config configurations describe <PROFILE NAME> --all", while "gcloud config list" has no option for profile name as argument. If we look at C: "kubectl config get-contexts" will show contexts configured for Kubectl tool, without considering the multiple profiles on gcloud. If we look at D: "kubectl config view" output of this command the same in every selected context, except for the line of "current-context". One command more than in C and it is still not considering the Gcloud profile configurations.
Option A - gcloud config configurations describe <INACTIVE_CONFIGURATION> Seems to be correct as this command directly retrieves the details of the specified inactive configuration, including its Kubernetes Engine cluster configuration, in a single step. It avoids activating the inactive configuration or switching contexts, making it the most efficient and accurate approach. Option D - kubectl config use-context and kubectl config view Also correct but compared to the single command in option A, option D involves two separate commands and potentially an additional step to identify the correct context name for the inactive configuration. Which one to chose? I think A right?
C is the right answer
D is right answer! Get Up-to-date: https://www.pinterest.com/pin/937522847419093171
Correct Answer: D Reference: https://medium.com/google-cloud/kubernetes-engine-kubectl-config-b6270d2b656c
The fewest steps to review the configured Kubernetes Engine cluster of an inactive configuration involve using the gcloud command-line tool and its configuration functionality: 1. Use gcloud config configurations describe: This command displays details about a specific configuration named after your inactive cluster setup. It provides information about the project, compute zone, and other cluster settings without needing to activate it.
Answe C
The correct answer is C. Use kubectl config get-contexts to review the output. (awesome-wares-392903)$ kubectl config get-contexts CURRENT NAME CLUSTER AUTHINFO NAMESPACE The `kubectl config get-contexts` command lists all of the available contexts, including both active and inactive contexts. To review the configured Kubernetes Engine cluster of an inactive configuration, you can use this command to list all of the contexts, and then identify the inactive context that you want to review. The other options are not as good. D is the closest one but it requires an additional step.
D is Answer
The correct answer is C
D should be correct!
The answer cannot be C or D because they are related to kubectl commands, not gcloud commands. Option C suggests using the kubectl config get-contexts command to review the Kubernetes context, which is not related to gcloud configurations. Option D suggests using the kubectl config use-context and kubectl config view commands to review the Kubernetes context, which again is not related to gcloud configurations. Therefore, the correct answer is B, which suggests using gcloud commands to activate the desired configuration and then list the details of the activated configuration, including the configured Kubernetes Engine cluster.
C. Use kubectl config get-contexts to review the output. Option C, using kubectl config get-contexts, allows you to directly see the available contexts, including those from inactive configurations, and review the Kubernetes Engine clusters associated with them. This approach provides the necessary information efficiently. Option D (Use kubectl config use-context and kubectl config view to review the output) involves changing the active context and viewing the Kubernetes configuration but may involve unnecessary steps.