Comments (15)
@arekkusu In order to reset the token, after set account
you need to run rm $HOME/.kube/gke_gcloud_auth_plugin_cache
, so the plugin will not reuse cached token.
Thanks for the hint with CLOUDSDK_CORE_ACCOUNT
, I can use it as a temporary workaround until the account
option is implemented.
from cloud-provider-gcp.
@darklore It would be slightly better, but still gke-gcloud-auth-plugin
needs to keep multiple caches of the token to make work efficient (in either one file or multiple files, maybe prefixed with account name?)
from cloud-provider-gcp.
#473 Should solve this issue
from cloud-provider-gcp.
gcloud config set account ...
Do you mean running gcloud config set account...
followed by gcloud container clusters get-credentials ...
?
(I don't think setting the account alone is enough, when I tested gke-gcloud-auth-plugin
always returned the same token)
FYI you can do this to get cluster credential while setting (overwriting) the account using env variable:
[email protected]; gcloud container clusters get-credentials log
The above + some bash scripting (or kubectl wrapper or even addon may work as a workaround.
In any case I agree it would be nice if gke-gcloud-auth-plugin
could add support for this.
from cloud-provider-gcp.
Is it helpful to you to use CLOUDSDK_CORE_ACCOUNT in .kube/config
?
Such like
users:
- name: user
user:
exec:
apiVersion: client.authentication.k8s.io/v1beta1
command: gke-gcloud-auth-plugin
env:
- name: CLOUDSDK_CORE_ACCOUNT
value: [email protected]
from cloud-provider-gcp.
Yes. I agree.
from cloud-provider-gcp.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs 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 or PR as fresh with
/remove-lifecycle stale
- Mark this issue or PR as rotten with
/lifecycle rotten
- Close this issue or PR with
/close
- Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
from cloud-provider-gcp.
/remove-lifecycle stale
from cloud-provider-gcp.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs 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 or PR as fresh with
/remove-lifecycle stale
- Mark this issue or PR as rotten with
/lifecycle rotten
- Close this issue or PR with
/close
- Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
from cloud-provider-gcp.
/remove-lifecycle stale
from cloud-provider-gcp.
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
from cloud-provider-gcp.
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
from cloud-provider-gcp.
this already work for Google Cloud SDK 428.0.0
account can be specified for user in kube config
- name: USER_ALIAS
user:
exec:
apiVersion: client.authentication.k8s.io/v1beta1
args:
- [email protected]
command: gke-gcloud-auth-plugin
env: null
installHint: Install gke-gcloud-auth-plugin for use with kubectl by following
https://cloud.google.com/blog/products/containers-kubernetes/kubectl-auth-changes-in-gke
interactiveMode: IfAvailable
provideClusterInfo: true
from cloud-provider-gcp.
/close
from cloud-provider-gcp.
@zshihang: Closing this issue.
In response to this:
/close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
from cloud-provider-gcp.
Related Issues (20)
- TEST ISSUE 2 HOT 2
- go.sum is out of sync (requires go 1.20?) HOT 6
- Make `crd/apis` a Go module? HOT 6
- Remove Bazel from cloud-provider-gcp and use make to build it HOT 4
- Cloud.InstanceID() does not actually return a unique Instance ID HOT 16
- The networking logic to detect preempted VMs based on the node.Spec.PodCIDR values is not generalizable HOT 2
- The cloud-controller-manager relies on the `system:serviceaccount:kube-system:cloud-provider` principal which is deprecated HOT 3
- Internal Loadbalancers don't work if a cluster is using custom mode subnets HOT 7
- The worker number for controllers should be configurable HOT 5
- Error: failed to get instance metadata HOT 9
- GNP controller does not log API errors HOT 5
- Remove backends from backend services before updating HOT 7
- RFE: Enable logging via service annotations for load balancer backends HOT 7
- `gke-gcloud-auth-plugin`: Support passing credentials via a specific JSON filepath HOT 3
- Add DevContainer Definitons For One-Click Dev Env Setup HOT 6
- Working example doc HOT 4
- CAPG: Upstream CCM manifest doesn't work HOT 7
- Create documentation for setting up and using the out-of-tree provider HOT 7
- Failure when trying to run kubetest2 --up with gcp in non-legacy mode HOT 2
- Cluster self healing have not works with Cilium CNI HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from cloud-provider-gcp.