OC-CONFIG-REFRESH-CA-BUNDLE(1)

📦
version 4.22.0 · 2 versions
, in nixpkgs unstable

🌸 OC-CONFIG-REFRESH-CA-BUNDLE 💅

ok so bestie, welcome to the oc config corner of the man pages — this one's from the OpenShift CLI User Manuals, dated June 2016, and it's the glow-up your CA bundle has been waiting for ✨

🎀 NAME 🎀

oc config refresh-ca-bundle — updates your OpenShift CA bundle by, like, actually going and talking to the API server. no cap.

🦋 SYNOPSIS 🦋

oc config refresh-ca-bundle [OPTIONS]

💖 DESCRIPTION 💖

So basically: this command freshens up your CA bundle by reading the content straight from an OpenShift cluster. that's the whole vibe. it goes to the cluster, grabs the goods, and updates your bundle. iconic behavior honestly 🫶

✨ OPTIONS ✨

  • --dry-run=false — shows you the CA bundle (a little preview, a vibe check, if you will) but does not actually change anything in your kubeconfig. pure window shopping 🛍️

🌈 OPTIONS INHERITED FROM PARENT COMMANDS 🌈

these ones come from the parent command — the whole family's invited to the party:

  • --as="" — username to impersonate for the operation. could be a regular user or a service account in a namespace 👑
  • --as-group=[] — group to impersonate for the operation. you can repeat this flag to specify multiple groups, so go off fr fr
  • --as-uid="" — UID to impersonate for the operation
  • --as-user-extra=[] — user extras to impersonate for the operation. repeating the flag lets you specify multiple values for the same key
  • --cache-dir="/homeless-shelter/.kube/cache" — default cache directory. yes that's the literal path, 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, you 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, which makes your HTTPS connections insecure. > ⚠️ bestie this one's giving chaotic energy — "insecure" is right there in the name, proceed with intention 💀
  • --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 by turning off the feature with KUBERC=off
  • --match-server-version=false — require the server version to match the client version
  • -n, --namespace="" — if present, the namespace scope for this CLI request
  • --profile="none" — name of the 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" — how long 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 — the "I'll wait forever, it's fine" setting 🕰️
  • -s, --server="" — the address and port of the Kubernetes API server
  • --tls-server-name="" — server name to use for server certificate validation. if it's 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. harsh but fair ⭐

🔥 EXAMPLE 🔥

here's the part where it all comes together, bestie — copy these exactly:

# Refresh the CA bundle for the current context's cluster
oc config refresh-ca-bundle

# Refresh the CA bundle for the cluster named e2e in your kubeconfig
oc config refresh-ca-bundle e2e

# Print the CA bundle from the current OpenShift cluster's API server
oc config refresh-ca-bundle --dry-run

first one? current context, easy. second one? you're naming the e2e cluster specifically. third one? just peeking with --dry-run, no changes, no consequences 🎀

🧚 SEE ALSO 🧚

go read that one too, it's the parent and it's lowkey giving main character energy 👑

🍓 HISTORY 🍓

June 2016, ported from the Kubernetes man-doc generator. a classic. a vintage. we stan an origin story 💜

and that's the whole page diva 💅 — brought to you by Openshift, from the Openshift CLI User Manuals, dated June 2016, OC CONFIG(1) and out 🦋✨
📦 where this page comes from