Observing the Continuous Deployment (CD) Process

Your pull request should be ready to merge. After merging the pull request, Argo CD will notice the changes within 3 minutes (default polling interval), and apply the new ConfigMap to your project-foo Namespace.

It’s possible to configure a webhook that immediately notifies Argo CD when new changes are merged into the Git repository. This is outside of the scope of this workshop.

To merge your pull request:

  1. Open your pull request in GitHub.

  2. Scroll down and click on the Merge pull request button.

  3. Verify the title and commit message are to your liking, then click Confirm merge.

Once the pull request has been merged, take a look in the Argo CD dashboard. The new commit that you merged will show up within 3 minutes.

You can use the Refresh button in Argo CD to force it to check the Git repository for changes, if you don’t want to wait. If you set the sync configuration to "Automated", then as soon as the refresh completes it will trigger a sync for the new changes.

ex8.argo post merge

Once your new commit has been synchronised by Argo CD, your meme can be displayed by visiting your application’s URL. Refresh the page a few times and your meme will eventually be shown, all with zero downtime or manual processes beyond approving a pull request!

You can further confirm that the new ConfigMap has been synchronised by:

  1. Logging into the Argo CD dashboard.

  2. Selecting the random-meme application.

  3. Clicking on the images-json ConfigMap in the Application Details Tree.

  4. Scrolling down in the overlay that appears and confirming your new image URL is listed in the Live Manifest YAML.

ex8.argocd live manifest

Summary

Congratulations! You learned how to:

  • Use a Argo CD to deploy a containerised application.

  • Create and merge a pull request after CI checks have passed.

  • Verify that Argo CD has deployed your changes as part of your CI/CD pipeline by checking the live manifest.