OC-POLICY-WHO-CAN(1)

🦋 oc policy who-can — the OC POLICY(1) manual, bestie edition 🦋

Okay so welcome to the OC POLICY(1) manual, bestie. This page is all about oc policy who-can, and it’s giving “tell me who can do the thing” energy. 💅

✨ NAME ✨

oc policy who-can — okay so this is the one that lists who can perform the specified action on a resource. No cap. 🫶

🎀 SYNOPSIS 🎀

oc policy who-can [OPTIONS]

💖 DESCRIPTION 💖

Literally: list who can perform the specified action on a resource. That’s the whole vibe of this command, and it ate. 🔥

🌸 OPTIONS 🌸

Here’s the flag menu, bestie — every single one, exactly as it ships:

• -A, --all-namespaces=false — if true, list who can perform the specified action in all namespaces. That’s the all-namespace tea, iykyk. 💅
• --allow-missing-template-keys=true — if true, ignore any errors in templates when a field or map key is missing in the template. Only applies to golang and jsonpath output formats. Periodt.
• -o, --output="" — Output format. One of: (json, yaml, kyaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). Pick your fave, bestie. ✨
• --show-managed-fields=false — if true, keep the managedFields when printing objects in JSON or YAML format.
• --subresource="" — SubResource such as log or scale.
• --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⟩].

🌈 OPTIONS INHERITED FROM PARENT COMMANDS 🌈

These come from the parent commands, and yes, you still need to know them. 💜

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

🦋 SEE ALSO 🦋

Go peek at: oc-policy(1),

👑 HISTORY 👑

Here’s the lore: June 2016, Ported from the Kubernetes man-doc generator.

---

💖 That’s the page, bestie! Source/version vibes: Openshift, from the Openshift CLI User Manuals, dated June 2016. Mwah! 🎀✨