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.

Progressive delivery is an advanced deployment method that allows you to gradually shift production traffic to a new version with zero downtime. Argo Rollouts is a Kubernetes controller that enables you to perform progressive deployments such as blue/green and canaries on your Kubernetes cluster. At Codefresh, we love Argo Rollouts and have covered several use cases so far such as smoke tests, metrics, config-maps and even performing deployments for multiple microservices.

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.

At Codefresh, we are always happy to see companies and organizations as they adopt Argo CD and get all the benefits of GitOps. But as they grow we see a common pattern: It is at this point that organizations come to Codefresh and ask how we can help them scale out the Argo CD (and sometimes Argo Rollouts) initiative in the organization. After talking with them about the blockers, we almost always find the same root cause.

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!

Last year we launched the Codefresh delivery platform powered by Argo. After the initial launch we started collecting feedback from all companies that tried it (as well as existing customers) and cataloged all feature requests and implementation ideas. The main goal is always to iterate quickly and address the most common issues in the most efficient way possible.

In the previous article of the series, we explained how to use Configmap generators in order to use Progressive Delivery for your configuration (and not just the container images). In this post, we will also cover another popular question: how to use Argo Rollouts with multiple services. Argo Rollouts is a Kubernetes controller that allows you to perform advanced deployment methods in a Kubernetes cluster. By default, it only supports a single service/application.

In our previous article about Database migrations we explained why you should treat your databases with the same respect as your application source code. Database migrations should be fully automated and handled in a similar manner to applications (including history, rollbacks, traceability etc).