OC-ADM-POLICY-REMOVE-CLUSTER-ROLE-FROM-USER(1)

🫶 NAME 🫶

okay so bestie, welcome to the OC ADM POLICY(1) page for oc adm policy remove-cluster-role-from-user — and the whole vibe is literally Remove a role from users for all projects in the cluster. cluster-wide, no cap. 💅

✨ SYNOPSIS ✨

oc adm policy remove-cluster-role-from-user [OPTIONS]

🦋 DESCRIPTION 🦋

so yeah, this command removes a role from users for all projects in the cluster. it’s giving “one role, every project” energy, and that is the entire description. periodt. 🫶

🌸 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.
• --dry-run="none" — Must be "none", "server", or "client". If client strategy, only print the object that would be sent, without sending it. If server strategy, submit server-side request without persisting the resource.
• -o, --output="" — Output format. One of: (json, yaml, kyaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file).
• --rolebinding-name="" — Name of the rolebinding to modify. If left empty it will operate on all rolebindings.
• -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].

🧚 OPTIONS INHERITED FROM PARENT COMMANDS 🧚

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

💜 EXAMPLE 💜

here’s the glow-up in action, bestie:

# Remove the 'system:build-strategy-docker' cluster role from the 'devuser' user
oc adm policy remove-cluster-role-from-user system:build-strategy-docker devuser

👑 SEE ALSO 👑

• oc-adm-policy(1), — peep the parent command page too, iykyk. 🫶

🌈 HISTORY 🌈

the lore is: June 2016, Ported from the Kubernetes man-doc generator. iconic. 🎀

---

mwah 💋 — brought to you by Openshift and the Openshift CLI User Manuals, dated June 2016. 💖