KUBERNETES(1)(kubernetes)

🎀 kubectl config set 🎀

okay bestie, welcome to the kubernetes manual page for kubectl config set. it's giving tiny command, big power. grab a strawberry 🍓 and let's do some kubeconfig surgery.

---

🌸 NAME 🌸

kubectl config set — Set an individual value in a kubeconfig file. literally just one value. that's the whole assignment. slay.

---

✨ SYNOPSIS ✨

kubectl config set [OPTIONS]

---

💖 DESCRIPTION 💖

So you wanna change one little thing inside a kubeconfig file? that's the vibe. this is the command. 💅

PROPERTY_NAME is a dot delimited name where each token represents either an attribute name or a map key. and listen, this part is important: map keys may not contain dots. no dots in the map keys. none. not even one. 🙈

PROPERTY_VALUE is the new value you want to set. now for the binary fields, like 'certificate-authority-data', they expect a base64 encoded string — unless you're using the --set-raw-bytes flag, in which case it doesn't. iykyk. 🧚

and here's the cute part: if you specify an attribute name that already exists, it will merge new fields on top of existing values. not overwrite, not delete, just layering. it's giving main character energy on top of your old data. ✨

---

🦋 OPTIONS 🦋

• --set-raw-bytes=false — when writing a []byte PROPERTY_VALUE, write the given string directly, without base64 decoding it. no decoding, no detour, just vibes straight to disk. 🔥

---

🔥 OPTIONS INHERITED FROM PARENT COMMANDS 🔥

these are the family traits, bestie — they come from the parent command, not from this one, but they work here too:

• --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: --insecure-skip-tls-verify=true means the server's certificate is not checked for validity, and that makes your HTTPS connections insecure. that's not a cute risk, that's a real one. 💀

---

🌈 EXAMPLE 🌈

the receipts, straight from the source, no edits:

# Set the server field on the my-cluster cluster to https://1.2.3.4
kubectl config set clusters.my-cluster.server https://1.2.3.4

# Set the certificate-authority-data field on the my-cluster cluster
kubectl config set clusters.my-cluster.certificate-authority-data $(echo "cert_data_here" | base64 -i -)

# Set the cluster field in the my-context context to my-cluster
kubectl config set contexts.my-context.cluster my-cluster

# Set the client-key-data field in the cluster-admin user using --set-raw-bytes option
kubectl config set users.cluster-admin.client-key-data cert_data_here --set-raw-bytes=true

look at those dot delimited names. <pink>clusters</pink>.<pink>my-cluster</pink>.<pink>server</pink> — beautiful. periodt. 💅

---

👑 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. this one came out of the kubernetes manual — section 1, the Manuals collection, filed under User — dated Jan 2015, with the header credit to Eric Paris. go forth and set exactly one value at a time. you got this. 🫶✨