1KUBERNETES(1)(kubernetes)                            KUBERNETES(1)(kubernetes)
2
3
4
5Eric Paris Jan 2015
6
7

NAME

9       kubectl create clusterrolebinding - Create a cluster role binding for a
10       particular cluster role
11
12
13

SYNOPSIS

15       kubectl create clusterrolebinding [OPTIONS]
16
17
18

DESCRIPTION

20       Create a cluster role binding for a particular cluster role.
21
22
23

OPTIONS

25       --allow-missing-template-keys=true      If true, ignore any  errors  in
26       templates  when a field or map key is missing in the template. Only ap‐
27       plies to golang and jsonpath output formats.
28
29
30       --clusterrole=""      ClusterRole this ClusterRoleBinding should refer‐
31       ence
32
33
34       --dry-run="none"       Must be "none", "server", or "client". If client
35       strategy, only print the object that would be sent, without sending it.
36       If  server  strategy, submit server-side request without persisting the
37       resource.
38
39
40       --field-manager="kubectl-create"      Name of the manager used to track
41       field ownership.
42
43
44       --group=[]      Groups to bind to the clusterrole
45
46
47       -o,  --output=""      Output format. One of: (json, yaml, name, go-tem‐
48       plate, go-template-file, template, templatefile, jsonpath, jsonpath-as-
49       json, jsonpath-file).
50
51
52       --save-config=false       If  true, the configuration of current object
53       will be saved in its annotation. Otherwise, the annotation will be  un‐
54       changed.  This flag is useful when you want to perform kubectl apply on
55       this object in the future.
56
57
58       --serviceaccount=[]      Service accounts to bind to  the  clusterrole,
59       in the format :
60
61
62       --show-managed-fields=false       If  true, keep the managedFields when
63       printing objects in JSON or YAML format.
64
65
66       --template=""      Template string or path to template file to use when
67       -o=go-template, -o=go-template-file. The template format is golang tem‐
68       plates [http://golang.org/pkg/text/template/#pkg-overview].
69
70
71       --validate="strict"      Must be one of: strict (or true), warn, ignore
72       (or false).            "true" or "strict" will use a schema to validate
73       the input and fail the request if invalid. It will perform server  side
74       validation  if  ServerSideFieldValidation is enabled on the api-server,
75       but will fall back to less  reliable  client-side  validation  if  not.
76                 "warn"  will  warn  about unknown or duplicate fields without
77       blocking the request if server-side field validation is enabled on  the
78       API  server,  and  behave  as "ignore" otherwise.            "false" or
79       "ignore" will not perform any schema validation, silently dropping  any
80       unknown or duplicate fields.
81
82
83

OPTIONS INHERITED FROM PARENT COMMANDS

85       --as=""      Username to impersonate for the operation. User could be a
86       regular user or a service account in a namespace.
87
88
89       --as-group=[]      Group to impersonate for the  operation,  this  flag
90       can be repeated to specify multiple groups.
91
92
93       --as-uid=""      UID to impersonate for the operation.
94
95
96       --azure-container-registry-config=""       Path  to the file containing
97       Azure container registry configuration information.
98
99
100       --cache-dir="/builddir/.kube/cache"      Default cache directory
101
102
103       --certificate-authority=""      Path to a cert file for the certificate
104       authority
105
106
107       --client-certificate=""      Path to a client certificate file for TLS
108
109
110       --client-key=""      Path to a client key file for TLS
111
112
113       --cluster=""      The name of the kubeconfig cluster to use
114
115
116       --context=""      The name of the kubeconfig context to use
117
118
119       --insecure-skip-tls-verify=false      If true, the server's certificate
120       will not be checked for validity. This will make your HTTPS connections
121       insecure
122
123
124       --kubeconfig=""       Path  to  the  kubeconfig file to use for CLI re‐
125       quests.
126
127
128       --match-server-version=false       Require  server  version  to   match
129       client version
130
131
132       -n,  --namespace=""       If  present, the namespace scope for this CLI
133       request
134
135
136       --password=""      Password for basic authentication to the API server
137
138
139       --profile="none"        Name   of   profile   to   capture.   One    of
140       (none|cpu|heap|goroutine|threadcreate|block|mutex)
141
142
143       --profile-output="profile.pprof"       Name  of  the  file to write the
144       profile to
145
146
147       --request-timeout="0"      The length of time to wait before giving  up
148       on  a  single  server  request. Non-zero values should contain a corre‐
149       sponding time unit (e.g. 1s, 2m, 3h). A value of zero means don't time‐
150       out requests.
151
152
153       -s, --server=""      The address and port of the Kubernetes API server
154
155
156       --tls-server-name=""       Server  name  to  use for server certificate
157       validation. If it is not provided, the hostname  used  to  contact  the
158       server is used
159
160
161       --token=""      Bearer token for authentication to the API server
162
163
164       --user=""      The name of the kubeconfig user to use
165
166
167       --username=""      Username for basic authentication to the API server
168
169
170       --version=false      Print version information and quit
171
172
173       --warnings-as-errors=false      Treat warnings received from the server
174       as errors and exit with a non-zero exit code
175
176
177

EXAMPLE

179                # Create a cluster role binding for user1, user2, and group1 using the cluster-admin cluster role
180                kubectl create clusterrolebinding cluster-admin --clusterrole=cluster-admin --user=user1 --user=user2 --group=group1
181
182
183
184

SEE ALSO

186       kubectl-create(1),
187
188
189

HISTORY

191       January 2015, Originally compiled by Eric Paris (eparis at  redhat  dot
192       com)  based  on the kubernetes source material, but hopefully they have
193       been automatically generated since!
194
195
196
197Manuals                              User            KUBERNETES(1)(kubernetes)
Impressum