# progressive delivery Published articles for progressive delivery. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Software Delivery Platform: Key Features & How to Evaluate DevFeed: [Software Delivery Platform: Key Features & How to Evaluate]() Original publisher: [Read original article]() Author: Eric Minick Published: 2026-08-11T00:00:00Z Content type: article Language: en Sources: [Harness Blog]() Topics: [Software](), [CI/CD](), [Continuous Delivery (CD)](), [Continuous integration]() Tags: [audit](), [automation](), [blog](), [ci-cd](), [ci-cd-pipeline](), [governance](), [how-to](), [progressive-delivery](), [rollback](), [scalability](), [security](), [software-delivery](), [visibility]() ### AI overview This article explains how a software delivery platform differs from a standalone CI/CD tool. It describes a platform as an integrated system covering the full after-code lifecycle, including continuous integration, continuous delivery, security, governance, insights, coordination, and rollback, then outlines criteria for evaluating vendors. ### Source excerpt A software delivery platform isn't just a CI/CD tool. Get the must-have feature checklist and the demo questions to use when evaluating vendors. | Blog ## How to Build an A/B Testing Framework for Modern CI/CD Pipelines DevFeed: [How to Build an A/B Testing Framework for Modern CI/CD Pipelines]() Original publisher: [Read original article]() Author: Aaron Newcomb Published: 2026-08-10T00:00:00Z Content type: tutorial Language: en Sources: [Harness Blog]() Topics: [A/B Testing](), [CI/CD](), [CI/CD Pipeline](), [feature flags](), [progressive delivery](), [Monitoring]() Tags: [a-b-testing](), [ci-cd](), [feature-flags](), [how-to](), [monitoring](), [progressive-delivery](), [rollback](), [verification]() ### AI overview This tutorial explains how to integrate A/B testing into CI/CD pipelines using feature flags, progressive delivery, real-time metrics, automated verification, and rollback controls. It argues that deployment should be decoupled from release so teams can validate changes before full rollout. ### Source excerpt Learn how to build an A/B testing framework in your CI/CD pipeline. Accelerate software delivery, reduce risk, and boost innovation. Start now! | Blog ## Blue Green and Canary Deployments Explained DevFeed: [Blue Green and Canary Deployments Explained]() Original publisher: [Read original article]() Author: Pramodh Kumar M Published: 2026-08-09T16:30:08Z Content type: tutorial Language: en Sources: [Kubernetes - KodeKloud Blog | DevOps, Cloud, Kubernetes, AI Tutorials & More]() Topics: [Deployment](), [Software](), [Database]() Tags: [argo-rollouts](), [automation](), [blue-green-and-canary-deployments](), [ci-cd](), [ci-cd-pipeline](), [cloud](), [database](), [deployment](), [deployment-strategies](), [devops](), [dora-change-failure-rate](), [expand-and-contract-migration](), [feature-flags](), [guide](), [kubernetes](), [progressive-delivery](), [release-management](), [rollback](), [rolling-update](), [schema](), [sre](), [traffic-splitting](), [zero-downtime-deployment]() ### AI overview This guide explains blue-green and canary deployment strategies for replacing running software versions. It emphasizes that effective rollback depends on detecting problems with reliable metrics and that database schema changes can limit reversibility. ### Source excerpt Both strategies buy you the same thing, which is a cheap way to be wrong. The mechanism is the easy part, and the two hard parts are noticing you are wrong and dealing with the database. ## Progressive Delivery with Argo Rollouts, Isovalent and Gateway API DevFeed: [Progressive Delivery with Argo Rollouts, Isovalent and Gateway API]() Original publisher: [Read original article]() Author: Christian Hernandez Published: 2026-08-06T07:01:00Z Content type: tutorial Language: en Sources: [Isovalent - The latest articles covering eBPF-based Networking, Observability, and Security]() Topics: [progressive delivery](), [Argo Rollouts](), [gateway]() Tags: [argo-rollouts](), [delivery](), [gateway](), [progressive-delivery]() ### AI overview This article explains how progressive delivery controls traffic to newly deployed Pods, focusing on header-based canary deployments with Argo Rollouts and Gateway API. ### Source excerpt Progressive delivery is not only about creating the new Pods, it is also about controlling which traffic reaches them. This blog explores Header-based canaries with Argo Rollouts and Gateway API ## Native AI Agent Deployment in Harness Continuous Delivery DevFeed: [Native AI Agent Deployment in Harness Continuous Delivery]() Original publisher: [Read original article]() Author: Akshit Madan Published: 2026-07-21T00:00:00Z Content type: article Language: en Sources: [Harness Blog]() Topics: [AI Agent](), [Deployment](), [Continuous Delivery (CD)](), [Security](), [Software](), [agent observability]() Tags: [agentic](), [ai](), [ai-agent](), [audit-trail](), [continuous-delivery](), [deployment](), [harness](), [progressive-delivery](), [security]() ### AI overview This Harness article introduces agent deployment in Harness Continuous Delivery, with governed pipelines, native runtime support for platforms including Google's Agent Runtime and Amazon Bedrock AgentCore, progressive delivery, policy controls, and audit trails. It explains deployment as a critical stage of the agent development lifecycle and describes coordinating agents with backend services, database changes, and prompt or model configuration. ### Source excerpt Deploy AI agents with Harness Continuous Delivery using governed pipelines, native runtime support, progressive delivery, and built-in security. | Blog ## 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 ## Azure Deployment Strategies & CI/CD Best Practices DevFeed: [Azure Deployment Strategies & CI/CD Best Practices]() Original publisher: [Read original article]() Author: Chinmay Gaikwad Published: 2026-06-09T00:00:00Z Content type: tutorial Language: en Sources: [Harness Blog]() Topics: [Azure](), [Deployment](), [CI/CD](), [feature flags](), [GitOps](), [Infrastructure as code](), [observability]() Tags: [aks](), [azure](), [best-practices](), [ci](), [ci-cd](), [deployment](), [deployment-strategies](), [feature-flags](), [gitops](), [harness](), [iac](), [observability](), [progressive-delivery]() ### AI overview This guide explains Azure deployment strategies and CI/CD practices for safer software delivery. It covers canary, blue-green, and rolling deployments, feature flags, GitOps, infrastructure as code, pipeline controls, and observability-driven rollback, including examples involving AKS and other Azure workloads. ### Source excerpt Master Azure deployment with CI/CD, canary releases, feature flags, GitOps, and IaC. Learn how progressive delivery and Harness help teams ship faster, safer, and with fewer incidents. | Blog ## With AI, The Proof Is in Production DevFeed: [With AI, The Proof Is in Production]() Original publisher: [Read original article]() Author: Joshua Klein Published: 2026-06-09T00:00:00Z Content type: opinion Language: en Sources: [Harness Blog]() Topics: [AI-assisted coding](), [feature flags](), [Software Engineering](), [Code](), [releases]() Tags: [ai](), [ai-code-review](), [code-review](), [feature-flags](), [metrics](), [progressive-delivery](), [safety](), [software]() ### AI overview The article argues that human review, AI code review, staging, and QA cannot guarantee that software changes will behave safely in production. Because AI-assisted development increases the volume and uncertainty of changes, it recommends relying on feature flags, progressive delivery, and production metrics to manage releases when review is imperfect. ### Source excerpt Human and AI code review can't guarantee production safety. Learn why feature flags, progressive delivery, and metrics-driven releases are essential in the AI software era. | Blog ## Five Deployment Strategies for Safer Software Releases DevFeed: [Five Deployment Strategies for Safer Software Releases]() Original publisher: [Read original article]() Author: Saurabh Dashora Published: 2026-05-12T07:05:17Z Content type: article Language: en Sources: [System Design Codex]() Topics: [Deployment Strategies](), [Deployment](), [progressive delivery](), [App]() Tags: [blue-green-deployment](), [deployment-strategies](), [downtime](), [load-balancer](), [progressive-delivery](), [rollback]() ### AI overview This article discusses deployment strategies for reducing release risk, downtime, and user impact. It explains blue/green deployment and canary deployment, including their workflows, benefits, tradeoffs, and suitable use cases, and introduces A/B testing as part of a release process. ### Source excerpt Every developer should know these ## Using Argo Rollouts for Header-Based Routing in Kubernetes Canary Deployments DevFeed: [Using Argo Rollouts for Header-Based Routing in Kubernetes Canary Deployments]() Original publisher: [Read original article]() Author: Kostis Kapelonis Published: 2025-06-23T13:39:25Z Content type: tutorial Language: en Sources: [Codefresh]() Topics: [Kubernetes](), [Deployment](), [Routing (disambiguation)]() Tags: [argo-rollouts](), [continuous-deployment](), [deployment-strategies](), [kubernetes](), [progressive-delivery](), [routing](), [technical-guides]() ### AI overview This guide explains how to use Argo Rollouts to control which users receive a canary deployment. It compares static routing with extra URLs and header-based routing, covering the tradeoffs between simplicity and flexibility. ### Source excerpt A Kubernetes cluster with default configuration has access to only two deployment strategies: To get access to more advanced deployment strategies such as blue/green and canaries you need to use a dedicated Progressive Delivery controller such as Argo Rollouts. We have previously covered several basic and advanced scenarios for Argo Rollouts in our blog. Today [...] The post Laser Focused Kubernetes Deployments Using Argo Rollouts and Header Based Routing appeared first on Codefresh.