FluxCon Atlanta Was Just the Start

When you organize an inaugural event, there’s always a nagging subtext. Will anyone actually show up?
I’ve spoken at enough events to know the drill. Sometimes the energy is there, and sometimes I’m staring at empty chairs. But the room at FluxCon Atlanta felt different. It was spectacular.
It wasn’t just that the room was packed, it was the specific energy of the people filling it.
We had core maintainers getting whoops and applause for walking on stage. We had platform engineers from massive organizations like Morgan Stanley and RBC sitting alongside hobbyists running Flux in home labs.
That mix matters. It shows that despite the tumultuous two years of changes with WeaveWorks and the uncertainty that followed, the project didn’t just survive. It hardened and accelerated.
This event was our proof of life, and the pulse is stronger and faster.
The Human Side of High Availability
It’s easy to get lost in technical abstraction, reconciliation loops, drift detection. But FluxCon reinforced that the bottom layer of the stack is a human effort.
The best part of the day wasn’t a technical demo. It was seeing the community validate the work of the maintainers.
Stefan Prodan and the highly skilled core team have put in unimaginable hours to keep this ship moving. When ControlPlane stepped up to help steward Flux, we didn’t want to take over. We wanted to ensure those maintainers had the runway to keep shipping features they’ve wanted to build for years.
Seeing them on stage, happy and shipping code, validated everything we’ve been working toward. It proved that the “vibrancy” of a project isn’t just a metric in a CNCF dashboard. It’s the relief and excitement in the room when people realize the tools they rely on are in safe hands.
From Policy to Production
During the keynote last year, I talked about moving “from policy to production,” and we’re doubling down on that.
In 2025, GitOps wasn’t just a nice-to-have deployment method, it is the blueprint for how we secure complex systems.
And the industry is shifting. We aren’t just shipping applications any more. We’re shipping fleets of clusters, complex infrastructure, and the security controls that wrap around them all.
For the banks and highly regulated industries ControlPlane works with, this precision is non-negotiable. You can’t have auditability without the strict state guarantees that Flux provides.
My view has always been that we shouldn’t prescribe a castle for everyone to live in. Some organizations already have a castle. They just need better bricks. Others need the whole fortress. Flux is successful because it serves both the platform engineer dealing with legacy integration headaches and the greenfield developer who wants to move fast.
Amsterdam: Marking 10 Years and The Next Step Up
We viewed Atlanta as the prototype: Flux was nine years old, and it deserved its own forum. Our mission was to prove that we could get the numbers, support the community, and pull off a zero-day event that felt distinct from the main KubeCon noise.
We did it. Now the ball keeps rolling.
FluxCon Amsterdam in March is the acceleration phase. Reference customers like Morgan Stanley are proving the scale. And the project has the highest backing of the CNCF.
To the sponsors and community members coming to Amsterdam, this is the time to get involved. We aren’t just stabilizing. We want to go bigger. And we will continue bridging the gap between highly regulated enterprise needs and frictionless, secure developer experience.
Atlanta was the reunion we needed. In Amsterdam we celebrate 10 years of Flux, and reveal what comes next.
Join us.
Related blogs

Flux D2 Reference Architecture – Gitless GitOps for Secure Multi-Tenancy

Ephemeral Environments for GitLab Merge Requests with Flux Operator
