OC-CONFIG-GET-USERS(1)

📦
version 4.22.0 · 2 versions
, in nixpkgs unstable

💅 OC CONFIG GET-USERS(1) 💅

Okay bestie, buckle up — this is the oc config manual page, and we're about to get into the users of your kubeconfig. It's giving "who even are these people" energy, and honestly? Iconic.

✨ NAME ✨

oc config get-users — displays the users defined in the kubeconfig. That's it. That's the whole vibe. 🫶

🦋 SYNOPSIS 🦋

oc config get-users [OPTIONS]

Simple slay. No cap.

🌸 DESCRIPTION 🌸

So like, this command literally just displays the users defined in the kubeconfig. That's the tea. It's a quick little peek at who's who in your cluster config — main character energy only. 💅✨

🎀 OPTIONS INHERITED FROM PARENT COMMANDS 🎀

These flags are inherited from the parent command, meaning oc config is sharing its whole wardrobe with get-users. Generous queen behavior. 👑

  • --as="" — Username to impersonate for the operation. User could be a regular user or a service account in a namespace. Basically cosplay, but for auth. 🎭
  • --as-group=[] — Group to impersonate for the operation. This flag can be repeated to specify multiple groups. Stack 'em up, bestie. 🫶
  • --as-uid="" — UID to impersonate for the operation. Numeric identity theft, but make it legal. 🔢
  • --as-user-extra=[] — User extras to impersonate for the operation. This flag can be repeated to specify multiple values for the same key. Extra? In this economy? We love to see it. 💖
  • --cache-dir="/homeless-shelter/.kube/cache" — Default cache directory. Yes, that's the actual default path. Not me questioning it, just reporting the facts. 🏠😭
  • --certificate-authority="" — Path to a cert file for the certificate authority. Trust issues? Solved. 🔐
  • --client-certificate="" — Path to a client certificate file for TLS. Your TLS flex, bestie. 📜
  • --client-key="" — Path to a client key file for TLS. Guard this with your life, fr fr. 🔑
  • --cluster="" — The name of the kubeconfig cluster to use. Pick your fighter. ⚔️
  • --context="" — The name of the kubeconfig context to use. Context is everything, literally. 🧠
  • --disable-compression=false — If true, opt-out of response compression for all requests to the server. Sometimes you just want the raw, uncompressed truth. 💀
  • --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, I am begging you — know what you're doing before you flip this one. This is not a drill. 🚨
  • --kubeconfig="" — Use a particular kubeconfig file. Choose your own adventure. 📂
  • --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. Feature gate lore, iykyk. 🧚
  • --match-server-version=false — Require server version to match client version. Strict queen behavior. 👑
  • -n, --namespace="" — If present, the namespace scope for this CLI request. Because location matters. 📍
  • --profile="none" — Name of profile to capture. One of (none|cpu|heap|goroutine|threadcreate|block|mutex). Pick your poison, bestie — the options are giving ✨variety✨. 🔬
  • --profile-output="profile.pprof" — Name of the file to write the profile to. Where the data goes to live its best life. 📝
  • --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. Patient queen energy only. ⏳
  • -s, --server="" — The address and port of the Kubernetes API server. Slide into the server's DMs. 📡
  • --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. Default behavior, but make it fashion. 🎀
  • --token="" — Bearer token for authentication to the API server. Your VIP pass. Keep it secret, keep it safe. 🎟️
  • --user="" — The name of the kubeconfig user to use. Calling all users, please stand up. 🙋‍♀️
  • --warnings-as-errors=false — Treat warnings received from the server as errors and exit with a non-zero exit code. Strict mode activated. 💅

🔥 EXAMPLE 🔥

Okay so the manpage shows this example — literally just:

# List the users that oc knows about
oc config get-users

And that's it. That's the whole tutorial. Iconic simplicity. 🎀

🌈 SEE ALSO 🌈

  • oc-config(1) — the parent command, the mothership, the main character of this whole saga. 👑

💜 HISTORY 💜

June 2016, Ported from the Kubernetes man-doc generator. A vintage moment, honestly. 🍓

And that's the tea, bestie! This page was brought to you by Openshift and the Openshift CLI User Manuals, dated June 2016. Go forth and know your users. 💖✨🦋

📦 where this page comes from