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

πŸ“¦
version 4.22.0 Β· 2 versions
, in nixpkgs unstable

πŸ’– OC ADM POLICY(1) πŸ’–

okay bestie, this is oc adm policy add-role-to-group from the OpenShift CLI User Manuals, dated June 2016 ✨ (yes she's an elder icon, we still stan)


✨ NAME ✨

oc adm policy add-role-to-group β€” add a role to groups for the project 🌸


πŸ¦‹ SYNOPSIS πŸ¦‹

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

πŸ’… DESCRIPTION πŸ’…

Add a role to groups for the project. periodt.

So here's the vibe: this command lets you hand a group access to specific resources and actions inside the current project by assigning them to a role πŸ”₯. It creates or modifies a role binding that references the role you picked, and adds the group(s) onto the list of subjects. The way that it does not care whether the matching role or group resources actually exist β€” it will create the binding successfully even when the role or group don't exist, or even when you don't have access to view them πŸ‘€. no cap.

If the --rolebinding-name argument is supplied, it will look for an existing role binding with that name πŸ”. And the role on the matching role binding MUST match the role name you supplied to the command. If no role binding name is given, a default name will be used. And when --role-namespace 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 references a cluster role resource. iykyk.

To learn more, see information about RBAC and policy, or use the get and describe commands on these resources: clusterroles, clusterrolebindings, roles, rolebindings, users, groups, and serviceaccounts. literally the whole squad πŸ’œ


πŸŽ€ 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 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) πŸ¦‹
  • --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 🌈

these are the ones she got from her parent, main character energy πŸ‘‘

  • --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 😭 (pls be careful with this one)
  • --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-adm-policy(1)


πŸ“ HISTORY πŸ“

June 2016, ported from the Kubernetes man-doc generator. she's vintage, she's iconic, she's fr fr πŸŽ€


okay that's the whole thing, go forth and grant those groups their access bestie πŸ’–βœ¨

Openshift β€” Openshift CLI User Manuals β€” OC ADM POLICY(1) 🫢 bye bestie!!

πŸ“¦ where this page comes from