OC-CONFIG-SET(1)

🎀 oc config set — OC-CONFIG-SET(1) 🎀

hiii bestie 💖 welcome to the oc config set page, living its best life in the Openshift CLI User Manuals. this is the manual for setting one individual value inside a kubeconfig file, and yes she ate. 🫶

🌸 NAME 🌸

oc config set — set an individual value in a kubeconfig file. that's it, that's the name, mwah. 💅

✨ SYNOPSIS ✨

oc config set [OPTIONS]

🦋 DESCRIPTION 🦋

okay so the whole point: set an individual value in a kubeconfig file. 🎀

PROPERTY_NAME is a dot delimited name where each token represents either an attribute name or a map key. map keys may not contain dots. no cap, dots are banned in map keys. 😭

PROPERTY_VALUE is the new value you want to set. binary fields such as 'certificate-authority-data' expect a base64 encoded string unless the --set-raw-bytes flag is used. so if you're not using that flag, base64 it, bestie. 🧚

if you specify an attribute name that already exists, it will merge new fields on top of existing values. it's giving "layering", not replacing. ✨

💅 OPTIONS 💅

only one option in this section, and she's lowkey iconic:

• --set-raw-bytes=false — when writing a []byte PROPERTY_VALUE, write the given string directly without base64 decoding. default is false. 🫶

🫶 OPTIONS INHERITED FROM PARENT COMMANDS 🫶

okay these are inherited from the parent command — not invented by oc config set, just passed down like a group-chat forward. 💌

• --as="" — username to impersonate for the operation. the 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="/homeless-shelter/.kube/cache" — default cache directory. that path is literally in the default, don't come for me. 🧚
• --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. 📛
• --profile="none" — name of profile to capture. one of (none|cpu|heap|goroutine|threadcreate|block|mutex).
• --profile-output="profile.pprof" — name of the file to write the profile to.
• --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.
• --warnings-as-errors=false — treat warnings received from the server as errors and exit with a non-zero exit code. 💀

⚠️ bestie, --insecure-skip-tls-verify is literally the dangerous one: when true, your HTTPS connections are insecure because the server's certificate is not checked for validity. 😭

🌈 EXAMPLE 🌈

these examples are exactly the commands, bestie — copy them character for character:

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

# Set the certificate-authority-data field on the my-cluster cluster
oc 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
oc config set contexts.my-context.cluster my-cluster

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

👀 SEE ALSO 👀

• oc-config(1), — go look, bestie. 👑

📜 HISTORY 📜

June 2016, Ported from the Kubernetes man-doc generator. periodt. 💖

---

xoxo 💅 from Openshift — Openshift CLI User Manuals, June 2016 edition. OC CONFIG(1) vibes, rewritten with love for you, bestie. 🎀✨