OC-CREATE-ROLEBINDING(1)

📦
version 4.22.0 · 2 versions
, in nixpkgs unstable

💖 NAME 💖

okay so this is the OC CREATE(1) manual page for oc create rolebinding — June 2016 edition, bestie — and it's literally: Create a role binding for a particular role or cluster role. slay. ✨

🦋 SYNOPSIS 🦋

oc create rolebinding [OPTIONS]

no cap, that's the whole vibe. 💅

🌸 DESCRIPTION 🌸

Create a role binding for a particular role or cluster role. that's it, that's the main character energy. 👑

✨ OPTIONS ✨

  • --allow-missing-template-keys=true — if this is 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. lowkey forgiving, we love that. 🫶
  • --clusterrole="" — the ClusterRole this RoleBinding 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. bestie, it's giving "preview mode" but make it official. 💅
  • --field-manager="kubectl-create" — name of the manager used to track field ownership. 🎀
  • --group=[] — Groups to bind to the role. The flag can be repeated to add multiple groups. yes, repeat it, we love a list. 🌈
  • -o, --output="" — Output format. One of: (json, yaml, kyaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). pick your aesthetic, fr fr. ✨
  • --role="" — Role this RoleBinding should reference. 🎯
  • --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-you says thank you. 💖
  • --serviceaccount=[] — Service accounts to bind to the role, in the format <namespace>:<name>. The flag can be repeated to add multiple service accounts. iconic format, no notes. 👑
  • --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]. template girlies rise. 🧚
  • --user=[] — Usernames to bind to the role. The flag can be repeated to add multiple users. add them all, bestie. 🌸
  • --validate="ignore" — 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. read that twice, bestie, it's important. 😭

🔮 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. main character switch-up. 🎭
  • --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. yes, that path is real. 🏠
  • --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. uncompressed and unbothered. 💅
  • --insecure-skip-tls-verify=false — If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure. 🚨 bestie, 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. noted. 📝
  • --match-server-version=false — Require server version to match client version. matchy-matchy. 🪞
  • -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). pick your profile era. 📊
  • --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. zero means no timeout, no cap. ⏳
  • -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. 🎟️
  • --warnings-as-errors=false — Treat warnings received from the server as errors and exit with a non-zero exit code. dramatic? maybe. effective? yes. 💀

🌟 EXAMPLE 🌟

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

# Create a role binding for service account monitoring:sa-dev using the admin role
oc create rolebinding admin-binding --role=admin --serviceaccount=monitoring:sa-dev

look at that syntax, ate and left no crumbs. 🔥

👀 SEE ALSO 👀

the see-also is literally just oc-create(1), — short, sweet, iconic. 🎀

📜 HISTORY 📜

June 2016, Ported from the Kubernetes man-doc generator. vintage lore, honestly. 🕰️

bye bestie 💖 — cute little sign-off from the Openshift / Openshift CLI User Manuals corner: OC CREATE(1), June 2016. periodt. 🌈✨

📦 where this page comes from