Single Helm Chart for All Kubernetes Deployments using ArgoCD (Mono Chart)

How to stop using multiple Helm charts for application deployments

Kubernetes is doing what Linux did to the world many years ago when it took over the computing space of enterprise computing, giving everyone the power to customize and build operating systems away from Microsoft Windows and Apple’s Mac. Kubernetes is making it easier to manage containers at a large scale and improving the efficiency of applications deployed in this environment, using the right set of configurations which I described in my previous article here. When the configurations are ready to be deployed in the Kubernetes cluster, what is the most efficient way to perform this deployment and avoid DRY (Don’t Repeat Yourself)? This is a common term used in the IaC (Infrastructure as Code) world, which implies that it is important to avoid repetition when writing code. In Terragrunt, DRY is implementable due to the following features; code reuse, shared configuration, and helper functions. Can this concept be applied in Kubernetes deployments? Let’s talk about DRY in Kubernetes applications.

DRY in Kubernetes Deployment

In most cases when deployments are to be done to Kubernetes. There is a lot of repetition of YAML files performing…