Summary

In the current chapter, we embarked on a detailed journey to understand and define CD. We began by exploring two strategies for CD: universal CI with master-only CD and the integrated model of universal CI and CD. In the process, we delved into the core concepts of GitOps and its intrinsic connection to CD. Our planning phase focused on the intricacies of high-level CD architecture, examining the Helm chart for our web application and establishing a foundation for both staging and production environments. This setup entailed creating namespaces and secrets in AKS, configuring insecure registries, and more.

Subsequently, we navigated the installation and configuration of Argo CD and its integration with Jenkins to bolster automation capabilities. Among other skills, we mastered creating an Argo CD user and generating its associated token. Additionally, we honed our ability to seamlessly link a GitHub repository to Argo CD, optimizing application management within the platform...