gke-gcloud-auth-plugin: Support CLOUDSDK_CONFIG env var

[rustycl0ck]

Currently if I have two google accounts [email protected] and [email protected], with single GKE cluster in each account, then I can not use the current gke-gcloud-auth-plugin easily because it does not take into consideration the CLOUDSDK_CONFIG env var¹ which points to my current active account.

Two issues here:

1. $ gke-gcloud-auth-plugin always prints the cache value of ~/.kube/gke_gcloud_auth_plugin_cache even if I authenticated with a different account now
2. If I manually export CLOUDSDK_AUTH_ACCESS_TOKEN=$(gcloud auth print-access-token) to override the cache, then it still tries to find ADC credentials in ~/.config/gcloud/application_default_credentials.json but I have set CLOUDSDK_CONFIG to something other than ~/.config/gcloud, so it fails with the following error:

   $ kubectl get pods
   F0530 19:01:25.377398   43950 cred.go:145] print credential failed with error: Failed to retrieve access token:: getting google default token failed after multiple retries: cannot construct google default token source: google: could not find default credentials. See https://developers.google.com/accounts/docs/application-default-credentials for more information.
   Unable to connect to the server: getting credentials: exec: executable gke-gcloud-auth-plugin failed with exit code 1

Footnotes

1. https://cloud.google.com/sdk/docs/configurations ↩

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[rustycl0ck]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten