Benefits and drawbacks of originalist GitOps

As the DevOps team dove deeper into the world of originalist GitOps and tools such as Argo CD, they discovered some very promising benefits of adopting this type of process. They found that Argo CD allowed for the mandatory Kubernetes manifests to be the main driver for configuration and change to microservice resources in the cluster. And since the developers were already used to using git, the adoption process of originalist GitOps automation would not be too much of a burden for the developers to work through.

By treating the git repository and helm chart as the source of truth for the desired end state, the user should always be able to see what microservice configuration is in the cluster based on what the git repository shows. Also, since git has native versioning, a rollback to a previous version is as easy as reverting a version in git and letting Argo CD handle the deployment part.

One other benefit that the team found was...