OC-ADM-POLICY-ADD-CLUSTER-ROLE-TO-USER(1)

💅 OC ADM POLICY(1) — the add-cluster-role-to-user glow-up

okay bestie so listen — this is the OpenShift CLI User Manuals page for oc adm policy add-cluster-role-to-user, straight out of June 2016 (yes she's an elder but she still slays). It's calling from the Openshift manual, one (1) — general commands — and honestly? she ate.

---

✨ NAME ✨

oc adm policy add-cluster-role-to-user — give a role to users across, like, every project in the cluster 🫶

---

🦋 SYNOPSIS 🦋

oc adm policy add-cluster-role-to-user [OPTIONS]

---

🌸 DESCRIPTION 🌸

Add a role to users or service accounts across all projects. All of them. The whole cluster. No cap.

So here's the vibe: this command lets you grant a user access to specific resources and actions within the cluster by assigning them to a role 🔥. It creates or modifies a cluster role binding that references the cluster role you named, and it adds the user(s) or service account(s) to the list of subjects.

And the icon part? This command does not require that the matching cluster role or user/service account resources exist. Like, it will create the binding successfully even when the role doesn't exist, or the user/service account doesn't exist, or when the user doesn't even have access to view them. It literally does not care. Main character energy 💅.

Now — if you pass the --rolebinding-name argument, it'll go looking for an existing cluster role binding with that name. > Heads up though: the role on the matching cluster role binding MUST match the role name you supplied to the command. Not optional. No wiggle room. If you don't give a role binding name, a default name gets used.

Wanna learn more? Go read up on RBAC and policy, or just run the get and describe commands on these resources, bestie:

• clusterroles
• clusterrolebindings
• roles
• rolebindings
• users
• groups
• serviceaccounts

---

🎀 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 it's the client strategy, it only prints the object that would be sent, without sending it. If it's the server strategy, it submits a 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 or create. If left empty, it creates a new rolebindo.RoleBindingNameg with a default name.
• -z, --serviceaccount=[] — service account in the current namespace to use o.SANamess 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 😭 be so careful.
• --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 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 🌈

# Add the 'system:build-strategy-docker' cluster role to the 'devuser' user
oc adm policy add-cluster-role-to-user system:build-strategy-docker devuser

Look at her go 🧚 she's so valid.

---

🍓 SEE ALSO 🍓

• oc-adm-policy(1)

(the comma is canon, we respect it 💀)

---

⭐ HISTORY ⭐

June 2016 — ported from the Kubernetes man-doc generator. A whole vintage era, honestly iconic.

---

and that's the whole page, bestie 💖 brought to you by Openshift under the Openshift CLI User Manuals, dated June 2016 — mwah, go grant some roles responsibly 🎀✨