Triggering CD
After the CI pipeline is complete, you can trigger the CD pipeline.
Go to the
Build & Deploy
tab of your application and click Select Image in the CD pipeline.Figure 1: 'Select Image' Button Select an image for deployment.
Figure 2: Selecting an Image for Deployment
However, if an image is already deployed, you can identify it by the tag Active on <Environment name>
.

If in any scenario, such as deploying a hotfix, if you need to use a different deployment strategy other than the default, you can select a different deployment strategy.
Note: You can only select the deployment strategies that are configured for that pipeline. Refer to the CD Pipeline to learn more.
Figure 4: Selecting Deployment Strategy In case you have made any changes in the environment configurations (such as changing deployment strategy, modifying ConfigMaps & Secrets, etc.) since the last deployment, use the Config Diff button to compare the new configurations with the last deployed configurations before deploying. Refer to Reviewing Configurations Differences to learn more.
Click Deploy to trigger the CD pipeline.
Reviewing Configuration Differences
Before triggering a deployment, if you’ve made any changes to the environment configurations, you can review the configuration differences between your Last Deployed Configurations (old configurations) and your Last Saved Configurations (new configurations) by clicking the Config Diff button. After reviewing, you can choose whether to deploy using the updated configurations or stick with the previously deployed ones.
Click the Config Diff button to review the changes; a modal window will appear.
Figure 5: Clicking 'Config Diff' button You can compare configuration differences for various resources, including the Deployment template, Pipeline Configurations, ConfigMaps, and Secrets.
To compare changes for a specific resource, select it from the left side of the modal window under Deployment Configurations.
Figure 6: Selecting Resource The right panel displays a side-by-side comparison between the Last Deployed and Last Saved configurations for the selected resource. You can review the configuration differences for each resource before triggering the deployment.
Figure 7a: Comparing Deployment Template Figure 7b: Comparing Pipeline Configurations Figure 7c: Comparing ConfigMaps Figure 7d: Comparing Secrets After reviewing, select whether you want to trigger the deployment with Last Saved Config (new configurations) or Last Deploy Config (old configurations).
Figure 8: Selecting Configuration For Deployment Select Deploy to trigger the deployment.
Figure 9: Triggering The Deployment
When manual approval is enabled for the deployment pipeline configured in the workflow, you are expected to request for an image approval before each deployment. Alternatively, you can deploy images that have already been approved once.
If no approved images are available or the current image is already deployed, you won't see any images for deployment when clicking Select Image.

Requesting for Image Approval
Users need to have Build & deploy permission or above (along with access to the environment and application) to request for an image approval.
To request an image approval, follow these steps:
Navigate to the
Build & Deploy
page, and click the Approval for deployment icon.Figure 11: Approval Button Click the Request Approval button present on the image for which you want to request an approval and click Submit Request.
Figure 12: Requesting Approval In case you have configured SES or SMTP on Devtron, you can directly choose the approver(s) from the list of approvers as shown below.
Figure 13: Choosing Approvers The users you selected will receive an approval request via email. Any user with 'Image approver' permission alongwith access to the given application and given environment would be able to approve the image.
Extras
In case you wish to cancel the image approval request, you can do so from the
Approval pending
tab as shown in the below image.Figure 14: Cancelling Request If you've received an approval but no longer want the image to be deployable, you can let the approval expire.
Figure 15: Expiring an Approval
Accepting Image Approval Request
By default, super-admin users are considered as the default approvers. Users who build the image and/or request for its approval, cannot self-approve it even if they have super-admin privileges.
Users with Approver
permission (for the specific application and environment) can also approve a deployment. This permission can be granted to users from User Permissions
present in Global Configurations.
In case SES or SMTP was configured in Devtron, and the user chose the approvers while raising an image approval request, the approvers would receive an email notification as shown below:

To approve an image approval request, follow these steps:
Go to the
Build & Deploy
page and click theApproval for deployment
button.Figure 17: Approval Button Switch to the
Approval pending
tab. Here, you will get a list of images that are awaiting approval.Figure 18: List of Pending Approvals Click Approve followed by Approve Request button.
Figure 19: Approving a Request
Deploying Approved Image
Users need to have Build & deploy permission or above (along with access to the respective environment and application) to select and deploy an approved image.
In case the super-admin has set the minimum number of approval to more than 1 (in workflow), you must wait for all approvals before deploying the image. In other words, partially approved image will not be eligible for deployment.

To deploy an approved image, follow these steps:
Navigate to the
Build & Deploy
tab and click Select Image.Figure 21: Select Image Button You will find all the approved images listed under the
Approved images
section. From the list, you can select the desired image and deploy it to your environment.Figure 22: List of Approved Images You can view the status of current deployment in the
App Details
tab.Figure 23: 'App Details' Screen
The status initially appears as Progressing
for approximately 1-2 minutes, and then gradually transitions to Healthy
state based on the deployment strategy.
Here, our CD pipeline trigger was successful and the deployment is in Healthy
state.
To further diagnose the deployments, click here
Last updated
Was this helpful?