oc-rollout man page
oc rollout — Manage a Kubernetes deployment or OpenShift deployment config
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
DEPRECATED: The API version to use when talking to the server
Username to impersonate for the operation
Path to the file container Azure container registry configuration information.
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
The name of the kubeconfig cluster to use
Path to the config file to use for CLI requests.
The name of the kubeconfig context to use
The Google Cloud Platform Service Account JSON Key to use for authentication.
If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure
Maximum number of seconds between log flushes
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.
The address and port of the Kubernetes API server
Bearer token for authentication to the API server
The name of the kubeconfig user to use
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).