OpenShift Container Platform 4.5 Applications Deployments can be paused at any point in time, meaning you can also pause ongoing rollouts. On the other hand, you cannot pause deployer pods currently, so if you try to pause a deployment in the middle of a rollout, the deployer process will not be affected and will continue until it finishes. DeploymentConfig  objects can be managed from the OpenShift Container Platform web console’s Workloads  page or using the  oc  CLI. The following procedures show CLI usage unless otherwise stated. You can start a rollout to begin the deployment process of your application. Procedure If a deployment process is already in progress, the command displays a message and a new replication controller will not be deployed. You can view a deployment to get basic information about all the available revisions of your application. $ oc rollout history dc/<name> $ oc rollout history dc/<name> --revision=1 $ oc describe dc <name> $ oc rollout latest dc/<name> 1. To start a new deployment process from an existing  DeploymentConfig  object, run the following command: 3.2. MANAGING DEPLOYMENT PROCESSES 3.2.1. Managing DeploymentConfig objects 3.2.1.1. Starting a deployment 3.2.1.2. Viewing a deployment Procedure 3.2.1.3. Retrying a deployment 50 If the current revision of your  DeploymentConfig  object failed to deploy, you can restart the deployment process. 3. For more detailed information about a  DeploymentConfig  object and its latest revision, use the oc describe  command: 2. To view details specific to a revision, add the  --revision  flag: 1. To show details about all recently created replication controllers for the provided  DeploymentConfig  object, including any currently running deployment process, run the following command: NOTE