KUBERNETES(1)(kubernetes)

💖 KUBERNETES(1)(kubernetes) 💖

okay bestie, welcome to the kubectl create page, straight out of the kubernetes manual (section 1, the user commands one) 💅 this one was originally written by Eric Paris back in January 2015, and we're about to make it make sense.

---

✨ NAME ✨

kubectl create — create a resource from a file or from stdin 🫶

---

🌸 SYNOPSIS 🌸

kubectl create [OPTIONS]

---

🦋 DESCRIPTION 🦋

Create a resource from a file or from stdin. That's it, that's the whole job, and it does it flawlessly.

JSON and YAML formats are accepted. Both. She's bilingual, she's versatile, she contains multitudes 💜

---

🎀 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.
• --dry-run="none" — must be "none", "server", or "client". If client strategy, only print the object that would be sent, without sending it. If server strategy, submit server-side request without persisting the resource.
• --edit=false — edit the API resource before creating 👀
• --field-manager="kubectl-create" — name of the manager used to track field ownership.
• -f, --filename=[] — filename, directory, or URL to files to use to create the resource.
• -k, --kustomize="" — process the kustomization directory. This flag can't be used together with -f or -R. 🚫
• -o, --output="" — output format. One of: (json, yaml, kyaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file).
• --raw="" — raw URI to POST to the server. Uses the transport specified by the kubeconfig file.
• --record=false — record current kubectl command in the resource annotation. If set to false, do not record the command. If set to true, record the command. If not set, default to updating the existing annotation value only if one already exists.
• -R, --recursive=false — process the directory used in -f, --filename recursively. Useful when you want to manage related manifests organized within the same directory.
• --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.
• -l, --selector="" — selector (label query) to filter on, supports '=', '==', '!=', 'in', 'notin'. (e.g. -l key1=value1,key2=value2,key3 in (value3)). Matching objects must satisfy all of the specified label constraints.
• --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.
• --windows-line-endings=false — only relevant if --edit=true. Defaults to the line ending native to your platform.

---

💜 OPTIONS INHERITED FROM PARENT COMMANDS 💜

these ones come down from the parent command, like family heirlooms but for flags ✨

• --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. ⚠️ bestie, 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 🌈

okay these are the vibes, literally just copy them 👑

# Create a pod using the data in pod.json
kubectl create -f ./pod.json

# Create a pod based on the JSON passed into stdin
cat pod.json | kubectl create -f -

# Edit the data in registry.yaml in JSON then create the resource using the edited data
kubectl create -f registry.yaml --edit -o json

---

🔥 SEE ALSO 🔥

the whole friend group, go say hi 🫶

kubectl(1), kubectl-create-clusterrole(1), kubectl-create-clusterrolebinding(1), kubectl-create-configmap(1), kubectl-create-cronjob(1), kubectl-create-deployment(1), kubectl-create-ingress(1), kubectl-create-job(1), kubectl-create-namespace(1), kubectl-create-poddisruptionbudget(1), kubectl-create-priorityclass(1), kubectl-create-quota(1), kubectl-create-role(1), kubectl-create-rolebinding(1), kubectl-create-secret(1), kubectl-create-service(1), kubectl-create-serviceaccount(1), kubectl-create-token(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! not me reading that last part 😭 iconic honestly.

---

and that's a wrap bestie 💖 this came from the Manuals / User corner of the world, page KUBERNETES(1)(kubernetes), dated January 2015. go create something slay ✨👑