Project post by Tamao Nakahara, Head of Developer Experience, Weaveworks and Flux community manager

On October 20, 6 major vendors are joining to demonstrate their backing of a major CNCF project – Flux.

Top Cloud and GitOps vendors – Microsoft, Amazon, VMware, D2iQ, Weaveworks, and Red Hat – all trust CNCF Flux to deliver GitOps to their enterprise customers.

We’ve heard how major companies such as Alibaba, State Farm, and Deutsche Telekom have shared their success using Flux. There are new adopters everyday who add themselves to the list of happy Flux users and share their love for Flux, the most recent being the U.S. Department of Defense.

Flux’s success is at another level now as the CTOs, GMs, and others will attest on October 20 of how they trust Flux to deliver GitOps to their end customers. Many of the customers of these vendors simply want GitOps to work and they may not be opinionated about what is under the hood. So it’s important for companies such as Amazon, D2iQ, Microsoft, Red Hat, VMware, and Weaveworks to use a trusted CNCF technology that will help them deliver enterprise-level quality, security, and reliability.

For practitioners and customers looking to move forward with GitOps, the event will be a showcase of enterprise offerings to make the next step easier:

  • Amazon EKS Anywhere
  • D2iQ DKP Kommander
  • Microsoft Azure Arc Kubernetes
  • VMware Tanzu Application Platform
  • Weaveworks Weave GitOps
  • Red Hat OpenShift

Brendan Burns (Kubernetes co-creator) and Ihor Dvoretskyi(CNCF Developer Advocate) will be on stage as well to celebrate this momentous event of a CNCF project that is also swiftly completing the steps toward graduation.

For long-time Flux fans, the latest technological updates are part of why they have trusted Flux for its security and reliability, and how the project helps with velocity, time and money savings, and more. Here are some recent highlights from the Flux project:  

  • API Stability: The API has been stable since June 2021 and continues to improve. Contractors at the U.S. Department of Defense recently shared how it was one of many reasons that Flux was a clear choice for them.
  • Cloud Support: The team added support for various cloud offerings, so your general tooling should just fall into place (ssh/gpg key formats, git submodules, extended SOPS support) and full support for mixed-arch clusters. Our support for vendors has included adding Flux to OpenShift OperatorHub so that users can now get GitOps with OpenShift via Flux. 
  • Improved performance: By using Server-Side Apply (available since Kubernetes 1.18) for reconciliation, we were able to improve performance (CPU, memory, network, FD usage) and reduce the number of calls to the Kubernetes API. 
  • Using CRDs and CRs together: Because of this work using Server-Side Apply, Flux can now validate and reconcile sources that contain both CRDs and CRs together. 
  • Improved reliability, drift detection, and observability: Flux can now detect and report drift more reliably between the desired state (git, s3, etc) and cluster state by leveraging Server-Side Apply. Users can now wait for all applied resources to become ready without the need to fill in the health checks list. This improves the overall observability of the reconciliation process by reporting in real-time the garbage collection and health assessment actions.
  • Working integrations: Integrations are critical for users, so fluxcd/pkg now encapsulates best practices for GitOps controllers. 
  • Compatibility: It has been our priority for Flux to work well with all the tools that you use regularly. Now our notification-controller (a component of the microservices-designed Flux project) can send alerts and notifications on almost all major protocols
  • Flagger: The list of new features has grown and it’s in the process of being rebased on top of Flux controllers.

Because of this, the Flux community continues to grow in terms of users, contributors, and maintainers. Hear from some of its greatest supporters on October 20 at