OC-CONFIG-SET-CLUSTER(1)

📦
version 4.22.0 · 2 versions
, in nixpkgs unstable

💖 OC-CONFIG-SET-CLUSTER(1) 💖

okay so like, hi bestie!! 🫶 this is a page from the OC CONFIG manual (yes, that's the manual name, iconic), and honestly it's giving "i'm about to make your kubeconfig slay" energy. let's get into it ✨

🌸 NAME 🌸

oc config set-cluster — literally sets a cluster entry in kubeconfig. that's the whole vibe. no cap. 👑

🦋 SYNOPSIS 🦋

oc config set-cluster [OPTIONS]

✨ DESCRIPTION ✨

Set a cluster entry in kubeconfig. periodt. 💅

and here's the tea 🍓: specifying a name that already exists will merge new fields on top of existing values for those fields. so it doesn't nuke your old stuff, it just layers the new stuff on top. lowkey considerate of it tbh.

💜 OPTIONS 💜

  • --certificate-authority="" — path to the certificate-authority file for the cluster entry in kubeconfig. like, where your CA lives. 🎀
  • --embed-certs=false — embed-certs for the cluster entry in kubeconfig. defaults to false, obviously.
  • --insecure-skip-tls-verify=false — insecure-skip-tls-verify for the cluster entry in kubeconfig. also false by default, bestie.
  • --proxy-url="" — proxy-url for the cluster entry in kubeconfig.
  • --server="" — server for the cluster entry in kubeconfig. the main character of your cluster config ngl. ⭐
  • --tls-server-name="" — tls-server-name for the cluster entry in kubeconfig.

🌈 OPTIONS INHERITED FROM PARENT COMMANDS 🌈

so these aren't even this command's own flags, they're just ✨ inherited ✨ from the parent command like family heirlooms. we love a legacy. 🧚

  • --as="" — username to impersonate for the operation. user could be a regular user or a service account in a namespace. iyk what that means (iykyk 😌)
  • --as-group=[] — group to impersonate for the operation. this flag can be repeated to specify multiple groups. repeat away bestie 💅
  • --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. yes, that's the actual path, don't come for me, i just work here 😭
  • --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.
  • --kubeconfig="" — use a particular kubeconfig file.
  • --kuberc="" — path to the kuberc file to use for preferences. this can be disabled by exporting the KUBECTL_KUBERC=false feature gate or turning off the feature KUBERC=off. head's up fr fr 🫶
  • --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). pick your fighter 🥊
  • --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. so "0" is just vibes, forever 💀
  • --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. strict queen behavior 👑

🎀 EXAMPLE 🎀

here's where it gets fun, bestie. these are verbatim, so copy-paste responsibly 🫶

# Set only the server field on the e2e cluster entry without touching other values
oc config set-cluster e2e --server=https://1.2.3.4

# Embed certificate authority data for the e2e cluster entry
oc config set-cluster e2e --embed-certs --certificate-authority= /.kube/e2e/kubernetes.ca.crt

# Disable cert checking for the e2e cluster entry
oc config set-cluster e2e --insecure-skip-tls-verify=true

# Set the custom TLS server name to use for validation for the e2e cluster entry
oc config set-cluster e2e --tls-server-name=my-cluster-name

# Set the proxy URL for the e2e cluster entry
oc config set-cluster e2e --proxy-url=https://1.2.3.4

look at that. five examples. five little icons. we ate. 🔥

🦋 SEE ALSO 🦋

go check out the parent, it's giving "the whole family tree" energy 🌸

💖 HISTORY 💖

June 2016, Ported from the Kubernetes man-doc generator. vintage!! a classic. 🎀

okay that's the whole page, bestie, you're officially educated ✨💅 and real quick, the cute little sign-off at the bottom of the original said Openshift, Openshift CLI User Manuals, and OC CONFIG(1) — that's the source/version info + footer — and it's dated June 2016. slay. 🫶💜

📦 where this page comes from