Once you have continuous delivery configured for your image repository and cluster, releasing new images as you make changes to your code is straightforward.

The diagram below shows a sample application that has been configured to work with Weave Cloud deploy. The column on the left displays a list of the microservices found in the app, which in this case, happens to be the Sock Shop - a microservices demo. When you click on a service its release history is displayed to the right.

Within Weave Cloud you can manage images releases by:

  • Doing a Dry Run
  • Releasing Images
  • Rolling Back Changes
  • Specifying the Release Policy

Performing a Dry Run & Releasing Updated Images

When the Deploy daemon has detected a new image that is not currently running in your cluster, the image and a history of its updates appear in a list when you click on the service. You can test whether the image can be updated by doing a Dry Run beforehand. Click the Release button beside an image revision to view the detailed plan of how the image will be deployed. If you are satisfied with the result, you can click Release beneath the Dry Run plan to deploy it the cluster. If you set the service to Automate, then Dry Run details are not available.

Rolling Back Changes

Deployed services are easily rolled back by selecting a prior image from the list and then re-deploying it. The associated manifests will also be updated with the change.

Turning on Automation

Turn on and control how images are deployed to your cluster. Automation can be easily controlled from within Weave Cloud by clicking the “Automate” button when inspecting a service. You can set different policies on each services if desired and also lock certain services to prevent them from being accidently deployed.

Further Reading