-
Notifications
You must be signed in to change notification settings - Fork 340
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fix script for December. Signed-off-by: Daniel Holbach <daniel@weave.works>
- Loading branch information
Daniel Holbach
committed
Jan 24, 2023
1 parent
e1b3f6e
commit ebcf3dd
Showing
3 changed files
with
346 additions
and
17 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,344 @@ | ||
--- | ||
author: dholbach | ||
date: 2023-01-24 09:30:00+00:00 | ||
title: January 2023 Update | ||
description: "XX" | ||
url: /blog/2023/02/january-2023-update/ | ||
tags: [monthly-update] | ||
resources: | ||
- src: "**.{png,jpg}" | ||
title: "Image #:counter" | ||
--- | ||
|
||
As the Flux family of projects and its communities are growing, we | ||
strive to inform you each January about what has already landed, new | ||
possibilities which are available for integration, and where you can get | ||
involved. Read our last update [here](/blog/2022/12/november-2022-update/). | ||
|
||
It's the beginning of February 2023 - let's recap together what | ||
happened in December and January - it has been a lot! | ||
|
||
## News in the Flux family | ||
|
||
### Next Flux release: more stability and performance improvements | ||
|
||
We have released Flux v0.38. Users are encouraged to upgrade for the best | ||
experience. | ||
|
||
Features and improvements | ||
|
||
- Graduation of Notification APIs to `v1beta2`, to upgrade please see | ||
[the release notes](https://github.com/fluxcd/flux2/releases/tag/v0.38.0). | ||
- Support for defining Kustomize components with `Kustomization.spec.components`. | ||
- Support for piping multi-doc YAMLs when publishing OCI artifacts with | ||
`kustomize build . | flux push artifact --path=-`. | ||
- Support for Gitea commit status updates with `Provider.spec.type` set to | ||
`gitea`. | ||
- Improve the memory usage of `helm-controller` by disabling the caching of | ||
`Secret` and `ConfigMap` resources. | ||
- Update the Helm SDK to v3.10.3 (fix for Helm CVEs). | ||
- All code references to `libgit2` were removed, and the | ||
`GitRepository.spec.gitImplementation` field is no longer being honored. | ||
|
||
Documentation | ||
|
||
The official example repository was refactored. The new version comes with | ||
the following improvements: | ||
|
||
- Make the example compatible with ARM64 Kubernetes clusters. | ||
- Add Weave GitOps Helm release to showcase the Flux UI. | ||
- Replace the ingress-nginx Bitnami chart with the official one that contains | ||
multi-arch container images. | ||
- Add cert-manager Helm release to showcase how to install CRDs and custom | ||
resources using `dependsOn`. | ||
- Add Let’s Encrypt ClusterIssuer to showcase how to patch resources in | ||
production with Flux `Kustomization`. | ||
- Add the `flux-system` overlay to showcase how to configure Flux at | ||
bootstrap time. | ||
|
||
♥ Big thanks to all the Flux contributors that helped us with this release! | ||
|
||
### Security news | ||
|
||
### Flagger 1.27.0 | ||
|
||
This release comes with support for Apache APISIX. For more details see | ||
[the tutorial](/flagger/tutorials/apisix-progressive-delivery). | ||
|
||
### 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 ..." | ||
--> | ||
|
||
#### Flux Subsystem for Argo | ||
|
||
#### Terraform-controller | ||
|
||
#### Weave GitOps | ||
|
||
- <https://github.com/weaveworks/weave-gitops/releases/tag/v0.15.0> | ||
- <https://github.com/weaveworks/weave-gitops/releases/tag/v0.14.1> | ||
- <https://github.com/weaveworks/weave-gitops/releases/tag/v0.13.0> | ||
- <https://github.com/weaveworks/weave-gitops/releases/tag/v0.12.0> | ||
|
||
#### Azure GitOps | ||
|
||
#### VS Code GitOps Extension | ||
|
||
#### New additions to the Flux Ecosystem | ||
|
||
## Recent & Upcoming 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 | ||
December and January here are a couple of talks we would like to highlight. | ||
|
||
{{< youtube JHmQlSvL0II >}} | ||
|
||
> HashiCorp User Group Luxembourg: GitOps your Terraform Configurations | ||
> | ||
> Flux Terraform Controller is a controller for Flux to reconcile Terraform | ||
> configurations in the GitOps way with the power of Flux and Terraform, | ||
> Terraform Controller allows you to GitOps-ify your infrastructure, and | ||
> your application resources, in the Kubernetes and Terraform universe. | ||
> | ||
> Flux Terraform Controller ensures what you’ve defined in your Terraform | ||
> configurations is what’s always running and available. Flux continuously | ||
> looks for changes and reconciles with the desired state. Take advantage | ||
> of all the benefits of GitOps: streamlined and secure deployments, quicker | ||
> time to market, and more time to concentrate on app development! | ||
{{< youtube uRiCRTSkPOQ >}} | ||
|
||
> Flux’s Security & Scalability with OCI & Helm (Part 2) with Kingdon Barrett | ||
> | ||
> With Flux, you can distribute and reconcile Kubernetes configuration packaged | ||
> as OCI artifacts. Instead of connecting Flux to a Git repository where the | ||
> application desired state is defined, you can connect Flux to a container | ||
> registry where you’ll push the application deploy manifests, right next to | ||
> the application container images. | ||
> | ||
> During this session Kingdon Barrett, OSS Engineer at Weaveworks & Flux | ||
> Maintainer, shows you how to quickly create scalable and Cosign-verified GitOps | ||
> configurations with Flux using the same process with two demo environments: one | ||
> will be a Kustomize Environment and the other a Helm-based environment. | ||
{{< youtube Bmh7kKYLIhY >}} | ||
|
||
> Flux Security & Scalability using VS Code GitOps Extension | ||
> | ||
> Recently Flux has released two new features (OCI and Cosign) for scalable and | ||
> secure GitOps. Juozas Gaigalas, a Developer Experience Engineer at Weaveworks, | ||
> will demonstrate how developers and platform engineers can quickly create | ||
> scalable and Cosign-verified GitOps configurations using VS Code GitOps Tools | ||
> extension. New and experienced Flux users can learn about Flux’s OCI and Cosign | ||
> support through this demo. Join us! | ||
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 | ||
February - tune in to learn more about Flux and GitOps best practices, | ||
get to know the team and join our community. | ||
|
||
### Flux 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: | ||
|
||
- [2023-02-02 18:00 UTC, 19:00 CET](/#calendar) | ||
- [2023-02-08 13:00 UTC, 14:00 CET](/#calendar) | ||
- [2023-02-16 18:00 UTC, 19:00 CET](/#calendar) | ||
- [2023-02-22 13:00 UTC, 14:00 CET](/#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. | ||
|
||
We really enjoyed this [demo of the k3d git | ||
server](https://www.youtube.com/watch?v=hNt3v0kk6ec) | ||
recently. It's a local Git server that runs outside of Kubernetes, to | ||
support offline dev in a realistic but also simple way that does not | ||
depend on GitHub or other hosted services. | ||
|
||
## In other news | ||
|
||
### Conference Call For Papers | ||
|
||
Conferences are all about the people. It's also more fun to present | ||
together. You get to share collective experience and be more entertaining | ||
as a duo! | ||
|
||
Two upcoming call for paper deadlines are the following | ||
|
||
- CFP until 2023-02-05, [SustainabilityCon](https://events.linuxfoundation.org/cdcon-gitopscon/program/cfp/) | ||
> May 10 – 12, 2023 | Vancouver, Canada | ||
> Join the community of developers, technologists, sustainability leaders | ||
> and anyone working on technological solutions to decarbonize the global | ||
> economy, mitigate and address the impacts of climate change, and build a | ||
> more sustainable future. SustainabilityCon provides a forum to drive open | ||
> source innovation in energy efficiency and interoperability and clean | ||
> development practices within industries ranging from manufacturing to | ||
> agriculture and beyond through collaboration and learning within the community. | ||
- CFP until 2023-02-10, [GitOpsCon](https://events.linuxfoundation.org/cdcon-gitopscon/program/cfp/) | ||
> May 8 – 9, 2023 | Vancouver, Canada | ||
> | ||
> cdCon + GitOpsCon is designed to foster collaboration, discussion, and | ||
> knowledge sharing by bringing two communities together. It’s the best | ||
> place for vendors and end users to collaborate in shaping the future of | ||
> GitOps and Continuous Delivery (CD). | ||
### Soulé Ba joins Flux Core Maintainers | ||
|
||
Soulé Ba has been working on Flux for a long while. Already a maintainer | ||
of Flux's `go-git-providers`, he didn't stop there but was involved in | ||
a lot of the RFC planning process of many features and contributed code and | ||
fixes for a long long time. | ||
|
||
The Flux community is grateful to have you. Well deserved becoming a | ||
[https://github.com/fluxcd/community/pull/271](Core maintainer now), Soulé! | ||
|
||
### Your Community Team | ||
|
||
### 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! ✍ | ||
|
||
- <https://containerjournal.com/features/introduction-to-flux/> | ||
- ... | ||
|
||
### News from the Website and our Docs | ||
|
||
#### Flux Adopters shout-out | ||
|
||
We are very pleased to announce that the following adopters of Flux have | ||
come forward and added themselves to our website: | ||
[DoneOps](https://www.doneops.com/) and [Riley](https://riley.ai/). | ||
|
||
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. | ||
|
||
#### More docs and website news | ||
|
||
We are constantly improving our documentation and website - here are a | ||
couple of small things we landed recently: | ||
|
||
- The [Flux landing page](/) is shorter and less overwhelming now. | ||
This was achieved by moving the adopters logos into a horizontal | ||
scroll band, dropping some old content and there will be more to | ||
come here. | ||
- Flagger docs were update to the latest. | ||
- Flux Bootstrap: cheatsheet for how to [Persistent storage for Flux | ||
internal artifacts](/flux/cheatsheets/bootstrap/#persistent-storage-for-flux-internal-artifacts) | ||
- [Our FAQ](/flux/faq/) now has entries about how to safely rename a | ||
Flux Kustomization and how to set local overrides to a Helm chart. | ||
- [Flux GCP docs](/flux/use-cases/gcp-source-repository/) were updated. | ||
- We improved the [Flux Support page](/support) to be even clearer | ||
about how to get Support for Flux, no matter if it's professionally | ||
or for community support. | ||
- We dropped a lot of unnecessary website build code; now a lot of the | ||
dynamic content is generated straight from YAML through Hugo Data | ||
Templates. This makes the website build process a lot more stable | ||
and we have less build scripts to maintain! | ||
- Update to latest hugo plus docsy and gallery themes. | ||
|
||
Thanks a lot to these folks who contributed to docs and website: Stefan | ||
Prodan, Arhell, Aurel Canciu, Hidde Beydals, h20220026, Paulo Gomes, | ||
Sanskar Jaiswal, Stacey Potter, Johannes Wienke, Jonathan Meyers, Lassi | ||
Pölönen, Nate, Scott Rigby, Sunny, Tarunbot, h20220025. | ||
|
||
## Flux Project Facts | ||
|
||
We are very proud of what we have put together. We want to reiterate | ||
some Flux facts - they are sort of our mission statement with Flux. | ||
|
||
1. 🤝 Flux provides GitOps for both apps or | ||
infrastructure. Flux and 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) | ||
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, 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. 📞 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](https://github.com/fluxcd/notification-controller/blob/main/docs/spec/v1beta1/provider.md). | ||
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 | ||
2023-02-09 or 2023-02-15. | ||
- 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. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters