---
author: XXX
date: YEAR-XX-01 15:30:00+00:00
title: LAST_MONTH YEAR Update
description: "XX"
url: /blog/YEAR/XX/LAST_MONTH-YEAR-update/
tags: [announcement]
resources:
- src: "**.{png,jpg}"
  title: "Image #:counter"
---

<!--

Have a look at these documents

- internal_docs/how-to-do-the-monthly-update.md
  online: https://github.com/fluxcd/website/blob/main/internal_docs/how-to-do-the-monthly-update.md
- internal_docs/how-to-write-a-blog-post.md
  online: https://github.com/fluxcd/website/blob/main/internal_docs/how-to-write-a-blog-post.md

to get more background on how to publish this blog post.

-->

As the Flux family of projects and its communities are growing, 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 our last update here (xxx).

It's the beginning of MONTH YEAR - let's recap together what
happened in LAST_MONTH - it has been a lot!

## New Releases

### Flux vx.y.z

### Flagger vx.y.z

### Security news [if available]

## Community News

### People writing/talking about Flux

We love it when you all write about Flux and share your experience,
write how-tos on integrating Flux with other pieces of software or other
things. Give us a shout-out and we will link it from this section! ✍

### New Adopters

We are very pleased to announce that the following adopters of Flux have
come forward and added themselves to our website: xxx

If you have not already done so, [use the instructions
here](/adopters/) or give us a ping and we will help to add you. Not only
is it great for us to get to know and welcome you to our community. It
also gives the team a big boost in morale to know where in the world
Flux is used everywhere.

### New Contributors (or Project Members / Project Maintainers)

## Events

It's important 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.

### Recent Events (ICYMI) 📺

We feel blessed to have such a big community of users, contributors and
integrators and so many are happy to talk about their experiences. In
LAST_MONTH here are a couple of talks we would like to highlight.

Here is a list of additional videos and topics we really enjoyed -
please let us know if we missed anything of interest and we will make
sure to mention it in the next post!

### Upcoming Events 📆

We are happy to announce that we have a number of events coming up in
MONTH- tune in to learn more about Flux and GitOps best practices,
get to know the team and join our community.

### Project Meeting & Bug Scrub

Our Flux Bug Scrubs still are happening on a weekly basis and remain one
of the best ways to get involved in Flux. They are a friendly and
welcoming way to learn more about contributing and how Flux is organised
as a project.

The next dates are going to be:

- [YEAR-xx-yy 12:00 UTC, 14:00 CEST](/#calendar)
- [YEAR-xx-yy 17:00 UTC, 19:00 CEST](/#calendar)
- [YEAR-xx-yy 12:00 UTC, 14:00 CEST](/#calendar)
- [YEAR-xx-yy 17:00 UTC, 19:00 CEST](/#calendar)

We are flexible with subjects and often go with the interests of the
group or of the presenter. If you want to come and join us in either
capacity, just show up or if you have questions, reach out to Kingdon on
Slack.

## Flux Ecosystem

<!--

If you add entries to this subsection, please don't use "we" as it gets
confusing from which perspective the whole blog post is written and who
"we" is. The whole post is meant to be from the perspective of the Flux
community. Better to write:]

- "Since the new release of X, it supports Y." or
- "Team lead X says: 'we have put a lot of effort into Y and are
   really proud of the performance results' ..." or
- "The team has been working on ..."

-->

### Weave GitOps

### Terraform-controller

### Flux Subsystem for Argo

### Azure GitOps

### VS Code GitOps Extension

### New additions to the Flux Ecosystem

## Flux Fun Facts 

<!-- Select one of the items below for this section

1. 🤝 Flux provides GitOps for both apps or
  infrastructure. Flux and [Flagger](https://github.com/fluxcd/flagger)
  deploy apps with canaries, feature flags, and A/B rollouts. Flux
  can also manage any Kubernetes resource. Infrastructure and workload
  dependency management is built-in.
1. 🤖 Just push to Git and Flux does the rest. Flux
  enables application deployment (CD) and (with the help of
  [Flagger](https://github.com/fluxcd/flagger))
  progressive delivery (PD) through automatic reconciliation. Flux
  can even push back to Git for you with automated container image
  updates to Git (image scanning and patching).
1. 🔩 Flux works with your existing tools: Flux works with your Git
   providers (GitHub, GitLab, Bitbucket, can even use s3-compatible
   buckets as a source), all major container registries, fully
   integrates [with OCI](/flux/cheatsheets/oci-artifacts) and all CI
   workflow providers.
1. 🔒 Flux is designed with security in mind: Pull vs. Push,
  least amount of privileges, adherence to Kubernetes security
  policies and tight integration with security tools and
  best-practices. Read more about our security considerations.
1. ☸️ Flux works with any Kubernetes and all common Kubernetes
  tooling: Kustomize, Helm, RBAC, and policy-driven
  validation (OPA, Kyverno, admission controllers) so it simply
  falls into place.
1. 🤹 Flux does Multi-Tenancy (and "Multi-everything"):
  Flux uses true Kubernetes RBAC via impersonation and supports
  multiple Git repositories. Multi-cluster infrastructure and apps
  work out of the box with Cluster API: Flux can use one Kubernetes
  cluster to manage apps in either the same or other clusters, spin
  up additional clusters themselves, and manage clusters including
  lifecycle and fleets.
1. ✨ Dashboards love Flux: No matter if you use one of
   [the Flux UIs](/ecosystem/#flux-uis--guis) or a hosted cloud
   offering from your cloud vendor, Flux has a thriving ecosystem
   of integrations and products built on top of it and all have
   great dashboards for you.
1. 📞 Flux alerts and notifies: Flux provides health
  assessments, alerting to external systems and external events
  handling. Just "git push", and get notified on Slack and [other
  chat systems](/flux/components/notification/provider/).
1. 👍 Users trust Flux: Flux is a CNCF Graduated project
  and was categorised as "Adopt" on the [CNCF CI/CD Tech
  Radar](https://radar.cncf.io/2020-06-continuous-delivery)
  (alongside Helm).
1. 💖 Flux has a lovely community that is very easy to work
  with! We welcome contributors of any kind. The
  components of Flux are on Kubernetes core controller-runtime, so
  anyone can contribute and its functionality can be extended very
  easily.
-->

## Over and out

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](/community/#meetings) on
  YEAR-XX-XX or YEAR-XX-XX.
- Talk to us in the #flux channel on [CNCF Slack](https://slack.cncf.io/)
- Join the [planning discussions](https://github.com/fluxcd/flux2/discussions)
- And if you are completely new to Flux, take a look at our [Get
  Started guide](/docs/get-started/) and give us feedback
- Social media: Follow [Flux on Twitter](https://twitter.com/fluxcd),
  join the discussion in the [Flux LinkedIn
  group](https://www.linkedin.com/groups/8985374/).

We are looking forward to working with you.
