OC(1)

🌸 NAME — OC(1) manual 🌸

okay bestie, welcome to the OC(1) manual page — this is the Openshift CLI User Manuals zone, and this page is all about oc logout. It does exactly one iconic thing: end the current server session. That’s the whole vibe 💅✨

🦋 SYNOPSIS 🦋

oc logout [OPTIONS]

💖 DESCRIPTION 💖

Log out of the active session by clearing saved tokens. Simple as that, no cap. 🧚

After login, an authentication token is stored in the config file. This command deletes that token on the server, and then removes the token from the configuration file. So it’s like a two-step goodbye: server-side token gone, then local config token gone. 👋

If you’re using an alternative authentication method like Kerberos or client certificates, your ticket or client certificate will not be removed from the current system, since these are typically managed by other programs. Instead, you can delete your config file to remove the local copy of that certificate or the record of your server login. Important vibe check: this command isn’t gonna clean those up for you. 🙈

After logging out, if you want to log back into the server, use oc login. Easy. 🔥

🌈 OPTIONS INHERITED FROM PARENT COMMANDS 🌈

These flags are inherited from the parent commands, bestie — here’s the full lineup, no skips. 👑

• --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. ⚠️ no cap, that’s a real insecure vibe.
• --kubeconfig="" — path to the kubeconfig file to use for CLI requests. 🗺️
• --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 ⭐

# Log out
oc logout

👀 SEE ALSO 👀

Peep oc(1), too — yes, comma included, that’s canon. 😌

🧚 HISTORY 🧚

June 2016 — Ported from the Kubernetes man-doc generator. 🧚💜

---

💖 sign-off: Openshift / Openshift CLI User Manuals — June 2016 — OC(1). mwah, bestie 🫶