KUBERNETES(1)(kubernetes)

👑 KUBERNETES(1) — kubectl config set-context 💅

okay bestie, buckle up, we're in the kubernetes manual, section 1, and this page is literally just about one little command that goes so hard. written by Eric Paris, Jan 2015, and it still eats. 🎀

---

✨ NAME ✨

kubectl config set-context — Set a context entry in kubeconfig

like. that's it. that's the whole job. and she does it flawlessly. 💖

---

🌸 SYNOPSIS 🌸

kubectl config set-context [OPTIONS]

---

🦋 DESCRIPTION 🦋

Set a context entry in kubeconfig. 🫶

And here's the tea: if you specify a name that already exists, it doesn't nuke it, it merges — new fields get layered on top of the existing values for those fields. iconic behavior, honestly. no notes. ✨

---

💅 OPTIONS 💅

• --cluster="" — the cluster for the context entry in kubeconfig
• --current=false — Modify the current context 👀
• -n, --namespace="" — the namespace for the context entry in kubeconfig
• --user="" — the user for the context entry in kubeconfig

---

🌈 OPTIONS INHERITED FROM PARENT COMMANDS 🌈

these are the ones she got from her mom (the parent command). they're all still valid, so don't skip them, fr fr.

• --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
• --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

okay bestie, real talk on that last one: setting it true means your HTTPS connections are insecure. like, no validity check at all. do not be casual about that one. 😭

• --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
• --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
• --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

---

🎀 EXAMPLE 🎀

the moment you've all been waiting for. she ate and left no crumbs:

  # Set the user field on the gce context entry without touching other values
  kubectl config set-context gce --user=cluster-admin

see how she only touched --user? everything else stayed exactly where it was. merge behavior supremacy. 👑

---

🔥 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 the whole page bestie, you're so welcome. this came out of the Manuals source, in the User section, filed under KUBERNETES(1)(kubernetes). mwah. 💋🦋💖