Continuous Deployment Tools: Automated Release, Progressive Delivery & Feature Flags

The practice of automatically releasing every change that passes the pipeline to production, without a manual approval step.

It is safe when paired with strong automated tests, monitoring, and progressive rollout with fast rollback; feature flags separate deploying code from exposing it to users.

Releasing to a small share of traffic first (canary), or switching between two environments (blue-green), and widening the rollout as metrics stay healthy; Argo Rollouts and Flagger automate this on Kubernetes.

Not always. Many teams practise continuous delivery and keep a deliberate release decision; see the Continuous Delivery Tools page.

Links were checked in October 2026. Archived or renamed products are labelled; sites that block automated checks are kept and may need a manual click.

Helm 4.3.1 and Helm 3.22.1 were both released on 15 October 2026, after Helm 4.3.0 on 9 September. The Helm 4 announcement set Helm 3 bug fixes until 8 July 2026 and security fixes until 11 November 2026. Helm's release policy calls for patch releases normally on the second Wednesday of each month and a minor release every four months, aligned with Kubernetes. Helm 4 adds server-side apply, a redesigned plugin system that supports WebAssembly plugins, and resource waiting based on kstatus.

Kustomize is a standalone tool that customizes Kubernetes objects through a kustomization file. Since Kubernetes 1.14, kubectl also supports kustomization files: kubectl kustomize renders the resources in a directory, and kubectl apply -k applies them. On GitHub in October 2026, kustomize v5.8.3 (8 October) was the latest release; its notes say it removes dependencies and compressed blobs that caused problems when updating kustomize inside kubectl, with no functional changes.

On GitHub in October 2026 Argo CD v3.5.6 was marked latest (20 October), with v3.4.12 and v3.3.17 released the same week. Argo CD makes a minor release every three months and patches only the three most recent minor versions. The 3.4 to 3.5 upgrade notes say Helm was upgraded to 4.2.0, so Helm 4 now renders all charts and an app's helm.version v3 setting is ignored, plain-HTTP OCI registries need --insecure-oci-force-http, UI extensions must be rebuilt for React 19, and GnuPG signature verification was replaced by Source Integrity. Argo is a CNCF graduated project.

Flux v2.9.0, released on 30 June 2026, added a CLI plugin system (flux plugin), server-side apply field ignore rules for Kustomizations, Age post-quantum SOPS decryption, Helm post-render strategies with chart hooks, SSH-key commit signing and verification, AWS CodeCommit authentication through Workload Identity, and secret-less, OIDC-secured Receivers. The image.toolkit.fluxcd.io/v1beta2 and notification.toolkit.fluxcd.io/v1beta2 APIs were removed. v2.9.6 (1 October) was the latest patch release. Flux supports the last three minor releases and ships a minor version at least every four months, after each Kubernetes minor release. Flux is a CNCF graduated project.

The CD Foundation's May 2026 project update lists Spinnaker as one of its six open source projects and says the old Halyard installer is deprecated, with a native kustomize-based installation now the default. It also says Spinnaker is moving images from Google's artifact storage to GitHub Container Registry, that Spring Boot 3 support is merged and stable, that adoption of the AWS SDK v2 is ongoing, and that users should upgrade promptly to a supported release because new critical and high-severity vulnerabilities were published. On GitHub in October 2026, Spinnaker 2026.3.0 was released on 7 September, with 2026.2.4 and 2026.1.3 following on 25 September; 2026.1.3 prevents server-side request forgery through HTTP redirects in Helm and Jenkins artifact accounts.

Harness's release notes for October 2026 include ECS Blue Green deployments supporting multiple ALB listener rules and phased rollbacks for Auto Scaling Group canary deployments (19 October), a new "Passed with warning" pipeline status and looping over deployment targets in Release Orchestration (15 October), a Success Criteria setting and execution strategy selection in GitOps (13 October), Cache Intelligence for npm in Continuous Integration (9 October), OPA governance for users and groups (12 October), and Delegate 3.0 in closed beta (8 October).

Octopus Deploy 2026.3 was released on 14 September 2026. Its release notes list a deployment approval system with approval gates, runbook webhook triggers, read-only API keys, environment state that deployments and runbook runs can set and use, a waterfall view of the deployment task log, support for Helm v4 and built-in HTTP rate limiting, although the page lists no official highlights. The What's new index shows builds up to 2026.4.8310.

The section 'More Progressive Delivery Resources' lists OpenFeature, Flagger, Argo Rollouts, Unleash, Martin Fowler: Feature Toggles. Feature flags and progressive delivery references.

The Software Tools Directory page links to curated directories across AI and ML, DevOps, observability, data, security and developer tooling.

Links were rechecked in October 2026 and all outbound links on this page returned 200 to automated checks. For related directories, see DevOps, CI/CD Tools, Platform Engineering and Developer Experience on this site.