OC-CREATE-CLUSTERROLEBINDING(1)

📦
version 4.22.0 · 2 versions
, in nixpkgs unstable

🎀 oc create clusterrolebinding — the NAME section, bestie 🎀

okay so real quick: this is oc create clusterrolebinding, and it lives in the Openshift CLI User Manuals corner of the universe (yes, those manuals, the Openshift ones, iykyk 💅). Its whole personality? Creating a cluster role binding for a particular cluster role. That's it. That's the girl. ✨

🌸 SYNOPSIS 🌸

oc create clusterrolebinding [OPTIONS]

💖 DESCRIPTION 💖

Create a cluster role binding for a particular cluster role.

fr fr that's the entire description. she's concise, she's iconic, she doesn't over-explain. periodt. 👑

✨ OPTIONS ✨

  • --allow-missing-template-keys=true — If true, it just... ignores any errors in templates when a field or map key is missing in the template. Only applies to golang and jsonpath output formats, no cap.
  • --clusterrole="" — the ClusterRole this ClusterRoleBinding should reference 🫶
  • --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 actually sending it. If it's the server strategy, it submits a server-side request without persisting the resource. literally a vibe check before the real thing.
  • --field-manager="kubectl-create" — Name of the manager used to track field ownership.
  • --group=[] — Groups to bind to the clusterrole. The flag can be repeated to add multiple groups. stack 'em up bestie 💅
  • -o, --output="" — Output format. One of: (json, yaml, kyaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file).
  • --save-config=false — If true, the configuration of the current object gets saved in its annotation. Otherwise the annotation stays exactly how it was. This flag is lowkey useful when you wanna do kubectl apply on this object later. 🔥
  • --serviceaccount=[] — Service accounts to bind to the clusterrole, formatted as <namespace>:<name>. The flag can be repeated to add multiple service accounts.
  • --show-managed-fields=false — If true, keeps 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].
  • --user=[] — Usernames to bind to the clusterrole. The flag can be repeated to add multiple users. yes queen, add as many as you want 🌸
  • --validate="ignore" — Must be one of: strict (or true), warn, ignore (or false). Here's the tea ☕: "true" or "strict" will use a schema to validate the input and fail the request if invalid. It'll do server side validation if ServerSideFieldValidation is enabled on the api-server, but will fall back to less reliable client-side validation if it's not. "warn" will warn about unknown or duplicate fields without blocking the request if server-side field validation is enabled on the API server — and behaves as "ignore" otherwise. "false" or "ignore" will not perform any schema validation at all, silently dropping any unknown or duplicate fields. 🙈

🦋 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. > ⚠️ bestie this will make your HTTPS connections insecure. like, actually insecure. proceed with intent 💀
  • --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. she's patient, okay? 😌
  • -s, --server="" — The address and port of the Kubernetes API server.
  • --tls-server-name="" — Server name to use for server certificate validation. If it's not provided, the hostname used to contact the server is used.
  • --token="" — Bearer token for authentication to the API server.
  • --warnings-as-errors=false — Treat warnings received from the server as errors and exit with a non-zero exit code. harsh but fair 💅

🌈 EXAMPLE 🌈

# Create a cluster role binding for user1, user2, and group1 using the cluster-admin cluster role
oc create clusterrolebinding cluster-admin --clusterrole=cluster-admin --user=user1 --user=user2 --group=group1

look at her go. one command, three subjects bound, zero drama. ate and left no crumbs 🍓

👑 SEE ALSO 👑

💜 HISTORY 💜

June 2016, Ported from the Kubernetes man-doc generator. vintage! a classic! she's been serving since 2016 and she's still booked and busy ✨

mwah, that's the whole page 🫶 this little number ships with Openshift, from the Openshift CLI User Manuals, dated June 2016. go forth and bind those cluster roles, bestie — ily, stay validated (--validate=warn at minimum 🙈) 💖

📦 where this page comes from