The security and storage of secrets is one of the most controversial subjects when it comes to GitOps deployments. Some teams want to go “by the book” and use Git as the storage medium (in an encrypted form of course) while others accept the fact that secrets must be handled in a different way (outside of GitOps). There is no right or wrong answer here and depending on the organization requirements, either solution might be a great fit.

GitOps is a set of best practices that build upon the foundation of Infrastructure As Code (IAC) and expand the approach of using Git as the source of truth for Kubernetes configuration. These best practices are the driving force behind new Kubernetes deployment tools such as Argo CD and Flux as well as the Codefresh enterprise deployment platform. Adopting GitOps in a Kubernetes environment is not a straightforward task when it comes to secret management.

Since Codefresh launched our GitOps platform and Enterprise version of Argo CD and Argo Rollouts in November 2020, and extended that platform with Argo Workflows in March 2022 we’ve added numerous features, improved installation, management of GitOps instances, improved security, scalability, and so much more. Now, we’re helping our users scale software delivery across environments.

Amid all the activity and excitement at KubeCon and ArgoCon 2023 – including some exciting news of our own – the CNCF released the results of a new micro survey assessing trends in GitOps adoption. There’s a lot of great data tucked inside, and worth the read to find out what peers across the industry are saying about GitOps usage in their organizations.

Last month, we announced our new GitOps Environment dashboard that finally allows you to promote Argo CD applications easily between different environments.

DevOps Insights with Dennis: GitOps - The way of the Kubernetes professional.

The cognitive bias known as the streetlight effect describes our desire as humans to look for clues where it’s easiest to search, regardless of whether that’s where the answers are. For decades in the software industry, we’ve focused on testing our applications under the reassuring streetlight of GitOps. It made sense in theory: wait for changes to the codebase made by engineers, then trigger a re-test of your code. If your tests pass, you’re good to go.

Simply put, GitOps applies DevOps practices like version control and CI/CD to infrastructure management. The name GitOps, coined by Weavewerks, is from Git, an open-source version control system that allows teams to manage infrastructure using the same tools and orchestration processes they use for software development.

Defining multiple environments in Argo CD and promoting an application between them is one of most popular questions for companies that adopt GitOps for their applications. While we have offered several guidelines in the past for organizing your GitOps environments, today we are taking it further by announcing a complete product that helps you visualize the full lifecycle of an application as it moves through different stages. Meet the new Codefresh GitOps Environment Dashboard!