OC-POLICY-ADD-ROLE-TO-GROUP(1)

🎀 NAME — from the OC POLICY(1) manual, June 2016 edition 🎀

This is the oc policy add-role-to-group page (a.k.a. OC-POLICY-ADD-ROLE-TO-GROUP(1)), bestie. The one-line vibe: Add a role to groups for the project. Periodt.

✨ SYNOPSIS ✨

oc policy add-role-to-group [OPTIONS]

🦋 DESCRIPTION 🦋

Okay so this command lets you grant a group access to specific resources and actions within the current project by assigning them to a role. It creates or modifies a role binding referencing the specified role and adding the group(s) to the list of subjects. Think “group chat gets the right access,” and honestly? Iconic.

The command does not require that the matching role or group resources exist. It will create the binding successfully even when the role or group do not exist, or when the user does not have access to view them. Fr fr, that’s literally what it says.

If the --rolebinding-name argument is supplied, it will look for an existing role binding with that name. The role on the matching role binding MUST match the role name supplied to the command. If no role binding name is given, a default name will be used. When --role-namespace argument is specified as a non-empty value, it MUST match the current namespace. When role-namespace is specified, the role binding will reference a namespaced role. Otherwise, the role binding will reference a cluster role resource.

Bestie caveat: those MUSTs are not optional-vibes — they mean it. 💅

To learn more, see information about RBAC and policy, or use the get and describe commands on the following resources: clusterroles, clusterrolebindings, roles, rolebindings, users, groups, and 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 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).
• --role-namespace="" — namespace where the role is located: empty means a role defined in cluster policy.
• --rolebinding-name="" — Name of the rolebinding to modify or create. If left empty creates a new rolebinding with a default name.
• --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.

🔗 SEE ALSO 🔗

• oc-policy(1), — that’s the reference, bestie. Go peek.

📜 HISTORY 📜

June 2016 — Ported from the Kubernetes man-doc generator.

---

That’s the whole page, bestie. Cute footer sign-off: this is Openshift — Openshift CLI User Manuals — page OC POLICY(1), dated June 2016. Byeee, go grant those groups their role 💅✨🫶 slay responsibly 💖