Continuous deployment GitOps – originalist and purist

One consideration that the DevOps team had was the possibility of tying in a tool like Argo CD with Ansible or Harness. This integration would allow the teams using Kubernetes to still have the continuous delivery portion automated, but also allow for the self-healing and automated pruning features of Argo CD to enforce the desired end state on the clusters during and after a deployment. But exploring this integration resulted in two main concerns related to inconsistent processes and automated execution led the DevOps team to abandon the idea. They realized that since Argo CD only works on Kubernetes clusters, they would have an inconsistent process with any application that was not Kubernetes-based. Also, Argo CD can only leverage the automated pruning and self-healing features if the automated syncing feature is turned on.

What the team wanted, but couldn't find, was a deployment tool like Argo CD, with the automated...