Benefits and drawbacks of purist GitOps

GitOps seemed significantly easier when the DevOps team only had to consider support for multiple Kubernetes clusters. There were multiple tools available to support the requirements in a native way. Developers wouldn't have to be trained on how they would configure any additional files. Setting up the tools had a minimal requirement on the teams. The only issue that the DevOps team had to consider was which GitOps tool was going to fit their scaling needs the best.

The increased support scope from engineering leadership meant that the DevOps team couldn't use the original set of GitOps tools, such as Argo CD and Jenkins X. And not only that, but the available tools that could support a GitOps style across all of the required architectures were non-existent. No tool had been built that natively supports a purist GitOps process for server-based, container-based, and serverless architecture deployments. The DevOps team had to resort...