CODEWITHSUNDEEP
kubernetesgoogle-kubernetes-enginekubectl
Jeremy Lewi
Jeremy Lewi

Reputation: 6776

Kubernetes: How do I delete clusters and contexts from kubectl config?

kubectl config view shows contexts and clusters corresponding to clusters that I have deleted.

How can I remove those entries?

The command

kubectl config unset clusters

appears to delete all clusters. Is there a way to selectively delete cluster entries? What about contexts?

Upvotes: 257

Views: 273038

Answers (4)

hpl002
hpl002

Reputation: 619

Unrelated to question, but maybe a useful resource.

Have a look at kubectx + kubens: Power tools for kubectl.

They make it easy to switch contexts and namespace + have the option to delete

Change context:

kubectx dev-cluster-01

Change namespace:

kubens dev-ns-01

Delete context:

kubectx -d dev-cluster-01

Interested in more power tools and plugins for kubectl? Have a look at Krew, the kubectl plugin manager. Cannot recommend this enough.

Upvotes: 39

Khoa
Khoa

Reputation: 1948

Run command below to get all contexts you have:

$ kubectl config get-contexts

CURRENT   NAME             CLUSTER     AUTHINFO                                NAMESPACE

*         Cluster_Name_1   Cluster_1   clusterUser_resource-group_Cluster_1

Delete context:

 $ kubectl config delete-context Cluster_Name_1

Upvotes: 99

Everett Toews
Everett Toews

Reputation: 10974

For clusters and contexts you can also do

kubectl config delete-cluster my-cluster

kubectl config delete-context my-cluster-context

There's nothing specific for users though, so you still have to do

kubectl config unset users.my-cluster-admin

Upvotes: 218

jeffml
jeffml

Reputation: 3681

kubectl config unset takes a dot-delimited path. You can delete cluster/context/user entries by name. E.g.

kubectl config unset users.gke_project_zone_name

kubectl config unset contexts.aws_cluster1-kubernetes

kubectl config unset clusters.foobar-baz

Side note, if you teardown your cluster using cluster/kube-down.sh (or gcloud if you use Container Engine), it will delete the associated kubeconfig entries. There is also a planned kubectl config rework for a future release to make the commands more intuitive/usable/consistent.

Upvotes: 334

Related Questions