OC-ADM-POLICY-SCC-SUBJECT-REVIEW(1)

🎀 oc adm policy scc-subject-review — the vibe check for pod creation 💅

okay so bestie, this is the oc adm policy scc-subject-review page from the Openshift CLI User Manuals (that's the manual name, folding it in right here at the top ✨). Buckle up, because this one's basically the bouncer at the club door of your cluster. 👑

---

✨ NAME ✨

oc adm policy scc-subject-review — Check whether a user or a service account can create a pod 🫶

---

🌸 SYNOPSIS 🌸

oc adm policy scc-subject-review [OPTIONS]

---

💖 DESCRIPTION 💖

So here's the tea, bestie: this command checks whether a user, service account or group can create a pod. 🧚 It hands you back a list of security context constraints that will admit the resource — like, "here's who's letting you in, girl."

And the little logic quirks, because they matter, no cap:

• If a user is specified but not groups, it is interpreted as "what if the user is not a member of any groups" 💀
• If user and groups are empty, then the check is performed using the current user 🌈

---

👑 OPTIONS 👑

• --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. 🙈
• -f, --filename=[] — Filename, directory, or URL to files Filename, directory, or URL to a file identifying the resource to get from a server. (yes, the original says it twice — iconic of it, honestly 🎀)
• -g, --groups=[] — Comma separated, list of groups. Review will be performed on behalf of these groups. 💜
• -k, --kustomize="" — Process the kustomization directory. This flag can't be used together with -f or -R. 🚫
• --no-headers=false — When using the default output format, don't print headers (default print headers).
• -o, --output="" — Output format. One of: (json, yaml, kyaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). ✨
• -R, --recursive=false — Process the directory used in -f, --filename recursively. Useful when you want to manage related manifests organized within the same directory. 🦋
• -z, --serviceaccount="" — service account in the current namespace to use as a user 🫶
• --show-managed-fields=false — If true, keep the managedFields when printing objects in JSON or YAML format.
• --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]. 🌸
• -u, --user="" — Review will be performed on behalf of this user 🔥

---

🌈 OPTIONS INHERITED FROM PARENT COMMANDS 🌈

like, these are the family heirlooms, passed down from the parent command 💫

• --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. ⚠️ bestie, this is literally the "ignore the red flags" flag, be careful fr fr
• --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
• --warnings-as-errors=false — Treat warnings received from the server as errors and exit with a non-zero exit code 💀

---

⭐ EXAMPLE ⭐

okay these are the moments, the main character examples 🎬

# Check whether user bob can create a pod specified in myresource.yaml
oc adm policy scc-subject-review -u bob -f myresource.yaml

# Check whether user bob who belongs to projectAdmin group can create a pod specified in myresource.yaml
oc adm policy scc-subject-review -u bob -g projectAdmin -f myresource.yaml

# Check whether a service account specified in the pod template spec in myresourcewithsa.yaml can create the pod
oc adm policy scc-subject-review -f myresourcewithsa.yaml

---

🦋 SEE ALSO 🦋

oc-adm-policy(1), — go read the parent, it's giving fam energy 💖

---

💀 HISTORY 💀

June 2016, Ported from the Kubernetes man-doc generator. vintage, honestly. 🕰️

---

and that's the page bestie!! 🎀 written up in the Openshift CLI User Manuals, source Openshift, dated June 2016 — go forth and review those subjects, you absolute legend 👑✨