CI/CD with GitHub Actions and Argo CD

Deploying applications to a range of Kubernetes clusters at scale is no easy task. GitOps helps with defining and tracking the desired state of applications in the form of manifests in a source code repository. Changes to the desired state, for example the use of a newly-released container image, can automatically trigger the deployment process.

This session primarily focuses on GitHub Actions and Argo CD to automate the building and deployment process geared toward cloud-native applications. We’ll take a look at the CI pipeline that builds, tests, and releases code changes. Next, you will integrate the pipeline with the deployment process managed by Argo CD with the goal of avoiding manual interaction.

We won’t stop there. Enterprise requirements call for supporting progressive delivery patterns. Argo Rollouts take Argo CD to the next level. You will learn how to implement the blue-green and canary deployment strategies with Argo Rollouts.

By the end of this session, you will be able to implement automated CI/CD pipelines for your own Kubernetes environments. Production-ready, operational aspects of your Argo CD installation, like monitoring, observability and high availability, are not going to be covered.

Prerequisites:

  • A good understanding of the Continuous Integration/Continuous Delivery methodology.
  • Exposure to Git, GitHub & optionally GitHub Actions.
  • Working knowledge of containers and Kubernetes.

Benjamin Muschko

About Benjamin Muschko

Benjamin Muschko is a software engineer, consultant, and trainer with more than 20 years of experience in the industry. He specializes in cloud-native application development and transformation, container solutions, DevSecOps, and Continuous Integration/Continuous Delivery implementations. Ben is an author, a frequent speaker at conferences, and an avid open source advocate.

More About Benjamin »