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

NAME

9       kubectl create cronjob - Create a cron job with the specified name
10
11
12

SYNOPSIS

14       kubectl create cronjob [OPTIONS]
15
16
17

DESCRIPTION

19       Create a cron job 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 name 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       --restart=""       job's  restart  policy. supported values: OnFailure,
48       Never
49
50
51       --save-config=false      If true, the configuration of  current  object
52       will  be saved in its annotation. Otherwise, the annotation will be un‐
53       changed. This flag is useful when you want to perform kubectl apply  on
54       this object in the future.
55
56
57       --schedule=""       A schedule in the Cron format the job should be run
58       with.
59
60
61       --show-managed-fields=false      If true, keep the  managedFields  when
62       printing objects in JSON or YAML format.
63
64
65       --template=""      Template string or path to template file to use when
66       -o=go-template, -o=go-template-file. The template format is golang tem‐
67       plates [http://golang.org/pkg/text/template/#pkg-overview].
68
69
70       --validate="strict"      Must be one of: strict (or true), warn, ignore
71       (or false).            "true" or "strict" will use a schema to validate
72       the  input and fail the request if invalid. It will perform server side
73       validation if ServerSideFieldValidation is enabled on  the  api-server,
74       but  will  fall  back  to  less reliable client-side validation if not.
75                 "warn" will warn about unknown or  duplicate  fields  without
76       blocking  the request if server-side field validation is enabled on the
77       API server, and behave as  "ignore"  otherwise.             "false"  or
78       "ignore"  will not perform any schema validation, silently dropping any
79       unknown or duplicate fields.
80
81
82

OPTIONS INHERITED FROM PARENT COMMANDS

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

EXAMPLE

178                # Create a cron job
179                kubectl create cronjob my-job --image=busybox --schedule="*/1 * * * *"
180
181                # Create a cron job with a command
182                kubectl create cronjob my-job --image=busybox --schedule="*/1 * * * *" -- date
183
184
185
186

SEE ALSO

188       kubectl-create(1),
189
190
191

HISTORY

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