KUBERNETES(1)(kubernetes)

💖 kubectl create job 💖

okay so bestie, welcome to the KUBERNETES(1)(kubernetes) manual page, and today's main character is kubectl create job. it's giving "i need a Job and i need it now" energy, and honestly? valid. let's get into it 🎀

---

📛 NAME 📛

kubectl create job — create a Job with the name you specify, bestie ✨

---

🫶 SYNOPSIS 🫶

kubectl create job [OPTIONS]

---

🌸 DESCRIPTION 🌸

Create a job with the specified name.

that's it. that's the whole vibe. you give it a name, it makes you a Job. no cap, no notes, lowkey iconic. 💅

---

✨ OPTIONS ✨

• --allow-missing-template-keys=true — if true, it ignores any errors in templates when a field or map key is missing in the template. only applies to golang and jsonpath output formats, iykyk.
• --dry-run="none" — must be "none", "server", or "client". if it's the client strategy, it only prints the object that would be sent, without sending it. if it's the server strategy, it submits a server-side request without persisting the resource. peek without committing, we love a preview era 🦋
• --field-manager="kubectl-create" — the name of the manager used to track field ownership.
• --from="" — the name of the resource to create a Job from. heads up: only CronJob is supported. fr fr, that's the only one.
• --image="" — image name to run. slay.
• -o, --output="" — output format. one of: (json, yaml, kyaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file).
• --save-config=false — if true, the configuration of the current object gets saved in its annotation. otherwise the annotation stays unchanged. this flag is useful when you want to perform kubectl apply on this object in the future. future-proofing queen 👑
• --show-managed-fields=false — if true, keeps 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="strict" — must be one of: strict (or true), warn, ignore (or false). "true" or "strict" will use a schema to validate the input and fail the request if it's invalid — it will perform server side validation if ServerSideFieldValidation is enabled on the api-server, but will fall back to less reliable client-side validation if it's not. "warn" will warn about unknown or duplicate fields without blocking the request if server-side field validation is enabled on the API server, and behave as "ignore" otherwise. "false" or "ignore" will not perform any schema validation at all, silently dropping any unknown or duplicate fields. 💀 silently dropping?? that's wild but okay, that's what it says.

---

🌈 OPTIONS INHERITED FROM PARENT COMMANDS 🌈

these are the family heirlooms, inherited from the parent commands, and there are a lot of them. buckle up 🎀

• --as="" — username to impersonate for the operation. user 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="/home/username/.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. this will make your HTTPS connections insecure. ⚠️ not me telling you to be careful with this one, but like... be careful with this one.
• --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.
• --password="" — password for basic authentication to the API server.
• --profile="none" — name of profile to capture. one of (none|cpu|heap|goroutine|threadcreate|block|mutex|trace).
• --profile-output="profile.pprof" — name of the file to write the profile to.
• --proxy-url="" — proxy URL to use for requests to the API server.
• --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.
• --username="" — username for basic authentication to the API server.
• --version=false — --version, --version=raw prints version information and quits; --version=vX.Y.Z... sets the reported version.
• --warnings-as-errors=false — treat warnings received from the server as errors and exit with a non-zero exit code.

---

🍓 EXAMPLE 🍓

go off, bestie, here are the receipts:

# Create a job
kubectl create job my-job --image=busybox

# Create a job with a command
kubectl create job my-job --image=busybox -- date

# Create a job from a cron job named "a-cronjob"
kubectl create job test-job --from=cronjob/a-cronjob

---

🦋 SEE ALSO 🦋

• kubectl-create(1),

---

🧚 HISTORY 🧚

January 2015, Originally compiled by Eric Paris (eparis at redhat dot com) based on the kubernetes source material, but hopefully they have been automatically generated since!

---

and that's the whole page, bestie 💜 this one lives in the Manuals / User corner of the KUBERNETES(1)(kubernetes) manual, and the OG date on it is January 2015 — shoutout to Eric Paris for the original compile, and to the auto-generators for carrying it ever since. now go make a Job, you got this 💖✨🎀