OPENSHIFT CLI(1)

NAME

openshift cli deploy - View, start, cancel, or retry a deployment

SYNOPSIS

openshift cli deploy [OPTIONS]

DESCRIPTION

View, start, cancel, or retry a deployment

This command allows you to control a deployment config. Each individual deployment is exposed as a new replication controller, and the deployment process manages scaling down old deployments and scaling up new ones. Use 'openshift cli rollback' to rollback to any previous deployment.

There are several deployment strategies defined:

    • Rolling (default) - scales up the new deployment in stages, gradually reducing the number of old deployments. If one of the new deployed pods never becomes "ready", the new deployment 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 deployment down to zero, then scales the new deployment 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.

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

If you want to cancel a running deployment, use '--cancel' but keep in mind that this is a best-effort operation and may take some time to complete. It’s possible the deployment will partially or totally complete before the cancellation is effective. In such a case an appropriate event will be emitted.

If no options are given, shows information about the latest deployment.

OPTIONS

--cancel=false
    If true, cancel the in-progress deployment.

--enable-triggers=false
    If true, enables all image triggers for the deployment config.

--follow=false
    If true, follow the logs of a deployment

--latest=false
    If true, start a new deployment now.

--retry=false
    If true, retry the latest failed 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

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

      # Display the latest deployment for the 'database' deployment config
      openshift cli deploy database

      # Start a new deployment based on the 'database'
      openshift cli deploy database --latest

      # Start a new deployment and follow its log
      openshift cli deploy database --latest --follow

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

      # Cancel the in-progress deployment based on 'frontend'
      openshift cli deploy frontend --cancel

SEE ALSO

openshift-cli(1),

HISTORY

June 2016, Ported from the Kubernetes man-doc generator