KUBERNETES(1)(kubernetes)

💅 NAME 💅

kubectl auth — bestie, this is the vibe check for authorization. Like, who's allowed to do what? Let's find out. ✨

---

🦋 SYNOPSIS 🦋

kubectl auth [OPTIONS]

---

🎀 DESCRIPTION 🎀

Inspect authorization. That's the whole thing, no cap — it's your little detective moment where you go peek at what permissions exist and who's got them. Iconic behavior, honestly. 💖

---

👑 OPTIONS INHERITED FROM PARENT COMMANDS 👑

These are the ones you got handed down from the parent command, like family heirlooms but for flags. 🫶

• --as="" — Username you're impersonating for this operation. Could be a regular user, could be a service account chillin' in a namespace. Either way, you're cosplaying as them. 💅
• --as-group=[] — Group you're impersonating for the operation. Repeat this flag as many times as you want to stack up multiple groups. ✨
• --as-uid="" — The UID you're impersonating for the operation.
• --as-user-extra=[] — Extra user stuff to impersonate for the operation. Repeat the flag to give multiple values for the same key. 🔁
• --cache-dir="/home/username/.kube/cache" — The default cache directory. Cozy little home for your cached stuff. 🏠
• --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 every single request to the server. Raw dogging the bytes, as it were. 😭
• --insecure-skip-tls-verify=false — If true, the server's certificate will not be checked for validity. This makes your HTTPS connections insecure. Genuinely dangerous, bestie — do not do this casually. 💀
• --kubeconfig="" — Path to the kubeconfig file to use for CLI requests.
• --kuberc="" — Path to the kuberc file to use for preferences. You can turn this off by exporting the KUBECTL_KUBERC=false feature gate, or by switching off the feature with KUBERC=off. 🎛️
• --match-server-version=false — Require the server version to match the client version. Matchy matchy, no mismatches allowed. 👯
• -n, --namespace="" — If present, this sets the namespace scope for this CLI request.
• --password="" — Password for basic authentication to the API server.
• --profile="none" — Name of the profile to capture. One of (none|cpu|heap|goroutine|threadcreate|block|mutex|trace). Pick your fighter. ⚔️
• --profile-output="profile.pprof" — Name of the file to write the profile to.
• --proxy-url="" — Proxy URL to use for requests to the API server.
• --request-timeout="0" — How long to wait before giving up on a single server request. Non-zero values should contain a corresponding time unit (like 1s, 2m, 3h). A value of zero means don't timeout requests at all — infinite patience, main character energy. 🧘‍♀️
• -s, --server="" — The address and port of the Kubernetes API server.
• --tls-server-name="" — Server name to use for server certificate validation. If you don't provide it, the hostname used to contact the server gets used instead.
• --token="" — Bearer token for authentication to the API server. 🎟️
• --user="" — The name of the kubeconfig user to use.
• --username="" — Username for basic authentication to the API server.
• --version=false — --version, --version=raw prints version information and quits; --version=vX.Y.Z... sets the reported version. Tell me who you are, queen. 👑
• --warnings-as-errors=false — Treat warnings received from the server as errors and exit with a non-zero exit code. No more "lol whatever" — warnings become full-on drama. 🚨

---

🌈 SEE ALSO 🌈

Go read these next, they're all in the same friend group:

• kubectl(1)
• kubectl-auth-can-i(1)
• kubectl-auth-reconcile(1)
• kubectl-auth-whoami(1)

---

💖 HISTORY 💖

January 2015 — originally compiled by Eric Paris (eparis at redhat dot com), based on the kubernetes source material. But hopefully they've been automatically generated since! 🙈 (Which, honestly? Growth. We love to see it.)

---

And that's a wrap, bestie — this page came to you from the Manuals source, User section, under KUBERNETES(1)(kubernetes). Slay responsibly. 💅✨