This article is more than one year old. Older articles may contain outdated content. Check that the information in the page has not become incorrect since its publication.
March 2021 Update
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 the GitOps manifesto 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: February 2021 Update.
Let’s recap what happened in February - there have been many changes.
Feature Parity - what is this?
If you have been following Slack and other resources you will have heard that in the past Flux v2 releases we reached the “feature parity” milestone, but what does that mean?
When we embarked on this journey to rewrite Flux from scratch, we set out three big blocks of work:
- support for Flux operations in read-only mode
- Helm v3 support
- Image update functionality
Once all of this was realised in Flux v2, we would have feature parity between v1 and v2. After around 10 months of development, we have achieved this.
So what’s left to do? This does not mean Flux v2 is GA just yet. We are in the process of finalising all APIs, updating our documentation and generally consolidating everything. You can find more details on our roadmap.
This means that we will spend some more time on stabilisation and we need your help testing. Flux v2 is only a couple of weeks away and it will be helpful to start your migration journey early. Refer to this discussion and our upcoming workshop.
Flux v2 is now up at 0.9
Last month saw two big releases of Flux v2.
0.8 included these highlights:
- Support for Helm post-renderer and Kustomize patches (
- Self-signed certs support for Git over HTTPS (
- In-line Kustomize Strategic Merge and JSON 6902 patches (
- Basic templating with bash-style variable substitutions (
- Prevent objects like volumes from being garbage collected with labels (
- Filter events from alerting based on regular expressions (
- Support numerical ordering in image policies (
- Support for Azure DevOps and other Git v2 providers (
- Install Flux on tainted Kubernetes nodes and other bootstrap improvements (CLI)
- Uninstall Flux by handling finalizers and preserving all the deployed workloads (CLI)
Hot on its heels 0.9 was released and included these new features:
- flux is now available for Apple Silicon (CLI)
- The manifests are embedded in the flux binary allowing air-gapped installations (CLI)
- Support for recreating Kubernetes objects (e.g. Jobs) when immutable fields are changed in Git (
- Fix alert regex filtering (
- Improved status reporting for Git push errors (
💥 This version comes with breaking changes to Helm users due to upstream changes in Helm v3.5.2. Charts not versioned using strict semver can no longer be deployed using Flux due to this. When using charts from Git, make sure that the version field is set to a valid semver in Chart.yaml.
🚀 The migration guides from Flux v1 to v2 can be found here https://github.com/fluxcd/flux2/discussions/413.
Thanks a lot to everyone who contributed to these releases! 💖
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:
8 Mar 2021 - Migrating from Flux v1 to Flux v2 with Leigh Capili
Welcome to a GitOps Days Community Special!
Get ahead of the game and migrate to Flux v2! With Flux v1 in maintenance mode we want to ensure you're ready for the transition to Flux v2.
In this session, Leigh Capili, DX Engineer at Weaveworks, will demo the Flux guide on how to Migrate from Flux v1, including bootstrapping a cluster with Flux 1 and how to move it over to Flux v2.
If we don't get to everything in this session, we will have subsequent sessions to cover this topic again. Join us we'll see how far we get!
📍 Flux v2 Guide Migrate from Flux v1
Check out our calendar section for more upcoming and links to recordings of past talks.
In other news
CNCF: Flux is still in the process of getting promoted to Incubation status within the CNCF. This always takes a while. So far we cleared Due Diligence during which our production users were interviewed, and the two-week public comment period went successfully as well.
Website: The Flux Community team has put some more love into our
https://fluxcd.io/, if you would like to join the team, have
ideas on how to make it better or would like to join the Comms team,
please reach out to
@staceypotter on Slack.
Flagger: The discussions around having a new logo for Flagger have concluded; below is the winner. Thanks a lot Bianca Cheng Costanzo for working on this! Thanks also everyone else for updating the diagrams, website and CNCF Landscape.
Meeting times: the Flux team holds weekly, public meetings. To make these accessible to everyone we offer an “early” and a “late” meeting to make sure everyone can attend. Due to changes in the team we approved the request to move the times a little, so we are currently following this schedule:
- "early" meeting: Uneven weeks: Wed, 10:00 UTC
- "late" meeting: Even weeks: Thu, 15:00 UTC
Find all the information about meetings here.
If you like what you read and would like to get involved, here are a few good ways to do that:
- Join our upcoming dev meetings on March, 3rd 12:00 UTC, or March 11th, 15:00 UTC
- Talk to us in the
#fluxchannel on CNCF Slack
- Join the planning discussions
- And if you are completely new to Flux v2, take a look at our Get Started guide and give us feedback
- Social media: Follow Flux on Twitter, join the discussion in the Flux LinkedIn group.
We are looking forward to working with you.