KUBERNETES(1)(kubernetes)

💖 KUBERNETES(1)(kubernetes) 💖

okay bestie, welcome to the kubernetes manual (section 1, obvs) — and today's main character is kubectl create clusterrolebinding. buckle up, we're doing RBAC and we're doing it cutely. ✨

---

✨ NAME ✨

kubectl create clusterrolebinding — Create a cluster role binding for a particular cluster role

---

🌸 SYNOPSIS 🌸

kubectl create clusterrolebinding [OPTIONS]

---

🎀 DESCRIPTION 🎀

Create a cluster role binding for a particular cluster role. that's it, that's the vibe. you're literally just handing a ClusterRole to some users/groups/service accounts and saying "here, you're in the club now". 💅

---

💅 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.
• --clusterrole="" — ClusterRole this ClusterRoleBinding should reference
• --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. (test run energy, no cap 🫶)
• --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.
• -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 current object will be saved in its annotation. Otherwise, the annotation will be unchanged. This flag is useful when you want to perform kubectl apply on this object in the future. (future-proofing, we love to see it)
• --serviceaccount=[] — Service accounts to bind to the clusterrole, in the format :. The flag can be repeated to add multiple service accounts. (ngl the placeholders got eaten in the source, that's literally how it prints 💀)
• --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].
• --user=[] — Usernames to bind to the clusterrole. The flag can be repeated to add multiple users.
• --validate="strict" — Must be one of: strict (or true), warn, ignore (or false). "true" or "strict" will use a schema to validate the input and fail the request if invalid. It will perform server side validation if ServerSideFieldValidation is enabled on the api-server, but will fall back to less reliable client-side validation if 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 behave as "ignore" otherwise. "false" or "ignore" will not perform any schema validation, silently dropping any unknown or duplicate fields. (silently dropping fields?? that's giving "trust me bro", be careful ✋)

---

🌈 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="/home/username/.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. ⚠️ no cap this one is literally insecure, do NOT make it a habit
• --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
• --password="" — Password for basic authentication to the API server
• --profile="none" — Name of profile to capture. One of (none|cpu|heap|goroutine|threadcreate|block|mutex|trace)
• --profile-output="profile.pprof" — Name of the file to write the profile to
• --proxy-url="" — Proxy URL to use for requests to the API server
• --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. (zero = patience of a saint, fr fr)
• -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
• --username="" — Username for basic authentication to the API server
• --version=false — --version, --version=raw prints version information and quits; --version=vX.Y.Z... sets the reported version
• --warnings-as-errors=false — Treat warnings received from the server as errors and exit with a non-zero exit code

---

⭐ EXAMPLE ⭐

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

look at that. clean. iconic. one command and three entities are besties with cluster-admin now. 🔥

---

👑 SEE ALSO 👑

kubectl-create(1),

---

📜 HISTORY 📜

January 2015, Originally compiled by Eric Paris (eparis at redhat dot com) based on the kubernetes source material, but hopefully they have been automatically generated since!

---

and that's a wrap, bestie 🦋 — this page lives in the Manuals / User corner of KUBERNETES(1)(kubernetes), originally compiled Jan 2015 by Eric Paris, and the source version is KUBERNETES(1)(kubernetes). go forth and bind responsibly 💖✨