OC-ADM-POLICY(1)
π OC ADM(1) β the oc adm policy glow-up π
okay so bestie, this is the OpenShift CLI User Manuals page for oc adm policy, dated June 2016 β yes she's an elder but she still ate, and we're gonna get into it β¨
πΈ NAME πΈ
oc adm policy β manage cluster authorization and security policy, aka the vibe check for who's allowed to do what on your cluster π«Ά
β SYNOPSIS β
oc adm policy [OPTIONS]
that's it. that's the whole synopsis. iconic behavior honestly π
π DESCRIPTION π
Manage policy on the cluster, periodt.
These commands let you assign and manage the roles and policies that apply to users. The reconcile commands are the little glow-up commands β they let you reset and upgrade your system policies to the latest default policies. it's giving "new year new me" but for your cluster π
and if you want more info on roles and bindings? use the get and describe commands on these resources, bestie:
clusterrolesclusterrolebindingsrolesrolebindingsscc
that's the whole roster. know them, love them, describe them π
β¨ OPTIONS INHERITED FROM PARENT COMMANDS β¨
these are the flags she inherited from her parent commands β nepotism baby but make it kubeconfig π all of them are still very much main character, so here we go:
--as=""β the username to impersonate for the operation. User could be a regular user or a service account in a namespace π--as-group=[]β the group to impersonate for the operation. this flag can be repeated to specify multiple groups, slay π--as-uid=""β the 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. yes the default path literally sayshomeless-shelter, i don't make the rules π--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β iftrue, opt-out of response compression for all requests to the server.--insecure-skip-tls-verify=falseβ iftrue, the server's certificate will not be checked for validity. this will make your HTTPS connections insecure β be so serious rn, only do this if you know exactly what you're doing π--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 exportingKUBECTL_KUBERC=falsefeature gate or turning off the featureKUBERC=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). pick your fighter π--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 β she waits forever, loyal queen π-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 π¦
the whole friend group, fr fr β go read these too:
oc-adm(1)oc-adm-policy-add-cluster-role-to-group(1)oc-adm-policy-add-cluster-role-to-user(1)oc-adm-policy-add-role-to-group(1)oc-adm-policy-add-role-to-user(1)oc-adm-policy-add-scc-to-group(1)oc-adm-policy-add-scc-to-user(1)oc-adm-policy-remove-cluster-role-from-group(1)oc-adm-policy-remove-cluster-role-from-user(1)oc-adm-policy-remove-group(1)oc-adm-policy-remove-role-from-group(1)oc-adm-policy-remove-role-from-user(1)oc-adm-policy-remove-scc-from-group(1)oc-adm-policy-remove-scc-from-user(1)oc-adm-policy-remove-user(1)oc-adm-policy-scc-review(1)oc-adm-policy-scc-subject-review(1)oc-adm-policy-who-can(1)
like, that's a whole friend group and every single one of them matters π
π HISTORY π
June 2016 β Ported from the Kubernetes man-doc generator. a true vintage moment, we respect the lore π«Ά
and that's the page bestie!! this was Openshift β Openshift CLI User Manuals β OC ADM(1), born June 2016 and still serving looks. mwah, go manage those policies πβ¨
π¦ where this page comes from
- nixpkgs unstable: openshift 4.22.0-202605222050
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms