# kubectl create clusterrole 命令详解
创建一个 ClusterRole。
# 语法
$ clusterrole NAME --verb=verb --resource=resource.group [--resource-name=resourcename] [--dry-run]
# 示例
创建一个名为“pod-reader”的 ClusterRole，允许用户在 pod 上执行“get”，“watch”和“list”
kubectl create clusterrole pod-reader --verb=get,list,watch --resource=pods
创建一个名为“pod-reader”的 ClusterRole，其中指定了 ResourceName
kubectl create clusterrole pod-reader --verb=get,list,watch --resource=pods --resource-name=readablepod --resource-name=anotherpod
在指定的 API Group 中创建为"foo"的 ClusterRole
kubectl create clusterrole foo --verb=get,list,watch --resource=rs.extensions
创建一个名为“foo”的 ClusterRole，并指定 SubResource
kubectl create clusterrole foo --verb=get,list,watch --resource=pods,pods/status
使用指定的 NonResourceURL 创建名称“foo”的 ClusterRole
kubectl create clusterrole "foo" --verb=get --non-resource-url=/logs/*
# Flags
| Name | Shorthand | Default | Usage |
|---|---|---|---|
| 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 | false | If true, only print the object that would be sent, without sending it. | |
| no-headers | false | When using the default or custom-column output format, don't print headers (default print headers). | |
| non-resource-url | [] | a partial url that user should have access to. | |
| output | o | Output format. One of: json|yaml|wide|name|custom-columns=...|custom-columns-file=...|go-template=...|go-template-file=...|jsonpath=...|jsonpath-file=... See custom columns [http://kubernetes.io/docs/user-guide/kubectl-overview/#custom-columns], golang template [http://golang.org/pkg/text/template/#pkg-overview] and jsonpath template [http://kubernetes.io/docs/user-guide/jsonpath]. | |
| output-version | DEPRECATED: To use a specific API version, fully-qualify the resource, version, and group (for example: 'jobs.v1.batch/myjob'). | ||
| resource | [] | resource that the rule applies to | |
| resource-name | [] | resource in the white list that the rule applies to, repeat this flag for multiple items | |
| 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. | |
| schema-cache-dir | ~/.kube/schema | If non-empty, load/store cached API schemas in this directory, default is '$HOME/.kube/schema' | |
| show-all | a | false | When printing, show all resources (default hide terminated pods.) |
| show-labels | false | When printing, show all labels as the last column (default hide labels column) | |
| sort-by | If non-empty, sort list types using this field specification. The field specification is expressed as a JSONPath expression (e.g. '{.metadata.name}'). The field in the API resource specified by this JSONPath expression must be an integer or a string. | ||
| 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]. | ||
| validate | true | If true, use a schema to validate the input before sending it | |
| verb | [] | verb that applies to the resources contained in the rule |