Two of the most popular guides we’ve written are the GitOps promotion guide and the ApplicationSet guide. Used together, they explain an end-to-end solution for organizing your GitOps applications and promoting them between different environments, while keeping things DRY by using application sets. Both of these guides use Kustomize. We offered some hints for Helm users, but this is a dedicated guide for Helm applications.

Integrating Cloudsmith, a cloud-native artifact management platform, with Codefresh enhances your CI/CD workflows in several significant ways. Read this blog to learn more about this powerful combination, and its automation of artifact handling and simplification of deployments!

With the increasing adoption of Kubernetes in recent years, there are various means and tools for achieving continuous delivery to Kubernetes. While it is possible to create a consistent CI/CD pipeline up to deploying to Kubernetes using CI/CD tools like CircleCI, there has been a rise in cases combining dedicated CD tools like FluxCD and ArgoCD to achieve this as well. A common aspect among these CD-dedicated tools is their adoption of GitOps.

GitOps is a framework that combines the principles of software development and continuous integration, continuous delivery (CI/CD) to automate and manage application configurations and infrastructure using Git.

This blog will be the second in a three-part blog series where we explore the benefits of the GitOps practice, how to get the most from GitOps, and how to measure and maintain success. Here is what you can expect from the series: We’ll dive into the practice of GitOps in this blog, defining and understanding what an efficient workflow can produce. Here you’ll put the principles of GitOps into practice, exploring how infrastructure as code (IaC) can help you get more done with fewer resources.

GitOps is a game-changer for managing infrastructure and deployments using Git as the single source of truth. It makes DevOps processes more efficient, reliable, and traceable. For developers and organizations, GitOps not only speeds up development but also improves security and compliance. Today, I’ll break down what GitOps is, why it’s important, and review some top GitOps tools to help you on your journey.

Teams adopting GitOps often ask how to use secrets with Argo CD. The official Argo CD page about secrets is unopinionated by design and simply lists a set of projects that can help you with secrets. We’ve seen several approaches to secret management. These include sealed secrets, the Argo CD Vault plugin, and the External Secret Operator. In this post, we showcase the External Secret Operator and Hashicorp Vault and focus on 2 important aspects.

I am super excited to announce the release of our complete guide on how to run GitOps with Qovery! GitOps revolutionizes infrastructure management by using Git repositories as the source of truth, offering a more streamlined, reliable, and automated workflow.

This blog will be the first in a three-part blog series where we explore the benefits of the GitOps practice, how to get the most from GitOps, and how to measure and maintain success. Here is what you can expect from the series: Let’s start at the very beginning — what is GitOps? If you want to start to build a single source of truth for both your code and your infrastructure, if you want to ensure your deployments are automated and reliable, you’ll want to know GitOps.

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.