oc-scale man page

oc scale — Change the number of pods in a deployment

Synopsis

oc scale [Options]

Description

Set a new size for a deployment or replication controller

Scale also allows users to specify one or more preconditions for the scale action. If --current-replicas or --resource-version is specified, it is validated before the scale is attempted, and it is guaranteed that the precondition holds true when the scale is sent to the server.

Note that scaling a deployment configuration with no deployments will update the desired replicas in the configuration template.

Options

--current-replicas=-1
Precondition for current size. Requires that the current size of the resource match this value in order to scale.
-f, --filename=[]
Filename, directory, or URL to a file identifying the resource to set a new size
--include-extended-apis=true
If true, include definitions of new APIs via calls to the API server. [default true]
-o, --output=""
Output mode. Use "-o name" for shorter output (resource/name).
--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.
--replicas=-1
The new desired number of replicas. Required.
--resource-version=""
Precondition for resource version. Requires that the current resource version match this value in order to scale.
--timeout=0
The length of time to wait before giving up on a scale operation, zero means don't wait. Any other values should contain a corresponding time unit (e.g. 1s, 2m, 3h).

Options Inherited from Parent Commands

--api-version=""
DEPRECATED: The API version to use when talking to the server

--as=""
Username to impersonate for the operation.

--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

--config=""
Path to the config file to use for CLI requests.

--context=""
The name of the kubeconfig context to use

--google-json-key=""
The Google Cloud Platform Service Account JSON Key to use for authentication.

--insecure-skip-tls-verify=false
If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure.

--log-flush-frequency=0
Maximum number of seconds between log flushes

--match-server-version=false
Require server version to match client version

-n, --namespace=""
If present, the namespace scope for this CLI request.

--server=""
The address and port of the Kubernetes API server

--token=""
Bearer token for authentication to the API server.

--user=""
The name of the kubeconfig user to use

Example

# Scale replication controller named 'foo' to 3.
oc scale --replicas=3 replicationcontrollers foo

# If the replication controller named foo's current size is 2, scale foo to 3.
oc scale --current-replicas=2 --replicas=3 replicationcontrollers foo

# Scale the latest deployment of 'bar'. In case of no deployment, bar's template
# will be scaled instead.
oc scale --replicas=10 dc bar

See Also

oc(1),

History

June 2016, Ported from the Kubernetes man-doc generator

Referenced By

oc(1).

Openshift CLI User Manuals Openshift June 2016