KUBERNETES(1)(kubernetes)

✨ KUBERNETES(1)(kubernetes) ✨

okay bestie, welcome to the kubectl manual, section 1 (that's the "user commands" section, iykyk) 💖

---

🎀 NAME 🎀

kubectl create deployment — create a deployment with the specified name. that's it. that's the whole job. iconic.

---

🌸 SYNOPSIS 🌸

kubectl create deployment [OPTIONS]

---

🦋 DESCRIPTION 🦋

Create a deployment with the specified name. literally just spin up a deployment, name it whatever you want, and let it cook. 👑

---

✨ OPTIONS ✨

• --allow-missing-template-keys=true — if true, ignore any errors in templates when a field or map key is missing in the template. only applies to golang and jsonpath output formats. so if your template is being dramatic about a missing key, this shuts it up.
• --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 actually sending it. if it's the server strategy, it submits a server-side request without persisting the resource. so yeah, a little sneak preview 🫣
• --field-manager="kubectl-create" — name of the manager used to track field ownership. someone has to keep the receipts, and it's this flag.
• --image=[] — image names to run. a deployment can have multiple images set for multi-container pod. stack 'em, bestie.
• -o, --output="" — output format. one of: (json, yaml, kyaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). pick your vibe.
• --port=-1 — the containerPort that this deployment exposes.
• -r, --replicas=1 — number of replicas to create. default is 1.
• --save-config=false — if true, the configuration of current object will be saved in its annotation. otherwise, the annotation will be unchanged. this flag is useful when you want to perform kubectl apply on this object in the future. future-you says thank you 💅
• --show-managed-fields=false — if true, keep the managedFields when printing objects in JSON or YAML format.
• --template="" — template string or path to 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 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 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, silently dropping any unknown or duplicate fields. 💀 (silently dropping fields is a choice, and honestly? a bold one.)

---

💜 OPTIONS INHERITED FROM PARENT COMMANDS 💜

these come from the parent command, so they're like... family. you still get them all.

• --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. ⚠️ yes, this is the "yolo" flag. say it with me: 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.
• --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. zero means infinity, basically. no cap.
• -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 🌈

here's the tea, fr fr:

# Create a deployment named my-dep that runs the busybox image
kubectl create deployment my-dep --image=busybox

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

# Create a deployment named my-dep that runs the nginx image with 3 replicas
kubectl create deployment my-dep --image=nginx --replicas=3

# Create a deployment named my-dep that runs the busybox image and expose port 5701
kubectl create deployment my-dep --image=busybox --port=5701

# Create a deployment named my-dep that runs multiple containers
kubectl create deployment my-dep --image=busybox:latest --image=ubuntu:latest --image=nginx

---

👑 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 honestly, slay for that, Eric. 🫶

---

and that's a wrap on our lil tour, bestie 🌸 this came out of the Manuals collection, User section, under KUBERNETES(1)(kubernetes) — go forth and create deployment responsibly. mwah 💋✨