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.
