To push or pull ?

As the DevOps team considered the current versioning issue and updating the Kubernetes manifest files, they also wondered whether the GitOps tool should be inside or outside of a cluster.

Some of the benefits that the team came up with were things like direct cluster access. This was especially helpful with the monitoring and enforcement of Kubernetes resources. The tool would also have immediate knowledge of the health of the resources. Another benefit is that the execution engine should be fairly small with a low cost of ownership. Lastly, since the execution happens within the cluster, all data and secrets reside in the cluster as well. This would prevent the need for consistent polling for information from an external source.

There were also some benefits of having a GitOps execution engine live outside of the cluster. Most importantly, the execution engine is not dependent upon the life and health of the cluster. If the cluster, or the node that the execution...