Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

./gcp-deployer delete doesn't clean up context #111

Closed
wangzhen127 opened this issue Apr 26, 2018 · 1 comment
Closed

./gcp-deployer delete doesn't clean up context #111

wangzhen127 opened this issue Apr 26, 2018 · 1 comment
Assignees

Comments

@wangzhen127
Copy link
Contributor

It seems that the kubernetes context is not removed after deleting the cluster using gcp-deployer.

To reproduce:

$ ./gcp-deployer delete
$ kubectl config get-contexts

You will see

CURRENT   NAME                          CLUSTER      AUTHINFO           NAMESPACE
*         kubernetes-admin@kubernetes   kubernetes   kubernetes-admin 

I expect at least it is not the current context, or the context is removed.

@roberthbailey
Copy link
Contributor

Closing this since we are deleting gcp-deployer. Please re-open if this is still an issue with clusterctl delete (which just merged today).

/close

chuckha pushed a commit to chuckha/cluster-api that referenced this issue Oct 2, 2019
jayunit100 pushed a commit to jayunit100/cluster-api that referenced this issue Jan 31, 2020
In the "MachineSpec" one can specify the labels, taints. In this
patch we use the kubelet args to bootstrap the node with the provided
taints and labels

Resolves kubernetes-sigs#111
Change-Id: Id184e1148c8f6149c9faa40cb382bf740210bba5
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants