The DevOps landscape in 2026 is transforming through agentic AI, platform engineering maturity, GitOps standardization, OpenTelemetry adoption, and supply chain security requirements. From AWS DevOps Agent to self-architecting systems, discover how these converging trends are reshaping software delivery.
A five-year journey from push-based pipelines to a self-service GitOps platform managing over 500 clusters, 2,000 nodes, and 100,000 containers.
Flux 2.8.0 introduces Helm v4 support, server-side apply for HelmReleases, kstatus-based health checking, faster recovery from failed deployments, and GitHub App integration for source authentication.
At FluxCon NA 2025, Morgan Stanley shared their five-year journey from push-based CI/CD to GitOps with Flux, now managing 500+ clusters, 2,000+ nodes, and 100,000+ containers with a self-service platform.
Morgan Stanley’s multi-year Flux journey shows that GitOps at enterprise scale is not just about choosing a reconciler. It is about onboarding, tenancy boundaries, source-of-truth design, and relentless tuning once the cluster count and resource count get large.
Flux 2.8 ships Helm v4 support (including server-side apply) and pushes more deployments toward kstatus-style readiness. That combination changes the operational contract of GitOps: fewer false ‘healthy’ signals, better drift visibility, and sharper rollback decisions.
Flux 2.8 goes GA with Helm v4 support, server-side apply defaults, kstatus health checks, and new features aimed directly at reducing MTTR in GitOps workflows.
Flux 2.8 lands Helm v4 support (SSA + kstatus health checks), reduces MTTR by canceling health checks when new revisions appear, and expands GitOps feedback loops with PR/MR comment providers and a new Flux Operator Web UI.
Flux 2.8 GA ships with Helm v4 support, bringing server-side apply and kstatus-based health checking to Helm releases. Here’s why that’s bigger than it sounds—and how platform teams should approach the upgrade.
