You are viewing documentation for Kubernetes version: v1.29
Kubernetes v1.29 documentation is no longer actively maintained. The version you are currently viewing is a static snapshot. For up-to-date information, see the latest version.
kubectl autoscale
Synopsis
Creates an autoscaler that automatically chooses and sets the number of pods that run in a Kubernetes cluster.
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.
kubectl autoscale (-f FILENAME | TYPE NAME | TYPE/NAME) [--min=MINPODS] --max=MAXPODS [--cpu-percent=CPU]
Examples
# 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-percent=80
Options
| --allow-missing-template-keys Default: 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-percent int32 Default: -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 string[="unchanged"] Default: "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 string Default: "kubectl-autoscale" | |
Name of the manager used to track field ownership. |
|
| -f, --filename strings | |
Filename, directory, or URL to files identifying the resource to autoscale. |
|
| -h, --help | |
help for autoscale |
|
| -k, --kustomize string | |
Process the kustomization directory. This flag can't be used together with -f or -R. |
|
| --max int32 Default: -1 | |
The upper limit for the number of pods that can be set by the autoscaler. Required. |
|
| --min int32 Default: -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 string | |
The name for the newly created object. If not specified, the name of the input resource will be used. |
|
| -o, --output string | |
Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). |
|
| -R, --recursive | |
Process the directory used in -f, --filename recursively. Useful when you want to manage related manifests organized within the same directory. |
|
| --save-config | |
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 | |
If true, keep the managedFields when printing objects in JSON or YAML format. |
|
| --template string | |
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]. |
|
| --as string | |
Username to impersonate for the operation. User could be a regular user or a service account in a namespace. |
|
| --as-group strings | |
Group to impersonate for the operation, this flag can be repeated to specify multiple groups. |
|
| --as-uid string | |
UID to impersonate for the operation. |
|
| --azure-container-registry-config string | |
Path to the file containing Azure container registry configuration information. |
|
| --cache-dir string Default: "$HOME/.kube/cache" | |
Default cache directory |
|
| --certificate-authority string | |
Path to a cert file for the certificate authority |
|
| --client-certificate string | |
Path to a client certificate file for TLS |
|
| --client-key string | |
Path to a client key file for TLS |
|
| --cloud-provider-gce-l7lb-src-cidrs cidrs Default: 130.211.0.0/22,35.191.0.0/16 | |
CIDRs opened in GCE firewall for L7 LB traffic proxy & health checks |
|
| --cloud-provider-gce-lb-src-cidrs cidrs Default: 130.211.0.0/22,209.85.152.0/22,209.85.204.0/22,35.191.0.0/16 | |
CIDRs opened in GCE firewall for L4 LB traffic proxy & health checks |
|
| --cluster string | |
The name of the kubeconfig cluster to use |
|
| --context string | |
The name of the kubeconfig context to use |
|
| --default-not-ready-toleration-seconds int Default: 300 | |
Indicates the tolerationSeconds of the toleration for notReady:NoExecute that is added by default to every pod that does not already have such a toleration. |
|
| --default-unreachable-toleration-seconds int Default: 300 | |
Indicates the tolerationSeconds of the toleration for unreachable:NoExecute that is added by default to every pod that does not already have such a toleration. |
|
| --disable-compression | |
If true, opt-out of response compression for all requests to the server |
|
| --insecure-skip-tls-verify | |
If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure |
|
| --kubeconfig string | |
Path to the kubeconfig file to use for CLI requests. |
|
| --match-server-version | |
Require server version to match client version |
|
| -n, --namespace string | |
If present, the namespace scope for this CLI request |
|
| --password string | |
Password for basic authentication to the API server |
|
| --profile string Default: "none" | |
Name of profile to capture. One of (none|cpu|heap|goroutine|threadcreate|block|mutex) |
|
| --profile-output string Default: "profile.pprof" | |
Name of the file to write the profile to |
|
| --request-timeout string Default: "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 string | |
The address and port of the Kubernetes API server |
|
| --storage-driver-buffer-duration duration Default: 1m0s | |
Writes in the storage driver will be buffered for this duration, and committed to the non memory backends as a single transaction |
|
| --storage-driver-db string Default: "cadvisor" | |
database name |
|
| --storage-driver-host string Default: "localhost:8086" | |
database host:port |
|
| --storage-driver-password string Default: "root" | |
database password |
|
| --storage-driver-secure | |
use secure connection with database |
|
| --storage-driver-table string Default: "stats" | |
table name |
|
| --storage-driver-user string Default: "root" | |
database username |
|
| --tls-server-name string | |
Server name to use for server certificate validation. If it is not provided, the hostname used to contact the server is used |
|
| --token string | |
Bearer token for authentication to the API server |
|
| --user string | |
The name of the kubeconfig user to use |
|
| --username string | |
Username for basic authentication to the API server |
|
| --version version[=true] | |
--version, --version=raw prints version information and quits; --version=vX.Y.Z... sets the reported version |
|
| --warnings-as-errors | |
Treat warnings received from the server as errors and exit with a non-zero exit code |
|
See Also
- kubectl - kubectl controls the Kubernetes cluster manager
This page is automatically generated.
If you plan to report an issue with this page, mention that the page is auto-generated in your issue description. The fix may need to happen elsewhere in the Kubernetes project.