GitOps – what and why

One of the major issues when adopting any new process is the ability to implement that process effectively and efficiently. The importance and impact of the process will directly correlate to the amount of time and effort required. But for the DevOps team, they were needing to implement both a GitOps practice and a new tool. And to add to the difficulty of a parallel implementation process, the team had to figure out the best scaling process for their applications.

In the case of Kubernetes and Hem charts, one of the major issues is manifest sprawl, which the DevOps team had experienced before. Their current hurdle was figuring out how best to manage and maintain that manifest sprawl when many of the applications are moving to containers and Kubernetes. The typical solution is to have a Git repository of many different Helm charts, one for each microservice, and have the teams maintain them. But that explosion of Helm charts would bring with it a massive...