openshift-cli-rollout-retry man page

openshift cli rollout retry ā€” Retry the latest failed rollout

Synopsis

openshift cli rollout retry [Options]

Description

If a rollout fails, you may opt to retry it (if the error was transient). Some rollouts may never successfully complete - in which case you can use the rollout latest to force a redeployment. If a deployment config has completed rolling out successfully at least once in the past, it would be automatically rolled back in the event of a new failed rollout. Note that you would still need to update the erroneous deployment config in order to have its template persisted across your application.

Options

-f, --filename=[]

Filename, directory, or URL to files Filename, directory, or URL to a file identifying the resource to get from a server.

-R, --recursive=false

Process the directory used in -f, --filename recursively. Useful when you want to manage related manifests organized within the same directory.

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

--azure-container-registry-config=""

Path to the file container Azure container registry configuration information.

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

--request-timeout="0"

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.

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

  # Retry the latest failed deployment based on 'frontend'
  # The deployer pod and any hook pods are deleted for the latest failed deployment
  openshift cli rollout retry dc/frontend

See Also

openshift-cli-rollout(1),

History

June 2016, Ported from the Kubernetes man-doc generator

Referenced By

openshift-cli-rollout(1).

Openshift CLI User Manuals June 2016