OC-CREATE-CLUSTERROLE(1)

✨ OC CREATE(1) — clusterrole edition, bestie ✨

Okay so this is oc create clusterrole, and it lives in the Openshift CLI User Manuals family of pages (the OC CREATE(1) squad, iykyk) 💅 It's been around since June 2016 and honestly it still slays.

🌸 NAME 🌸

oc create clusterrole — literally just: create a cluster role. That's the whole vibe. 🎀

🦋 SYNOPSIS 🦋

oc create clusterrole [OPTIONS]

💖 DESCRIPTION 💖

Create a cluster role. That's it, that's the description — short, sweet, main character energy. ✨

🔥 OPTIONS 🔥

• --aggregation-rule= — an aggregation label selector used for combining ClusterRoles together 🫶
• --allow-missing-template-keys=true — if this is true, any errors in templates get ignored when a field or map key is missing from the template. Heads up though: it only applies to golang and jsonpath output formats.
• --dry-run="none" — must be "none", "server", or "client". If it's the client strategy, you only print the object that would be sent, without actually sending it 💀. If it's the server strategy, you submit a server-side request without persisting the resource.
• --field-manager="kubectl-create" — the name of the manager used to track field ownership, bestie.
• --non-resource-url=[] — a partial url that the user should have access to.
• -o, --output="" — output format, pick one pls: (json, yaml, kyaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file) 🌈
• --resource=[] — the resource that the rule applies to.
• --resource-name=[] — resource in the white list that the rule applies to — repeat this flag for multiple items, no cap 🧚
• --save-config=false — if true, the configuration of the current object gets saved in its annotation. Otherwise the annotation stays unchanged. This flag is lowkey useful when you wanna perform kubectl apply on this object later 👑
• --show-managed-fields=false — if true, keep the managedFields when printing objects in JSON or YAML format.
• --template="" — template string or path to a 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⟩ ].
• --validate="ignore" — must be one of: strict (or true), warn, ignore (or false). So "true" or "strict" will use a schema to validate the input and fail the request if it's invalid. It performs server-side validation if ServerSideFieldValidation is enabled on the api-server, but falls back to less reliable client-side validation if it's not 😭. "warn" warns about unknown or duplicate fields without blocking the request if server-side field validation is enabled on the API server, and otherwise behaves as "ignore". And "false" or "ignore" performs no schema validation at all — silently dropping any unknown or duplicate fields 💀
• --verb=[] — the verb that applies to the resources contained in the rule.

🌟 OPTIONS INHERITED FROM PARENT COMMANDS 🌟

• --as="" — username to impersonate for the operation. The 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 won't be checked for validity. > ⚠️ This will make your HTTPS connections insecure, so like… be careful bestie 😭
• --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 by 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 isn't 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 🔥

---

🌈 EXAMPLE 🌈

# Create a cluster role named "pod-reader" that allows user to perform "get", "watch" and "list" on pods
oc create clusterrole pod-reader --verb=get,list,watch --resource=pods

# Create a cluster role named "pod-reader" with ResourceName specified
oc create clusterrole pod-reader --verb=get --resource=pods --resource-name=readablepod --resource-name=anotherpod

# Create a cluster role named "foo" with API Group specified
oc create clusterrole foo --verb=get,list,watch --resource=rs.apps

# Create a cluster role named "foo" with SubResource specified
oc create clusterrole foo --verb=get,list,watch --resource=pods,pods/status

# Create a cluster role name "foo" with NonResourceURL specified
oc create clusterrole "foo" --verb=get --non-resource-url=/logs/*

# Create a cluster role name "monitoring" with AggregationRule specified
oc create clusterrole monitoring --aggregation-rule="rbac.example.com/aggregate-to-monitoring=true"

🫶 SEE ALSO 🫶

• oc-create(1),

💜 HISTORY 💜

June 2016 — Ported from the Kubernetes man-doc generator. So vintage, so iconic. 🎀

---

And that's the whole page, bestie! 🦋 Sourced from Openshift, straight out of the Openshift CLI User Manuals, dated June 2016 — periodt. 💅✨