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.
If true, ignore any errors in templates when a field or map key is missing in the template. Only applies to golang and jsonpath output formats.
If true, include the previous deployment's replicationController replica count and selector in the rollback
If true, include the previous deployment's strategy in the rollback
If true, 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=""
Output format. One of: json|yaml|name|go-template|go-template-file|templatefile|template|jsonpath|jsonpath-file.
Template string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang templates [ ⟨http://golang.org/pkg/text/template/#pkg-overview⟩].
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
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
# 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 - # Print the updated deployment configuration in JSON format instead of performing the rollback oc rollback frontend -o json
June 2016, Ported from the Kubernetes man-doc generator