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

NAME

9       kubectl create deployment - Create a deployment with the specified name
10
11
12

SYNOPSIS

14       kubectl create deployment [OPTIONS]
15
16
17

DESCRIPTION

19       Create a deployment with the specified name.
20
21
22

OPTIONS

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

OPTIONS INHERITED FROM PARENT COMMANDS

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

EXAMPLE

176                # Create a deployment named my-dep that runs the busybox image
177                kubectl create deployment my-dep --image=busybox
178
179                # Create a deployment with a command
180                kubectl create deployment my-dep --image=busybox -- date
181
182                # Create a deployment named my-dep that runs the nginx image with 3 replicas
183                kubectl create deployment my-dep --image=nginx --replicas=3
184
185                # Create a deployment named my-dep that runs the busybox image and expose port 5701
186                kubectl create deployment my-dep --image=busybox --port=5701
187
188
189
190

SEE ALSO

192       kubectl-create(1),
193
194
195

HISTORY

197       January  2015,  Originally compiled by Eric Paris (eparis at redhat dot
198       com) based on the kubernetes source material, but hopefully  they  have
199       been automatically generated since!
200
201
202
203Manuals                              User            KUBERNETES(1)(kubernetes)
Impressum