oc rollout [OPTIONS]
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
Allow a SignatureVerifier to use keys which are technically non-compliant with RFC6962.
log to standard error as well as files
Max number of application metrics to store (per container)
Username to impersonate for the operation
Group to impersonate for the operation, this flag can be repeated to specify multiple groups.
Path to the file containing Azure container registry configuration information.
Comma-separated list of files to check for boot-id. Use the first one that exists.
Default HTTP cache directory
Path to a cert file for the certificate authority
Path to a client certificate file for TLS
Path to a client key file for TLS
CIDRs opened in GCE firewall for LB traffic proxy health checks
The name of the kubeconfig cluster to use
location of the container hints file
The name of the kubeconfig context to use
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.
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.
use TLS to connect to docker
path to trusted CA
path to client certificate
path to private key
a comma-separated list of environment variable keys that needs to be collected for docker containers
Only report docker containers in addition to root stats
DEPRECATED: docker root is read from docker info (this is a fallback, default: /var/lib/docker)
Whether to enable cpu load reader
Max length of time for which to store events (per type). Value is a comma separated list of key values, where the keys are event types (e.g.: creation, oom) or "default" and the value is a duration. Default is applied to all non-specified event types
Max number of events to store (per type). Value is a comma separated list of key values, where the keys are event types (e.g.: creation, oom) or "default" and the value is an integer. Default is applied to all non-specified event types
Interval between global housekeepings
Interval between container housekeepings
If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure
Path to the kubeconfig file to use for CLI requests.
Maximum number of seconds between log flushes
when logging hits line file:N, emit a stack trace
Whether to log the usage of the cAdvisor container
If non-empty, write log files in this directory
log to standard error instead of files
Comma-separated list of files to check for machine-id. Use the first one that exists.
Require server version to match client version
- -n, --namespace=""
If present, the namespace scope for this CLI request
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
logs at or above this threshold go to stderr
Writes in the storage driver will be buffered for this duration, and committed to the non memory backends as a single transaction
use secure connection with database
Bearer token for authentication to the API server
The name of the kubeconfig user to use
- -v, --v=0
log level for V logs
Print version information and quit
comma-separated list of pattern=N settings for file-filtered logging
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),
June 2016, Ported from the Kubernetes man-doc generator
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).