KUBERNETES(1)(kubernetes)

✨ KUBERNETES(1)(kubernetes) ✨

okay bestie, welcome to the kubectl config rename-context page 💖 this is part of the kubernetes manual, and it's literally just about giving one of your contexts a glow-up name change. no cap.

written by the one and only Eric Paris, January 2015 🫶

---

🌸 NAME 🌸

kubectl config rename-context — Rename a context from the kubeconfig file

---

🎀 SYNOPSIS 🎀

kubectl config rename-context [OPTIONS]

---

💅 DESCRIPTION 💅

So here's the vibe: this command renames a context from the kubeconfig file. that's it. that's the whole thing. iconic behavior fr fr.

CONTEXT_NAME is the context name that you want to change. like, the one you're renaming from.

NEW_NAME is the new name you want to set. the glow-up name. the main character name. ✨

Note: if the context being renamed is the 'current-context', this field will also be updated. so no, you don't have to re-select it after. it follows you, like a loyal bestie 🦋

---

🔥 OPTIONS INHERITED FROM PARENT COMMANDS 🔥

these are the flags you get handed down from the parent commands, and there are a LOT of them, so buckle up babes 🌈

• --as="" — Username to impersonate for the operation. User could be a regular user or a service account in a namespace.
• --as-group=[] — Group to impersonate for the operation, this flag can be repeated to specify multiple groups.
• --as-uid="" — UID to impersonate for the operation.
• --as-user-extra=[] — User extras to impersonate for the operation, this flag can be repeated to specify multiple values for the same key.
• --cache-dir="/home/username/.kube/cache" — Default cache directory
• --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
• --insecure-skip-tls-verify=false — If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure
• --kubeconfig="" — use a particular kubeconfig file
• --kuberc="" — Path to the kuberc file to use for preferences. This can be disabled by exporting KUBECTL_KUBERC=false feature gate or turning off the feature KUBERC=off.
• --match-server-version=false — Require server version to match client version
• -n, --namespace="" — If present, the namespace scope for this CLI request
• --password="" — Password for basic authentication to the API server
• --profile="none" — Name of 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" — The length of time to wait before giving up on a single server request. Non-zero values should contain a corresponding time unit (e.g. 1s, 2m, 3h). A value of zero means don't timeout requests.
• -s, --server="" — The address and port of the Kubernetes API server
• --tls-server-name="" — Server name to use for server certificate validation. If it is 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

heads up bestie: that --insecure-skip-tls-verify one is literally telling your client "yeah idc if this cert is valid" — your HTTPS connections become insecure. be so for real before you turn that on. 💀

---

🦋 EXAMPLE 🦋

  # Rename the context 'old-name' to 'new-name' in your kubeconfig file
  kubectl config rename-context old-name new-name

look at that. old-name walked in, new-name walked out. slay. 👑

---

⭐ SEE ALSO ⭐

• kubectl-config(1)

---

💜 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!

---

and that's a wrap on the manual page, bestie!! 🎀 this lil doc is filed under the Manuals manual, in the User section, and it's from the KUBERNETES(1)(kubernetes) era — so yeah, 2015 energy with 2025 kubeconfigs. obsessed. bye now, go rename something. 💖✨🫶