oc-rollback man page

oc rollback — Revert part of an application back to a previous deployment


oc rollback [Options]


Revert an application back to a previous deployment

When you run this command your deployment configuration will be updated to match a previous deployment. By default only the pod and container configuration will be changed and scaling or trigger settings will be left as- is. Note that environment variables and volumes are included in rollbacks, so if you've recently updated security credentials in your environment your previous deployment may not have the correct values.

Any image triggers present in the rolled back configuration will be disabled with a warning. This is to help prevent your rolled back deployment from being replaced by a triggered deployment soon after your rollback. To re-enable the triggers, use the 'deploy' command.

If you would like to review the outcome of the rollback, pass '--dry-run' to print a human-readable representation of the updated deployment configuration instead of executing the rollback. This is useful if you're not quite sure what the outcome will be.


Include the previous deployment's replicationController replica count and selector in the rollback
Include the previous deployment's strategy in the rollback
Include the previous deployment's triggers in the rollback
-d, --dry-run=false
Instead of performing the rollback, describe what the rollback will look like in human-readable form
-o, --output=""
Instead of performing the rollback, print the updated deployment configuration in the specified format (json|yaml|name|template|templatefile)
-t, --template=""
Template string or path to template file to use when -o=template or -o=templatefile.
A config version to rollback to. Specifying version 0 is the same as omitting a version (the version will be auto-detected). This option is ignored when specifying a deployment.

Options Inherited from Parent Commands

DEPRECATED: The API version to use when talking to the server

Username to impersonate for the operation.

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 address and port of the Kubernetes API server

Bearer token for authentication to the API server.

The name of the kubeconfig user to use


# Perform a rollback to the last successfully completed deployment for a deploymentconfig
oc rollback frontend

# See what a rollback to version 3 will look like, but don't perform the rollback
oc rollback frontend --to-version=3 --dry-run

# Perform a rollback to a specific deployment
oc rollback frontend-2

# Perform the rollback manually by piping the JSON of the new config back to oc
oc rollback frontend -o json | oc replace dc/frontend -f -

See Also



June 2016, Ported from the Kubernetes man-doc generator

Referenced By


Explore man page connections for oc-rollback(1).

Openshift Openshift CLI User Manuals June 2016