Common verified GitOps tools

The process of designing the requirements for verified GitOps gave the team a better understanding of where they should spend their time. The DevOps team has experienced building an in-house solution before, mainly avoid the costs of buying a tool. But they have also experienced the significant administration and maintenance effort associated to building a tool. Although Ansible had offered a wide range of customization capabilities, it was essentially a tool that they would have to build out and maintain. The other problem with Ansible was that although the files could be stored in a Git repository and pulled at runtime, the tool required the Git repository to be pulled down before every execution.

After performing market research for a verified GitOps tool, the team found Harness, which had a very promising solution. The tool allowed the team to support Kubernetes, serverless, and server-based platforms. It had a native code conversion process that...