oc-rollout man page

oc rollout — Manage a Kubernetes deployment or OpenShift deployment config

Synopsis

oc rollout [OPTIONS]

Description

Start a new rollout, view its status or history, rollback to a previous revision of your app

This command allows you to control a deployment config. Each individual rollout is exposed as a replication controller, and the deployment process manages scaling down old replication controllers and scaling up new ones.

There are several deployment strategies defined:

· Rolling (default) - scales up the new replication controller in stages, gradually reducing the number of old pods. If one of the new deployed pods never becomes "ready", the new rollout will be rolled back (scaled down to zero). Use when your application can tolerate two versions of code running at the same time (many web applications, scalable databases)

· Recreate - scales the old replication controller down to zero, then scales the new replication controller up to full. Use when your application cannot tolerate two versions of code running at the same time

· Custom - run your own deployment process inside a Docker container using your own scripts.

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

--azure-container-registry-config=""

Path to the file container Azure container registry configuration information.

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

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

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

See Also

oc(1), oc-rollout-cancel(1), oc-rollout-history(1), oc-rollout-latest(1), oc-rollout-pause(1), oc-rollout-resume(1), oc-rollout-retry(1), oc-rollout-status(1), oc-rollout-undo(1),

History

June 2016, Ported from the Kubernetes man-doc generator

Referenced By

oc(1), oc-rollout-cancel(1), oc-rollout-history(1), oc-rollout-latest(1), oc-rollout-pause(1), oc-rollout-resume(1), oc-rollout-retry(1), oc-rollout-status(1), oc-rollout-undo(1).

Openshift CLI User Manuals June 2016