OPENSHIFT CLI(1)

NAME

openshift cli rollback - Revert part of an application back to a previous deployment

SYNOPSIS

openshift cli rollback [OPTIONS]

DESCRIPTION

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.

OPTIONS

--change-scaling-settings=false
    Include the previous deployment's replicationController replica count and selector in the rollback

--change-strategy=false
    Include the previous deployment's strategy in the rollback

--change-triggers=false
    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.

--to-version=0
    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

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

      # Perform a rollback to the last successfully completed deployment for a deploymentconfig
      openshift cli rollback frontend
      # See what a rollback to version 3 will look like, but don't perform the rollback
      openshift cli rollback frontend --to-version=3 --dry-run
      # Perform a rollback to a specific deployment
      openshift cli rollback frontend-2
      # Perform the rollback manually by piping the JSON of the new config back to openshift cli
      openshift cli rollback frontend -o json | openshift cli replace dc/frontend -f -

SEE ALSO

openshift-cli(1),

HISTORY

June 2016, Ported from the Kubernetes man-doc generator