Guest post originally published on Flux’s blog by Daniel Holbach

Flux v2 has its first anniversary and reaches the 0.13 milestone, Alison joins maintainers, new guides and use-cases docs, upcoming events (yes we’ll be at KubeCon!) and general community news!

Before we get started, what is GitOps?

If you are new to the community and GitOps, you might want to check out some general resources. We like “What is GitOps?” or “The Official GitOps FAQ” written by folks at Weaveworks.

The Road to Flux v2

The Flux community has set itself very ambitious goals for version 2 and as it’s a multi-month project, we strive to inform you each month about what has already landed, new possibilities which are available for integration and where you can get involved. Read last month’s update here:

Let’s recap what happened in April – there has been so much happening!

It’s the one-year anniversary of Flux v2

Incredible, but true. The first experimentation around Flux v2 started about a year ago. It was only meant to be a proof of concept to illustrate that a set of small and targeted controllers could replace all of Flux eventually. We celebrate how far we have come: Flux v2 is closer to GA, and already solves more problems than v1. It’s far more flexible, ships more features and is easier to navigate and debug. What’s even more important is that our community has grown considerably since then. We have more maintainers from more organisations on board, more documentation and are looking forward to having you on the team as well!

Thanks a lot to everyone who contributed so Flux v2 so far!

We added many long-requested features

0.12 had the following highlights:

The Flux v2 CLI and the GitOps Toolkit controllers are now CII Best Practices certified.

Checkout the new bootstrap procedure.

0.13 comes with breaking changes to image automation and has the following highlights:

Please follow the upgrade procedure for image automation.

Checkout the new bootstrap customisation feature.

The Image automation guide has been updated to the new APIs, and also includes a reference to a new GitHub Actions use case guide, for automatic pull request creation with Flux and GitHub Actions. This guide is for you, if you want Flux updates to go to a staging branch, where they can be reviewed and approved before going to production.

Flagger v1.8.0

Until now Flagger was compatible with Linkerd which implements the Service Mesh Interface (SMI) v1alpha1. Starting with v1.8.0, Flagger extends the SMI support for the v1alpha2 and v1alpha3 APIs. This means Flagger can be used to automate canary releases with progressive traffic shifting for Open Service MeshNGINX Service MeshConsul Connect, and any other service mesh conforming to SMI.

More features have been included in v1.8.0 release, please see the changelog.

If you want to get hands-on experience with GitOps (Flux v2) and Progressive Delivery (Flagger), check out Stefan’s blog post: A GitOps recipe for Progressive Delivery with Istio.

Upcoming events

It’s important to us to keep you up to date with new features and developments in Flux and provide simple ways to see our work in action and chat with our engineers. In the next days we have these events coming up for you:

It’s KubeCon EU 2021 and because we are now an incubating project Flux will have a booth at the project pavilion for the first time! Stop by the booth to chat with us and check out our booth schedule of talks with various users, contributors, and maintainers.

The Flux maintainers will be speaking during the conference as well:

Still a bit further down the line, but this will definitely be worth your time: an entire two-day conference about the newest developments in the GitOps world with Keynotes from Justin Cormack (CTO, Docker), Katie Gamanji (Ecosystem Advocate, CNCF), and Lei “Harry” Zhang (Staff Engineer at Alibaba Cloud).

Check out for more upcoming events and links to recordings of past talks.

In other news

Our website has grown

Since the start of Flux v2 we wanted to make good documentation front and center of what we do. For a while now we published all the guides and API docs at For a time now we knew that this was confusing, so we started the work on moving everything to

We are very pleased to announce that we succeeded in moving the docs and now offer community information, our blog and many other useful bits on the website, everything is searchable and we look forward to adding more.

The team who has been working on this is looking for help, so if you have a knack for fixing typos, improve grammar, add short guides or work on graphics or make the layout more user-friendly, please talk to us in the #flux Slack channel and/or send a pull request to fluxcd/website.

Looking forward to growing the team! 💖

Alison Dowdney joins the maintainer team

Alison has been part of the Flux project for quite a while now. Not only did she present Flux at meetups, fix bugs and add documentation in the last months. She also helped out with the website and has a long background in working with communities in the Kubernetes space. Recently she took on the role of chair in k8s SIG Contributor Experience as well!

Alison Dowdney

We feel very fortunate to have Alison on board!

Over and out

If you like what you read and would like to get involved, here are a few good ways to do that:

We are looking forward to working with you.