# argo Published articles for argo. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## 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. ## Operationalize Redpanda Connect with GitOps DevFeed: [Operationalize Redpanda Connect with GitOps]() Original publisher: [Read original article]() Author: Ben Barkhouse Published: 2025-12-02T00:00:00Z Content type: tutorial Language: en Sources: [Redpanda]() Topics: [GitOps](), [Kubernetes](), [CI/CD](), [internal developer portal](), [Command-line interface](), [Git]() Tags: [argo](), [argo-cd](), [auditability](), [cli](), [deployment](), [developer-experience](), [github](), [gitops](), [kubernetes](), [redpanda-connect](), [security](), [yaml]() ### AI overview This tutorial explains how to operationalize Redpanda Connect with GitOps on Kubernetes. It covers declarative management through Git and Argo CD, deployment workflows, and the differences between standalone mode and Streams mode for running pipelines. ### Source excerpt Here's how to operationalize Redpanda Connect with GitOps for less manual ops, predictable deployments, and a standard workflow. ## 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. ## Configuring Slack Notifications with Argo Workflows DevFeed: [Configuring Slack Notifications with Argo Workflows]() Original publisher: [Read original article]() Author: Shawn Sesna Published: 2025-06-24T18:06:52Z Content type: tutorial Language: en Sources: [Codefresh]() Topics: [Kubernetes](), [CI/CD](), [Orchestration](), [Containers](), [YAML]() Tags: [applicationset](), [argo](), [argo-cd](), [ci-cd](), [clusters](), [containers](), [feature-flags](), [kubernetes](), [orchestration](), [product-and-tools](), [software-development](), [technical-guides](), [yaml]() ### AI overview This tutorial introduces Argo Workflows as an open source workflow engine for orchestrating parallel jobs and CI/CD pipelines on Kubernetes. It explains workflow definitions, containers, templates, dependencies, storage volumes, and workflow state. ### Source excerpt The acquisition of Codefresh gave me an exciting opportunity to learn new tech. Initially, I thought Argo was just Argo CD. I didn't realize that Argo consists of 4 distinct projects: A key feature of the Codefresh product is Promotion Flows, which makes heavy use of Argo Workflows. Promotion Flows add the ability to assign [...] The post Configuring Slack notifications with Argo Workflow - a learning experience 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. ## CI Shootout: Getting started with Jenkins, Concourse, Tekton and Argo Workflows DevFeed: [CI Shootout: Getting started with Jenkins, Concourse, Tekton and Argo Workflows]() Original publisher: [Read original article]() Author: Tom Godkin Published: 2023-10-04T11:05:39Z Content type: comparison Language: en Sources: [Blog - Container Solutions]() Topics: [ci](), [Self-hosted](), [Jenkins](), [Kubernetes]() Tags: [argo](), [ci](), [continuous-integration](), [helm](), [jenkins](), [kubernetes](), [self-hosted](), [workflows]() ### AI overview This comparison evaluates Jenkins, Concourse, Tekton, and Argo Workflows as self-hosted CI systems. It examines installation and configuration, along with introductory pipeline tasks, using deployments to an existing Kubernetes cluster. ### Source excerpt At EngineerBetter we've evaluated four self-hosted CI systems in order to compare them against each other: Jenkins, Concourse, Tekton and Argo Workflows. For each CI system we've created some pipelines that: ## Chainguard and CNCF conduct SLSA assessments for Argo and Prometheus projects DevFeed: [Chainguard and CNCF conduct SLSA assessments for Argo and Prometheus projects]() Original publisher: [Read original article]() Published: 2023-04-19T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [open-source-security](), [supply-chain-security](), [Prometheus](), [Open Source](), [Security](), [chainguard]() Tags: [argo](), [argo-cd](), [audits](), [chainguard](), [cncf](), [github](), [maintainers](), [open-source](), [prometheus](), [provenance](), [security](), [security-best-practices](), [slsa](), [slsa-levels](), [software-supply-chain-security](), [supply-chain-integrity](), [supply-chain-security]() ### AI overview Chainguard and CNCF assessed the software supply chain security of the Argo CD and Prometheus projects using the SLSA framework. Argo CD achieved SLSA Level 3 for source, build, and provenance, while Prometheus achieved Level 3 for source and build; the assessment recommended adding provenance generation to Prometheus build infrastructure. ### Source excerpt Chainguard and the CNCF partnered to conduct security assessments of Argo and Prometheus to ensure open source software projects apply security best practices.