Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

j3ffml
Copy link
Contributor

@j3ffml j3ffml commented Aug 22, 2015

@j3ffml
Copy link
Contributor Author

j3ffml commented Aug 22, 2015

Closes #13060

@k8s-bot
Copy link

k8s-bot commented Aug 22, 2015

GCE e2e build/test failed for commit cd69a4e5f4fbb2670a19e074f8039a9caba081cb.

@k8s-bot
Copy link

k8s-bot commented Aug 22, 2015

GCE e2e build/test passed for commit 4382168.

@thockin
Copy link
Member

thockin commented Aug 22, 2015

LGTM, but what will this do to people who have more than one cluster of a particular provider (e.g. dev and e2e)?

@j3ffml
Copy link
Contributor Author

j3ffml commented Aug 22, 2015

Multiple clusters will get different credentials, even if they are the same provider. Arguably, that is the correct approach anyway. Note that this doesn't mean that the older cluster credentials get overwritten; if you have e.g. a 'dev' and 'e2e' gce cluster, you will have 2 kubeconfig entries for them, and can switch between them by using kubectl config use-context

@thockin thockin added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Aug 24, 2015
@thockin
Copy link
Member

thockin commented Aug 24, 2015

lgtm

nikhiljindal added a commit that referenced this pull request Aug 24, 2015
Don't reuse credentials on cluster create
@nikhiljindal nikhiljindal merged commit 411d78d into kubernetes:master Aug 24, 2015
@j3ffml j3ffml deleted the no-reuse-auth branch August 28, 2015 01:44
mikedanese added a commit that referenced this pull request Sep 16, 2015
…13068-upstream-release-1.0

Automated cherry pick of #13068
@ikehz ikehz mentioned this pull request Oct 27, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lgtm "Looks good to me", indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants