Can we get rid of the part of CI/CD pipelines that are modifying GitOps manifests repositories with new releases? Can we use Argo CD Image Updater to streamline part of our processes?Continue reading
Tag Archives: Argo
Tekton vs. Argo Workflows – Kubernetes-Native CI/CD Pipelines
Which self-managed kubernetes-native CI/CD pipeline is the best choice? Is it Tekton or Argo Workflows? Which one should you pick?Continue reading
Automation of Everything – How To Combine Argo Events, Workflows & Pipelines, CD, and Rollouts
What do we get if we combine events, workflows, GitOps, progressive delivery, and secrets management? The short answer is that we get automation of everything in Kubernetes in a way that we should be operating in 2021.
We’ll combine Argo Events, Workflows & Pipelines, CD, and Rollouts and sprinkle all that with SealedSecrets, Kaniko, and a few other tools.
Argo Events – Event-Based Dependency Manager for Kubernetes
Argo Events is an event-based dependency manager for Kubernetes that helps us connect applications through events.
Argo Rollouts – Canary Deployments Made Easy In Kubernetes
Argo Rollouts provides advanced deployment capabilities. It supports blue-green and canary strategies. It integrates with Ingress controllers and service meshes. Argo Rollouts can query metrics from various providers and make decisions whether to roll forward or to roll back based on the results.
Environments Based On Pull Requests (PRs): Using Argo CD To Apply GitOps Principles On Previews
Release frequency keeps increasing and, with it, the need to get away from static environments like staging, integration, and other permanent setups. Dynamic environments based on pull requests are probably the best example of a need for a much higher level of dynamism. Kubernetes allows us to easily create whatever we need, and destroy what is not in use. There is no need for anything, especially not environments to be permanent, except for production. We can get far in that direction by combining GitOps practices and Argo CD in a way that each pull request (PR) creates a new environment that is destroyed when a PR is closed. By doing that, we can improve efficiency while, at the same time, reducing the costs.
Argo CD: Applying GitOps Principles To Manage Production Environment In Kubernetes
Argo CD is a declarative GitOps deployment tool for Kubernetes.
It is one of the best, if not the best tool we have today to deploy applications inside Kubernetes clusters. It is based on GitOps principles, and it is a perfect fit to be a part of continuous delivery pipelines. It provides all the building blocks we might need if we would like to adopt GitOps principles for deployments and inject them inside the process of application lifecycle management.
Argo CD is a tool that helps us forget the existence of
helm install, and similar commands. It is a mechanism that allows us to focus on defining the desired state of our environments and pushing definitions to Git. It is up to Argo CD to figure out how to converge our desires into reality.