KUBERNETES(1)(kubernetes)

✨ KUBERNETES(1) — the kubectl autoscale era ✨

okay bestie, sit DOWN, because we're talking about kubectl autoscale from the kubernetes manual (that's manual section 1, the user commands one, iykyk). This page is your whole guide to it, fr fr. 💖

---

🌸 NAME 🌸

kubectl autoscale — auto-scale a deployment, replica set, stateful set, or replication controller. that's the whole vibe. 🦋

---

🎀 SYNOPSIS 🎀

kubectl autoscale [OPTIONS]

---

💅 DESCRIPTION 💅

So here's the tea: this command creates an autoscaler that automatically chooses and sets the number of pods that run in a Kubernetes cluster. The command will attempt to use the autoscaling/v2 API first, and in case of an error, it will fall back to the autoscaling/v1 API. slay, it's got a backup plan. ✨

It looks up a deployment, replica set, stateful set, or replication controller by name and creates an autoscaler that uses the given resource as a reference. An autoscaler can automatically increase or decrease number of pods deployed within the system as needed. it's giving main character energy that manages your replica count for you. 👑

---

🔥 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.
• --cpu="" — Target CPU utilization over all the pods. When specified as a percentage (e.g. "70%" for 70% of requested CPU) it will target average utilization. When specified as quantity (e.g. "500m" for 500 milliCPU) it will target average value. Value without units is treated as a quantity with miliCPU being the unit (e.g. "500" is "500m").
• --cpu-percent=-1 — The target average CPU utilization (represented as a percent of requested CPU) over all the pods. If it's not specified or negative, a default autoscaling policy will be used.
• --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.
• --field-manager="kubectl-autoscale" — Name of the manager used to track field ownership.
• -f, --filename=[] — Filename, directory, or URL to files identifying the resource to autoscale.
• -k, --kustomize="" — Process the kustomization directory. This flag can't be used together with -f or -R. 🚫
• --max=-1 — The upper limit for the number of pods that can be set by the autoscaler. Required. like, you actually have to give this one, bestie.
• --memory="" — Target memory utilization over all the pods. When specified as a percentage (e.g. "60%" for 60% of requested memory) it will target average utilization. When specified as quantity (e.g. "200Mi" for 200 MiB, "1Gi" for 1 GiB) it will target average value. Value without units is treated as a quantity with mebibytes being the unit (e.g. "200" is "200Mi").
• --min=-1 — The lower limit for the number of pods that can be set by the autoscaler. If it's not specified or negative, the server will apply a default value.
• --name="" — The name for the newly created object. If not specified, the name of the input resource will be used.
• -o, --output="" — Output format. One of: (json, yaml, kyaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-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.
• --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].

---

💜 OPTIONS INHERITED FROM PARENT COMMANDS 💜

these aren't even autoscale's own flags, they're the family heirlooms passed down from the parent command. still iconic though. 🫶

• --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. ⚠️ like, not the moment, bestie.
• --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 🌈

look at these. these are the moments. copy them exactly, no cap. 💖

# Auto scale a deployment "foo", with the number of pods between 2 and 10, no target CPU utilization specified so a default autoscaling policy will be used
kubectl autoscale deployment foo --min=2 --max=10

# Auto scale a replication controller "foo", with the number of pods between 1 and 5, target CPU utilization at 80%
kubectl autoscale rc foo --max=5 --cpu=80%

# Auto scale a deployment "bar", with the number of pods between 3 and 6, target average CPU of 500m and memory of 200Mi
kubectl autoscale deployment bar --min=3 --max=6 --cpu=500m --memory=200Mi

# Auto scale a deployment "bar", with the number of pods between 2 and 8, target CPU utilization 60% and memory utilization 70%
kubectl autoscale deployment bar --min=2 --max=8 --cpu=60% --memory=70%

---

🦋 SEE ALSO 🦋

• kubectl(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! 😭 the way this manpage has been through so much

---

and that's the whole thing, bestie! 💖 this was KUBERNETES(1)(kubernetes) from the Manuals / User corner of the world — page compiled by Eric Paris back in Jan 2015, and the footer says the same: source KUBERNETES(1)(kubernetes), date January 2015. go forth and autoscale, you absolute icon. 👑✨