Open upodroid opened 1 year ago
cc @chaodaiG @cjwagner
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/priority important-longterm
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:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
@upodroid [edit: is this] still important with the migration? (not sure what we settled on in k8s-infra)
It is important, Argo is configured to access clusters using gke-auth plugin and we want prow to do the same as well
The new gke auth plugin doesn't store access tokens in the kubeconfig file.
Intree gcp plugin used to do the following which wasn't great.
Related to https://github.com/kubernetes/test-infra/issues/27896
/sig testing /sig k8s-infra