OC-CREATE-CRONJOB(1)

πŸ“¦
version 4.22.0 Β· 2 versions
, in nixpkgs unstable

πŸ’… oc create cronjob β€” OC CREATE(1), June 2016, Openshift CLI User Manuals ✨

okay bestie, buckle UP πŸŽ€ because this is the page for oc create cronjob, straight out of the Openshift CLI User Manuals (June 2016 edition, we stan a vintage queen πŸ‘‘). It's the <manual> for the oc create family and it's literally just here to help you spin up a cron job with a name you pick. No cap.


✨ NAME ✨

oc create cronjob β€” create a cron job with the specified name πŸ•


πŸ¦‹ SYNOPSIS πŸ¦‹

oc create cronjob [OPTIONS]

🌸 DESCRIPTION 🌸

Create a cron job with the specified name. That's it, that's the whole vibe. You give it a name, it gives you a cron job. Iconic behavior, honestly πŸ’…


πŸ’– OPTIONS πŸ’–

  • --allow-missing-template-keys=true β€” if this is true, any errors in templates get ignored when a field or map key is missing in the template. Careful though, bestie: this only applies to golang and jsonpath output formats πŸ™ˆ
  • --dry-run="none" β€” must be "none", "server", or "client". If you go with the client strategy, it just prints the object that would be sent, without actually sending it (window shopping, basically πŸ›οΈ). If you pick server strategy, it submits a server-side request without persisting the resource. Very "look don't touch" of you.
  • --field-manager="kubectl-create" β€” the name of the manager used to track field ownership πŸ—‚οΈ
  • --image="" β€” image name to run. Yes, the actual image, please and thank you πŸ–ΌοΈ
  • -o, --output="" β€” output format, and the menu is LONG. One of: (json, yaml, kyaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). pick your fighter πŸ’€
  • --restart="" β€” the job's restart policy. supported values: OnFailure, Never πŸ”
  • --save-config=false β€” if true, the configuration of the current object gets saved in its annotation. Otherwise, the annotation stays unchanged. This flag is lowkey useful when you wanna do a kubectl apply on this object in the future πŸ‘€
  • --schedule="" β€” a schedule in the Cron format that the job should be run with ⏰
  • --show-managed-fields=false β€” if true, keep the managedFields when printing objects in JSON or YAML format 🧾
  • --template="" β€” template string or path to a 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="ignore" β€” must be one of: strict (or true), warn, ignore (or false). Here's the tea β˜•: "true" or "strict" uses a schema to validate the input and fails the request if invalid. It performs server side validation if ServerSideFieldValidation is enabled on the api-server, but falls back to less reliable client-side validation if not. "warn" warns about unknown or duplicate fields without blocking the request if server-side field validation is enabled on the API server β€” and behaves as "ignore" otherwise. "false" or "ignore" performs no schema validation at all, silently dropping any unknown or duplicate fields. silent. dropping. 🫠

πŸŽ€ OPTIONS INHERITED FROM PARENT COMMANDS πŸŽ€

these are the hand-me-downs from the parent command, and honestly they ate πŸ‘‘

  • --as="" β€” username to impersonate for the operation. could be a regular user or a service account in a namespace πŸͺͺ
  • --as-group=[] β€” group to impersonate for the operation. this flag can be repeated to specify multiple groups 🫢
  • --as-uid="" β€” UID to impersonate for the operation
  • --as-user-extra=[] β€” user extras to impersonate for the operation. this flag can be repeated to specify multiple values for the same key πŸ”‘
  • --cache-dir="/homeless-shelter/.kube/cache" β€” default cache directory πŸ“
  • --certificate-authority="" β€” path to a cert file for the certificate authority
  • --client-certificate="" β€” path to a client certificate file for TLS
  • --client-key="" β€” path to a client key file for TLS
  • --cluster="" β€” the name of the kubeconfig cluster to use
  • --context="" β€” the name of the kubeconfig context to use
  • --disable-compression=false β€” if true, opt-out of response compression for all requests to the server πŸ—œοΈ
  • --insecure-skip-tls-verify=false β€” if true, the server's certificate will not be checked for validity. heads up bestie, this will make your HTTPS connections insecure πŸ’€βš οΈ
  • --kubeconfig="" β€” path to the kubeconfig file to use for CLI requests
  • --kuberc="" β€” path to the kuberc file to use for preferences. This can be disabled by exporting KUBECTL_KUBERC=false feature gate or turning off the feature KUBERC=off πŸŽ›οΈ
  • --match-server-version=false β€” require server version to match client version
  • -n, --namespace="" β€” if present, the namespace scope for this CLI request 🏷️
  • --profile="none" β€” name of profile to capture. one of (none|cpu|heap|goroutine|threadcreate|block|mutex) πŸ“Š
  • --profile-output="profile.pprof" β€” name of the file to write the profile to
  • --request-timeout="0" β€” the length of time to wait before giving up on a single server request. non-zero values should contain a corresponding time unit (e.g. 1s, 2m, 3h). a value of zero means don't timeout requests βŒ›
  • -s, --server="" β€” the address and port of the Kubernetes API server 🌐
  • --tls-server-name="" β€” server name to use for server certificate validation. if it is not provided, the hostname used to contact the server is used
  • --token="" β€” bearer token for authentication to the API server 🎫
  • --user="" β€” the name of the kubeconfig user to use
  • --warnings-as-errors=false β€” treat warnings received from the server as errors and exit with a non-zero exit code 🚨

🌈 EXAMPLE 🌈

like, actual examples, because we love a demo:

# Create a cron job
oc create cronjob my-job --image=busybox --schedule="*/1 * * * *"

# Create a cron job with a command
oc create cronjob my-job --image=busybox --schedule="*/1 * * * *" -- date

see how the second one has -- date at the end? that's the command, bestie. it's giving "and also run this" ✨


πŸ’œ SEE ALSO πŸ’œ

oc-create(1), β€” go read the parent page too, it's the main character and this is its spin-off 🫢


⭐ HISTORY ⭐

June 2016, Ported from the Kubernetes man-doc generator. a true classic πŸŽ€


and that's the whole page, no notes πŸ’… before you close the tab: this came from Openshift β€” the Openshift CLI User Manuals β€” dated June 2016 (header and footer both said OC CREATE(1), and yes the date shows up twice because it's committed to the bit 🫢). bye bestie, go make some cron jobs πŸŒΈπŸ¦‹πŸ’–

πŸ“¦ where this page comes from