# argo-cd Argo CD is a declarative GitOps continuous delivery tool for Kubernetes. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Build a unified CI/CD control plane with Red Hat Developer Hub DevFeed: [Build a unified CI/CD control plane with Red Hat Developer Hub]() Original publisher: [Read original article]() Author: Rishabh Singh Published: 2026-09-17T13:16:44Z Content type: tutorial Language: en Sources: [Red Hat](), [Red Hat Developer]() Topics: [internal developer portal](), [Backstage](), [argo-cd](), [CI/CD](), [Platform Engineering]() Tags: [argo-cd](), [backstage](), [ci-cd](), [cognitive-load](), [developer-portal](), [developer-productivity](), [guide](), [how-to](), [onboarding](), [openshift](), [platform](), [platform-engineering]() ### AI overview This guide explains how platform engineers can deploy and configure Red Hat Developer Hub as a unified developer portal for Red Hat OpenShift, Argo CD, Tekton, Quay, and related deployment information. It describes aggregating pipeline runs, deployment health, and container image tags in one view, along with software templates for self-service project bootstrapping. ### Source excerpt If your engineering teams waste time context-switching between Red Hat OpenShift, Argo CD, Tekton, and Quay, your platform needs a unified developer portal. The post Build a unified CI/CD control plane with Red Hat Developer Hub appeared first on Red Hat Developer. ## Beyond the sync: Argo CD needs an Enterprise Control Plane DevFeed: [Beyond the sync: Argo CD needs an Enterprise Control Plane]() Original publisher: [Read original article]() Author: Eric Minick Sudarshan Purohit Published: 2026-09-16T20:28:57.610955Z Content type: opinion Language: en Sources: [Harness Blog]() Topics: [argo-cd](), [GitOps](), [Orchestration](), [DevOps](), [Platform Engineering](), [Deployment](), [Artificial Intelligence]() Tags: [argo-cd](), [deployment](), [gitops](), [governance](), [orchestration](), [platform-engineering](), [verification]() ### AI overview This article argues that Argo CD's manifest synchronization is only one part of enterprise software delivery. It describes how scaling GitOps can create operational toil and Argo sprawl, and proposes an enterprise control plane with workflow orchestration, governance, and deployment verification. ### Source excerpt Scaling GitOps? Argo CD is great for syncing manifests, but enterprise delivery requires workflow orchestration, governance, and AI verification. | Blog ## Implementing GitOps from Infrastructure to DB Operators to Unify Ops for Kubernetes Databases DevFeed: [Implementing GitOps from Infrastructure to DB Operators to Unify Ops for Kubernetes Databases]() Original publisher: [Read original article]() Author: Sucahyo Ardy Prasetiyo Published: 2026-09-16T08:57:10Z Content type: tutorial Language: en Sources: [SeveralNines]() Topics: [GitOps](), [Kubernetes](), [Terraform](), [argo-cd](), [ClusterControl](), [Databases](), [opentofu]() Tags: [argo-cd](), [clustercontrol](), [databases](), [gitops](), [hybrid-operations](), [infrastructure](), [kubernetes](), [opentofu](), [sovereign-dbaas](), [terraform]() ### AI overview This article describes a layered GitOps approach for Kubernetes database platforms: manage infrastructure with Terraform or OpenTofu, manage Kubernetes deployments with Argo CD, and standardize operations for operator-managed databases with ClusterControl. It explains how declarative configuration and drift reconciliation differ between Terraform and Argo CD, and compares infrastructure automation options including Atlantis and Flux tf-controller. ### Source excerpt Most platform teams already use GitOps for their Kubernetes apps. The config lives in Git, Argo CD applies it, and deployments are predictable. But look one layer down and things get messy. Infrastructure setup is often still done by hand, running Terraform locally or through scattered scripts. Database operations, especially for databases running through Kubernetes [...] The post Implementing GitOps from Infrastructure to DB Operators to Unify Ops for Kubernetes Databases appeared first on Severalnines. ## Best Kubernetes Infrastructure as Code Tools in 2026 DevFeed: [Best Kubernetes Infrastructure as Code Tools in 2026]() Original publisher: [Read original article]() Author: Pulumi Content Team Published: 2026-08-14T00:00:00Z Content type: comparison Language: en Sources: [Pulumi]() Topics: [Infrastructure as code](), [Kubernetes](), [Terraform](), [argo-cd](), [Helm charts](), [GitOps](), [flux](), [opentofu](), [Amazon EKS](), [AWS CloudFormation](), [VPC](), [AWS IAM]() Tags: [argo-cd](), [cloudformation](), [code](), [comparisons](), [devops](), [flux](), [general](), [gitops](), [helm](), [helm-charts](), [iam](), [infrastructure](), [infrastructure-as-code](), [kubernetes](), [opentofu](), [platform-engineering](), [terraform](), [vpc]() ### AI overview This comparison explains that Kubernetes infrastructure as code spans cluster and cloud provisioning, in-cluster workload definition, and continuous delivery and reconciliation. It presents Pulumi and Terraform or OpenTofu as general-purpose provisioning options, Helm and Kustomize for workload templating, and Argo CD and Flux for GitOps reconciliation. ### Source excerpt There is no single best Kubernetes infrastructure as code tool, because "Kubernetes IaC" actually spans three different jobs. For provisioning the cluster and its cloud dependencies, Pulumi and Terraform (or OpenTofu) are the strongest general-purpose options. For templating and packaging workloads, Helm and Kustomize dominate. For continuous reconciliation once things are running, Argo CD and Flux lead the GitOps category. The right stack usually combines one tool from each layer, not a single tool that claims to do all three. What counts as infrastructure as code for Kubernetes? Kubernetes infrastructure as code work splits into three layers that get conflated constantly, and the confusion is where most tool comparisons go wrong. The cluster and cloud layer provisions the things Kubernetes itself sits on top of: the managed control plane (EKS, GKE, AKS), node pools, the VPC and subnets, IAM roles, load balancers, and cluster add-ons. Terraform, Pulumi, and cloud-native tools like CloudFormation operate here. The in-cluster workload layer defines what runs on the cluster once it exists: Deployments, Services, ConfigMaps, CustomResourceDefinitions, and the Helm charts or Kustomize overlays that template them. This is where Helm, Kustomize, and Crossplane's custom resources live. The delivery and reconciliation layer keeps what's declared in Git in sync with what's actually running on the cluster, continuously, rather than as a one-shot apply. Argo CD and Flux own this layer, and they consume the output of the other two rather than replacing them. Most real Kubernetes platforms use tools from at least two of these layers together. A team might provision EKS with Terraform, package its application with Helm, and let Argo CD reconcile it continuously. Knowing which layer a tool actually addresses, rather than treating "Kubernetes IaC" as one shopping list, is the first decision that matters. Pulumi provisions the cluster and the workloads on it in the same language Pul ## Harness AI Verification and Rollback for Argo CD: Limitations of Static Thresholds DevFeed: [Harness AI Verification and Rollback for Argo CD: Limitations of Static Thresholds]() Original publisher: [Read original article]() Author: Prasad Satam Akshit Madan Shubhendu Patidar Published: 2026-06-17T00:00:00Z Content type: opinion Language: en Sources: [Harness Blog]() Topics: [argo-cd](), [GitOps](), [Kubernetes](), [Artificial Intelligence](), [Prometheus]() Tags: [ai](), [argo-cd](), [gitops](), [harness](), [kubernetes](), [machine-learning](), [maintenance](), [progressive-delivery](), [prometheus](), [rollback](), [software-delivery](), [statistical-significance]() ### AI overview This vendor commentary argues that Argo Rollouts Analysis Templates can be difficult to maintain because they rely on manually defined static thresholds. It presents Harness AI Verification and Rollback as a context-aware alternative that uses unsupervised machine learning and service health trajectories to assess deviations and support rollbacks. ### Source excerpt Stop the maintenance nightmare of static thresholds. Learn how Harness AI Verification and Rollback provides context-aware safety for Argo CD. | Blog ## Faster than the advisory DevFeed: [Faster than the advisory]() Original publisher: [Read original article]() Published: 2026-06-10T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [Security](), [argo-cd](), [GitOps](), [Vulnerabilities](), [Kubernetes](), [chainguard os](), [anthropic](), [Artificial Intelligence]() Tags: [ai](), [anthropic](), [argo-cd](), [chainguard-containers](), [chainguard-os](), [container-images](), [gitops](), [kubernetes](), [scanner-advisories](), [security](), [vulnerabilities](), [wolfi]() ### AI overview The article explains how Chainguard Factory delivered a patched Argo CD version to Wolfi and Chainguard OS before the related security advisory reached GitHub's global advisory database. It argues that automated upstream tracking and rapid remediation are increasingly important because vulnerability exploitation and AI-assisted discovery are outpacing traditional disclosure timelines. ### Source excerpt Chainguard often ships security fixes before advisories reach scanners. Learn why upstream speed matters in the era of AI-driven exploits. ## From Tickets to Pull Requests: Running Cilium in a GitOps Platform DevFeed: [From Tickets to Pull Requests: Running Cilium in a GitOps Platform]() Original publisher: [Read original article]() Author: Dean Lewis Published: 2026-06-02T12:56:19Z Content type: tutorial Language: en Sources: [Isovalent - The latest articles covering eBPF-based Networking, Observability, and Security]() Topics: [Cilium](), [GitOps](), [argo-cd](), [Kyverno](), [ci]() Tags: [argo](), [argo-cd](), [ci](), [cilium](), [gitops](), [hubble-timescape](), [kyverno](), [network-policy](), [platform-engineering](), [pull-requests]() ### AI overview The article describes running Cilium as part of a GitOps platform using Argo CD, Kyverno, and isopolicy CI. ### Source excerpt Run Cilium as a GitOps platform: use Argo CD, Kyverno, and isopolicy CI. ## Anatomy of a Pull Request Generator DevFeed: [Anatomy of a Pull Request Generator]() Original publisher: [Read original article]() Author: Shawn Sesna Published: 2025-10-02T14:48:57Z Content type: tutorial Language: en Sources: [Codefresh]() Topics: [argo-cd](), [pull-requests](), [Kubernetes](), [Git](), [bitbucket](), [Deployment]() Tags: [argo-cd](), [bitbucket](), [deployment](), [git](), [kubernetes](), [pull-request](), [technical-guides]() ### AI overview This tutorial explains Argo CD's Pull Request Generator, an ApplicationSet deployment type that monitors a Git repository for matching pull requests, deploys their manifests to ephemeral environments, and removes the deployed resources when the pull request closes. It also breaks down the manifest configuration, including polling intervals and Bitbucket Server settings. ### Source excerpt Argo CD has built a number of Generators to support various scenarios that developers need when using Argo CD and Kubernetes. In this post, I'll be discussing the Pull Request Generator. A Pull Request Generator is an Argo CD Application Set deployment type that is configured to "watch" a Git repository for Pull Requests (PRs). [...] The post Anatomy of a Pull Request Generator appeared first on Codefresh. ## Top 30 Argo CD Anti-Patterns to Avoid When Adopting Gitops DevFeed: [Top 30 Argo CD Anti-Patterns to Avoid When Adopting Gitops]() Original publisher: [Read original article]() Author: Kostis Kapelonis Published: 2025-08-19T16:36:21Z Content type: tutorial Language: en Sources: [Codefresh]() Topics: [argo-cd](), [GitOps](), [Kubernetes](), [Helm charts]() Tags: [argo-cd](), [best-practices](), [devops](), [gitops](), [helm-charts](), [kubernetes]() ### AI overview This article explains common anti-patterns teams encounter when adopting Argo CD and GitOps. It focuses on understanding Argo CD's declarative setup and storing applications and related Kubernetes resources in Git so deployments and configuration can be recreated reliably. ### Source excerpt The time has finally come! After the massive success of our Docker and Kubernetes guides, we are now ready to see several anti-patterns for Argo CD. Anti-patterns are questionable practices that people adopt because they seem like a good idea at first glance, but in the long run, they make processes more complicated than necessary. [...] The post Top 30 Argo CD Anti-Patterns to Avoid When Adopting Gitops appeared first on Codefresh. ## Using Argo CD's targetRevision Field for Application Promotion DevFeed: [Using Argo CD's targetRevision Field for Application Promotion]() Original publisher: [Read original article]() Author: Kostis Kapelonis Published: 2025-08-01T13:57:26Z Content type: tutorial Language: en Sources: [Codefresh]() Topics: [argo-cd](), [GitOps](), [Kubernetes](), [Helm charts]() Tags: [argo](), [argo-cd](), [argocd](), [auditability](), [best-practices](), [continuous-deployment](), [gitops](), [helm-charts](), [kubernetes](), [usability]() ### AI overview This guide explains how Argo CD's targetRevision field tracks Git repositories or Helm chart versions and why using it as a promotion mechanism for developer applications can create usability and auditability problems. It recommends using targetRevision: HEAD in ApplicationSets, with specific Helm versions used sparingly for mostly static infrastructure applications. ### Source excerpt In our big guide on how to use ApplicationSets for Argo CD applications, we explained the best practice of having a 3-level structure for all manifests with a clear distinction between Argo CD Application files and Kubernetes resource files. In that article, we also outlined several anti-patterns that we have seen in the wild, meaning [...] The post Abusing the Target Revision Field for Argo CD Promotions appeared first on Codefresh. ## Distribute Your Argo CD Applications to Different Kubernetes Clusters Using Application Sets DevFeed: [Distribute Your Argo CD Applications to Different Kubernetes Clusters Using Application Sets]() Original publisher: [Read original article]() Author: Kostis Kapelonis Published: 2025-06-17T10:44:02Z Content type: tutorial Language: en Sources: [Codefresh]() Topics: [argo-cd](), [Kubernetes]() Tags: [applications](), [applicationset](), [argo](), [argo-cd](), [argo-cd-kubernetes](), [article](), [best-practices](), [clusters](), [how-to](), [kubernetes](), [kubernetes-clusters](), [series]() ### AI overview This guide explains how to use Argo CD ApplicationSets to distribute multiple applications across multiple Kubernetes clusters. It covers cluster selection, environment-specific settings, cluster labels, and combining the Git and Cluster generators. ### Source excerpt In the previous article in this series, we explained how Argo CD application Sets work and how to use them for organizing your applications in different environments or groups. We received a lot of positive feedback from our readers, and many teams now use the associated Git repository as a starting point for their own [...] The post Distribute Your Argo CD Applications to Different Kubernetes Clusters Using Application Sets appeared first on Codefresh. ## Combine the Codefresh GitOps Cloud with your existing Argo CD instance DevFeed: [Combine the Codefresh GitOps Cloud with your existing Argo CD instance]() Original publisher: [Read original article]() Author: Kostis Kapelonis Published: 2025-04-30T08:16:16Z Content type: article Language: en Sources: [Codefresh]() Topics: [argo-cd](), [GitOps](), [Kubernetes](), [Continuous Deployment (CD)](), [Deployment](), [Git]() Tags: [argo](), [argo-cd](), [argocd](), [codefresh](), [continuous-deployment](), [declarative](), [deployment](), [git](), [gitops](), [kubernetes](), [product-and-tools](), [pull-request]() ### AI overview This article explains Argo CD as a Kubernetes-native continuous deployment tool and describes how Codefresh GitOps Cloud can work with an existing Argo CD instance. It covers GitOps workflows, application promotion across clusters, declarative configuration, approvals, and deployment synchronization. ### Source excerpt We recently announced the new Codefresh GitOps Cloud, the easiest way to promote changes across Argo CD applications-even across different clusters. With Codefresh GitOps Cloud, you can model your own promotion flow with a graphical editor (although YAML is still available). You define exactly how an application reaches production, including all the requirements and approval [...] The post Combine the Codefresh GitOps Cloud with your existing Argo CD instance appeared first on Codefresh. ## Introducing Codefresh GitOps Cloud - Seamless environment promotions across clusters using your existing Argo CD DevFeed: [Introducing Codefresh GitOps Cloud - Seamless environment promotions across clusters using your existing Argo CD]() Original publisher: [Read original article]() Author: Kostis Kapelonis Published: 2025-03-30T23:48:40Z Content type: release Language: en Sources: [Codefresh]() Topics: [GitOps](), [argo-cd](), [Automation](), [Cloud]() Tags: [argo-cd](), [automation](), [cloud](), [codefresh](), [continuous-deployment](), [gitops](), [kubernetes](), [product-and-tools](), [reconciliation](), [sync]() ### AI overview Codefresh announces GitOps Cloud, an offering for GitOps deployments that supports multi-environment application promotions across clusters using existing Argo CD. The article also explains GitOps concepts and practices, including version-controlled desired state and continuous reconciliation. ### Source excerpt We're excited to announce our new Codefresh GitOps Cloud offering that lets you bring your GitOps deployments to the next level. You get: In this blog post, we'll dive into some of the key features of Codefresh GitOps Cloud. Multi-environment application promotions with Argo CD As more organizations adopt Argo CD, platform engineers need to [...] The post Introducing Codefresh GitOps Cloud - Seamless environment promotions across clusters using your existing Argo CD appeared first on Codefresh. ## Speeding Up Data Imports for Deployment Previews with PVC Snapshotting DevFeed: [Speeding Up Data Imports for Deployment Previews with PVC Snapshotting]() Original publisher: [Read original article]() Author: Nick Nikitas Published: 2024-01-23T12:48:14Z Content type: article Language: en Sources: [Blueground Engineering blog]() Topics: [Deployment](), [Kubernetes](), [Developer experience](), [pull-requests](), [data](), [Databases](), [argo-cd](), [Amazon Web Services]() Tags: [argo-cd](), [aws](), [data](), [databases](), [deployment](), [developer-experience](), [devops](), [kubernetes](), [platform](), [provisioning](), [pull-requests]() ### AI overview This article describes a bottleneck in deployment previews caused by importing de-identified production data into ephemeral environments. It introduces PVC snapshotting as the method used to provision previews more promptly and outlines drawbacks of the previous Argo CD- and Kubernetes-based approach, including lengthy waits, limited scalability, and errors. ### Source excerpt Check out our previous blog post to learn about implementing Deployment Previews, a concept popularized by Netlify and Vercel in Kubernetes. This post will explain our method of provisioning them promptly, rather than keeping our engineers waiting, using PVC snapshotting. This December, we went out and asked our colleagues to