OC-AUTH-WHOAMI(1)

πŸ“¦
version 4.22.0 Β· 2 versions
, in nixpkgs unstable

πŸ’… OC-AUTH-WHOAMI(1) β€” like, the whole manual but make it make sense πŸŽ€

okay so real talk, this is from the OpenShift CLI User Manuals (Openshift), and the page is titled OC AUTH(1). Buckle up bestie, we're going on a ✨journey✨.


🌸 NAME 🌸

oc auth whoami β€” Experimental: check your own self subject attributes πŸ’–

(yeah, experimental, she's still figuring herself out, we support her 🫢)


πŸ¦‹ SYNOPSIS πŸ¦‹

oc auth whoami [OPTIONS]

✨ DESCRIPTION ✨

Experimental: check who you are and what your attributes are β€” that's your groups and your extra πŸŽ€

This command is literally there to help you get yourself aware of the current user attributes, especially when dynamic authentication is enabled in the Kubernetes cluster β€” and by dynamic auth we mean things like a token webhook, an auth proxy, or an OIDC provider. iykyk 🧚


πŸ’… OPTIONS πŸ’…

  • --allow-missing-template-keys=true β€” if true, ignore any errors in templates when a field or map key is missing from the template. only applies to golang and jsonpath output formats, no cap.
  • -o, --output="" β€” output format, bestie. one of: (json, yaml, kyaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file).
  • --show-managed-fields=false β€” if true, keep the managedFields when printing objects in JSON or YAML format. slay.
  • --template="" β€” template string or path to template file to use when -o=go-template, -o=go-template-file. the template format is golang templates [http://golang.org/pkg/text/template/#pkg-overview]. iconic.

🌈 OPTIONS INHERITED FROM PARENT COMMANDS 🌈

these are the ones she got from her mom, we don't question it 🫢

  • --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 β€” like, actually insecure, not in a cute way 😭
  • --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 the KUBECTL_KUBERC=false feature gate, or by turning off the feature with 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. harsh but fair πŸ’€

πŸ”₯ EXAMPLE πŸ”₯

# Get your subject attributes
oc auth whoami

# Get your subject attributes in JSON format
oc auth whoami -o json

πŸ‘‘ SEE ALSO πŸ‘‘


πŸŽ€ HISTORY πŸŽ€

June 2016 β€” Ported from the Kubernetes man-doc generator. retro era fr fr πŸ¦‹


okay that's the whole page, you ate that πŸ’… main character energy only. this was Openshift (OpenShift CLI User Manuals), version/date June 2016, manual OC AUTH(1) β€” periodt. πŸŒΈπŸ’–βœ¨

πŸ“¦ where this page comes from