Bartosz Bierkowski - Low dose cloud

OpenShift Morsels: pausing deployments

On day #23 last look at the oc rollout subcommands brings us to pausing and resuming the deployments

The deployment can be paused. As a result you will not be able to rollout new version of application. Also all triggers will be ignored, so changes to configuration will not trigger the deployment.

It is clear from the message that the new deployment will not be rolled out.

As soon as the changes to the Deployment Configuration are finished, you can resume the deployments. This will trigger the deployment if new one is pending for example because of the configuration change trigger.


The commands were executed using minishift and the following client/server versions of OpenShift.

oc v3.7.0+7ed6862
client kubernetes v1.7.6+a08f5eeb62
openshift v3.6.0+c4dd4cf
server kubernetes v1.6.1+5115d708d7


Thanks for reading the OpenShift morsels. To get updates about new articles, you can sign up to the newsletter below.

As a thank you message, you will also get access to OpenShift CLI CheatSheet listing most commonly used commands together with a short explanation.

Did you like the article?
Join the newsletter to receive notifications about new articles.
I respect your privacy.