OC-CONFIG-USE-CONTEXT(1)

hiii bestie 💖 you're reading the OC CONFIG(1) page from the Openshift CLI User Manuals — yes, the oc config use-context one. it's dated June 2016 and it's here to explain one very specific little kubeconfig move. let's gooo ✨

🌸 NAME 🌸

oc config use-context — set the current-context in a kubeconfig file. that's the whole assignment, no cap 💅

✨ SYNOPSIS ✨

oc config use-context [OPTIONS]

💅 DESCRIPTION 💅

okay so this command sets the current-context in a kubeconfig file. it's giving "make this context the main character" energy, but in a config file. iconic, lowkey 🎀

🎀 OPTIONS INHERITED FROM PARENT COMMANDS 🎀

these are the flags inherited from the parent commands, so they're not unique to use-context — but bestie, they're all here, every single one 🫶

• --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="/homeless-shelter/.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.

bestie, that last one is the danger button 💀 it literally says insecure. don't say i didn't warn you.

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

🦋 EXAMPLE 🦋

                # Use the context for the minikube cluster
                oc config use-context minikube

periodt, that's the flex 🔥

🔥 SEE ALSO 🔥

• oc-config(1),

yes, with the comma — iykyk 🫶

👑 HISTORY 👑

June 2016, Ported from the Kubernetes man-doc generator

---

mwah 💋 this page is from Openshift, part of the Openshift CLI User Manuals, and the date on it is June 2016. byeee bestie, go switch that context 🌈💖