KUBERNETES(1)(kubernetes)

✨ NAME ✨

kubectl config delete-cluster β€” delete the specified cluster from the kubeconfig, bestie πŸ’…

(so yeah, this whole thing lives in the KUBERNETES(1) manual, aka the kubernetes manual β€” that's the manual name, now you know 🫢)


🌸 SYNOPSIS 🌸

kubectl config delete-cluster [OPTIONS]

πŸ’– DESCRIPTION πŸ’–

Okay so literally all this does: it deletes the cluster you name from the kubeconfig. That's it. That's the whole vibe. Gone. Bye. Not me manifesting a clean kubeconfig ✨


πŸŽ€ OPTIONS INHERITED FROM PARENT COMMANDS πŸŽ€

These are the flags you didn't ask for but got anyway, because parent commands said "here, take these too" πŸ‘‘

  • --as="" β€” the username you're impersonating for this operation. Could be a regular user, could be a service account in a namespace. main character energy, but borrowed πŸ‘‘
  • --as-group=[] β€” the group you're impersonating for this operation. You can repeat this flag to specify multiple groups, so go off, stack 'em 🌈
  • --as-uid="" β€” the UID you're impersonating for this operation. yes, a UID. slay.
  • --as-user-extra=[] β€” user extras to impersonate for this operation. Repeat the flag to specify multiple values for the same key. lowkey thorough πŸ’œ
  • --cache-dir="/home/username/.kube/cache" β€” the default cache directory. that's the default, fr fr
  • --certificate-authority="" β€” path to a cert file for the certificate authority πŸŽ€
  • --client-certificate="" β€” path to a client certificate file for TLS
  • --client-key="" β€” path to a client key file for TLS
  • --cluster="" β€” the name of the kubeconfig cluster to use
  • --context="" β€” the name of the kubeconfig context to use
  • --disable-compression=false β€” if true, opt out of response compression for all requests to the server. if false (the default), compression stays on 🫢
  • --insecure-skip-tls-verify=false β€” if true, the server's certificate will not be checked for validity. and like… that makes your HTTPS connections insecure. no cap, that's literally what it does 😭 be careful bestie
  • --kubeconfig="" β€” use a particular kubeconfig file
  • --kuberc="" β€” path to the kuberc file to use for preferences. you can disable this by exporting the KUBECTL_KUBERC=false feature gate, or by turning off the feature with KUBERC=off ✨
  • --match-server-version=false β€” require server version to match client version. strict queen πŸ‘‘
  • -n, --namespace="" β€” if present, the namespace scope for this CLI request
  • --password="" β€” password for basic authentication to the API server πŸ™ˆ
  • --profile="none" β€” name of the profile to capture. one of (none|cpu|heap|goroutine|threadcreate|block|mutex|trace) πŸ“
  • --profile-output="profile.pprof" β€” name of the file to write the profile to
  • --proxy-url="" β€” proxy URL to use for requests to the API server
  • --request-timeout="0" β€” how long to wait before giving up on a single server request. non-zero values should contain a corresponding time unit (like 1s, 2m, 3h). a value of zero means don't timeout requests β€” zero means infinite patience, iconic ⭐
  • -s, --server="" β€” the address and port of the Kubernetes API server
  • --tls-server-name="" β€” server name to use for server certificate validation. if it's not provided, the hostname used to contact the server is used
  • --token="" β€” bearer token for authentication to the API server πŸ”₯
  • --user="" β€” the name of the kubeconfig user to use
  • --username="" β€” username for basic authentication to the API server
  • --version=false β€” --version, --version=raw prints version information and quits; --version=vX.Y.Z... sets the reported version πŸ’«
  • --warnings-as-errors=false β€” treat warnings received from the server as errors and exit with a non-zero exit code. dramatic? yes. effective? also yes πŸ’€

🌈 EXAMPLE 🌈

the way that you just run it with the cluster name and it's done πŸ¦‹
# Delete the minikube cluster
kubectl config delete-cluster minikube

🧚 SEE ALSO 🧚

  • kubectl-config(1), β€” go read that one too, bestie, it's the whole family πŸ’œ

πŸ’€ HISTORY πŸ’€

January 2015, originally compiled by Eric Paris (eparis at redhat dot com) based on the kubernetes source material, but hopefully they have been automatically generated since! πŸ™ˆ like, fingers crossed, no manual labour here


and that's the whole page β€” KUBERNETES(1)(kubernetes), User manual, and yes the author credit up top is Eric Paris, Jan 2015 πŸ’– periodt, you're welcome, go delete that cluster πŸ‘‘
πŸ“¦ where this page comes from