1KUBERNETES(1)                      Jan 2015                      KUBERNETES(1)
2
3
4

NAME

6       kubectl  create  clusterrolebinding - Create a ClusterRoleBinding for a
7       particular ClusterRole
8
9
10

SYNOPSIS

12       kubectl create clusterrolebinding [OPTIONS]
13
14
15

DESCRIPTION

17       Create a ClusterRoleBinding for a particular ClusterRole.
18
19
20

OPTIONS

22       --allow-missing-template-keys=true
23           If true, ignore any errors in templates when a field or map key  is
24       missing  in  the  template.  Only applies to golang and jsonpath output
25       formats.
26
27
28       --clusterrole=""
29           ClusterRole this ClusterRoleBinding should reference
30
31
32       --dry-run=false
33           If true, only print the object that would be sent, without  sending
34       it.
35
36
37       --generator="clusterrolebinding.rbac.authorization.k8s.io/v1alpha1"
38           The name of the API generator to use.
39
40
41       --group=[]
42           Groups to bind to the clusterrole
43
44
45       -o, --output=""
46           Output    format.    One   of:   json|yaml|name|go-template|go-tem‐
47       plate-file|template|templatefile|jsonpath|jsonpath-file.
48
49
50       --save-config=false
51           If true, the configuration of current object will be saved  in  its
52       annotation.  Otherwise,  the annotation will be unchanged. This flag is
53       useful when you want to perform kubectl apply on  this  object  in  the
54       future.
55
56
57       --serviceaccount=[]
58           Service  accounts to bind to the clusterrole, in the format <names‐
59       pace>:<name>
60
61
62       --template=""
63           Template string or path to template file  to  use  when  -o=go-tem‐
64       plate,  -o=go-template-file.  The template format is golang templates [
65http://golang.org/pkg/text/template/#pkg-overview⟩].
66
67
68       --validate=true
69           If true, use a schema to validate the input before sending it
70
71
72

OPTIONS INHERITED FROM PARENT COMMANDS

74       --alsologtostderr=false
75           log to standard error as well as files
76
77
78       --application-metrics-count-limit=100
79           Max number of application metrics to store (per container)
80
81
82       --as=""
83           Username to impersonate for the operation
84
85
86       --as-group=[]
87           Group to impersonate for the operation, this flag can  be  repeated
88       to specify multiple groups.
89
90
91       --azure-container-registry-config=""
92           Path  to the file containing Azure container registry configuration
93       information.
94
95
96       --boot-id-file="/proc/sys/kernel/random/boot_id"
97           Comma-separated list of files to check for boot-id. Use  the  first
98       one that exists.
99
100
101       --cache-dir="/builddir/.kube/http-cache"
102           Default HTTP cache directory
103
104
105       --certificate-authority=""
106           Path to a cert file for the certificate authority
107
108
109       --client-certificate=""
110           Path to a client certificate file for TLS
111
112
113       --client-key=""
114           Path to a client key file for TLS
115
116
117       --cloud-provider-gce-lb-src-cidrs=130.211.0.0/22,209.85.152.0/22,209.85.204.0/22,35.191.0.0/16
118           CIDRs opened in GCE firewall for LB traffic proxy  health checks
119
120
121       --cluster=""
122           The name of the kubeconfig cluster to use
123
124
125       --container-hints="/etc/cadvisor/container_hints.json"
126           location of the container hints file
127
128
129       --containerd="/run/containerd/containerd.sock"
130           containerd endpoint
131
132
133       --containerd-namespace="k8s.io"
134           containerd namespace
135
136
137       --context=""
138           The name of the kubeconfig context to use
139
140
141       --default-not-ready-toleration-seconds=300
142           Indicates   the   tolerationSeconds   of   the    toleration    for
143       notReady:NoExecute  that is added by default to every pod that does not
144       already have such a toleration.
145
146
147       --default-unreachable-toleration-seconds=300
148           Indicates the tolerationSeconds  of  the  toleration  for  unreach‐
149       able:NoExecute  that  is  added  by  default to every pod that does not
150       already have such a toleration.
151
152
153       --docker="unix:///var/run/docker.sock"
154           docker endpoint
155
156
157       --docker-env-metadata-whitelist=""
158           a comma-separated list of environment variable keys that  needs  to
159       be collected for docker containers
160
161
162       --docker-only=false
163           Only report docker containers in addition to root stats
164
165
166       --docker-root="/var/lib/docker"
167           DEPRECATED:  docker  root is read from docker info (this is a fall‐
168       back, default: /var/lib/docker)
169
170
171       --docker-tls=false
172           use TLS to connect to docker
173
174
175       --docker-tls-ca="ca.pem"
176           path to trusted CA
177
178
179       --docker-tls-cert="cert.pem"
180           path to client certificate
181
182
183       --docker-tls-key="key.pem"
184           path to private key
185
186
187       --enable-load-reader=false
188           Whether to enable cpu load reader
189
190
191       --event-storage-age-limit="default=0"
192           Max length of time for which to store events (per type). Value is a
193       comma  separated  list  of  key  values, where the keys are event types
194       (e.g.: creation, oom) or "default" and the value is a duration. Default
195       is applied to all non-specified event types
196
197
198       --event-storage-event-limit="default=0"
199           Max  number  of  events to store (per type). Value is a comma sepa‐
200       rated list of key values, where the keys are event  types  (e.g.:  cre‐
201       ation,  oom)  or  "default"  and  the  value  is an integer. Default is
202       applied to all non-specified event types
203
204
205       --global-housekeeping-interval=1m0s
206           Interval between global housekeepings
207
208
209       --housekeeping-interval=10s
210           Interval between container housekeepings
211
212
213       --insecure-skip-tls-verify=false
214           If true, the server's certificate will not be checked for validity.
215       This will make your HTTPS connections insecure
216
217
218       --kubeconfig=""
219           Path to the kubeconfig file to use for CLI requests.
220
221
222       --log-backtrace-at=:0
223           when logging hits line file:N, emit a stack trace
224
225
226       --log-cadvisor-usage=false
227           Whether to log the usage of the cAdvisor container
228
229
230       --log-dir=""
231           If non-empty, write log files in this directory
232
233
234       --log-file=""
235           If non-empty, use this log file
236
237
238       --log-file-max-size=1800
239           Defines the maximum size a log file can grow to. Unit is megabytes.
240       If the value is 0, the maximum file size is unlimited.
241
242
243       --log-flush-frequency=5s
244           Maximum number of seconds between log flushes
245
246
247       --logtostderr=true
248           log to standard error instead of files
249
250
251       --machine-id-file="/etc/machine-id,/var/lib/dbus/machine-id"
252           Comma-separated list of files to  check  for  machine-id.  Use  the
253       first one that exists.
254
255
256       --match-server-version=false
257           Require server version to match client version
258
259
260       -n, --namespace=""
261           If present, the namespace scope for this CLI request
262
263
264       --password=""
265           Password for basic authentication to the API server
266
267
268       --profile="none"
269           Name of profile to capture. One of (none|cpu|heap|goroutine|thread‐
270       create|block|mutex)
271
272
273       --profile-output="profile.pprof"
274           Name of the file to write the profile to
275
276
277       --request-timeout="0"
278           The length of time to wait before giving  up  on  a  single  server
279       request. Non-zero values should contain a corresponding time unit (e.g.
280       1s, 2m, 3h). A value of zero means don't timeout requests.
281
282
283       -s, --server=""
284           The address and port of the Kubernetes API server
285
286
287       --skip-headers=false
288           If true, avoid header prefixes in the log messages
289
290
291       --skip-log-headers=false
292           If true, avoid headers when opening log files
293
294
295       --stderrthreshold=2
296           logs at or above this threshold go to stderr
297
298
299       --storage-driver-buffer-duration=1m0s
300           Writes in the storage driver will be buffered  for  this  duration,
301       and committed to the non memory backends as a single transaction
302
303
304       --storage-driver-db="cadvisor"
305           database name
306
307
308       --storage-driver-host="localhost:8086"
309           database host:port
310
311
312       --storage-driver-password="root"
313           database password
314
315
316       --storage-driver-secure=false
317           use secure connection with database
318
319
320       --storage-driver-table="stats"
321           table name
322
323
324       --storage-driver-user="root"
325           database username
326
327
328       --token=""
329           Bearer token for authentication to the API server
330
331
332       --update-machine-info-interval=5m0s
333           Interval between machine info updates.
334
335
336       --user=""
337           The name of the kubeconfig user to use
338
339
340       --username=""
341           Username for basic authentication to the API server
342
343
344       -v, --v=0
345           number for the log level verbosity
346
347
348       --version=false
349           Print version information and quit
350
351
352       --vmodule=
353           comma-separated  list  of pattern=N settings for file-filtered log‐
354       ging
355
356
357

EXAMPLE

359                # Create a ClusterRoleBinding for user1, user2, and group1 using the cluster-admin ClusterRole
360                kubectl create clusterrolebinding cluster-admin --clusterrole=cluster-admin --user=user1 --user=user2 --group=group1
361
362
363
364

SEE ALSO

366       kubectl-create(1),
367
368
369

HISTORY

371       January 2015, Originally compiled by Eric Paris (eparis at  redhat  dot
372       com)  based  on the kubernetes source material, but hopefully they have
373       been automatically generated since!
374
375
376
377Eric Paris                  kubernetes User Manuals              KUBERNETES(1)
Impressum