We've got a lot going on across the project, and we've got to make sure people know about it! haha
We're thinking 6 blog posts
Plan:
Blog Concepts:
Flux 2.9 release
we need our traditional post to cover everything in the release.
we can have a subnote pointing people to use flux-mirror for their HelmChart workflows, since HelmRepo/HelmChart are showing their age, and flux-mirror can act as both an OCI and HTTP chart supply chain diode -- note can say "blog post to come!".
Notably, we have some big features that won't be getting posts immediately:
- SSH Key Verification for Git
- managedFields Ignore Rules
- Private Sigstore Stack
- Solidified Helm 4 Support
- more
Flux 10 Year Anniversary!
Our beloved project is turning 10. This is a massive symbol of everything all of maintainers, contributors, end-users, and community members have poured into the project over the years and we should look back on it fondly, knowing we have ,unquestionably, another decade in front of us.
Flux Mirror
Flux mirror primary use-case is something everyone needs:
- unix'y tool that does one thing well which is to move the bits of your OCI images, Helm Charts, Desired State, and any other OCI artifacts such as kyverno policies or machine images (bootc) into your OCI registry of choice
- We can mention that it's a great replacement for chartsyncer for those who are worried about the license change
- We should highlight that it's a supply chain focused tool built on top of one of the most trustworthy infra supply chains in OSS
- SLSA build provenance and all that
These are using the new Plugin system :)
Flux Schema
Another really solid tool shipped as a plugin that fits into your GitOps workflows --
flux-schema solves a common gap in people's setups where you need to pre-validate the resulting YAML from your kustomization builds across all of your git repos, often offline on your laptop or in CI, and without direct access to your cluster controlplanes. A GitOps repo may use API's from many different kube clusters that may even be in an air-gapped network. Flux Schema provides a secure, OCI first way of solving this issue. The same supply-chain trust story applies.
OpenBao Integrations
Flux <3 workload identity, and we've added controller-level and object-level SA support for authenticating to an OpenBao instance!
We're also now making sure that our e2e tests are covering both OpenBao and Vault.
Flux always aims to be extensible and secure, and when it comes to pulling secrets into your workflow, whether it's ahead of time, or at runtime, we've got you covered.
New Receiver Workflows
flux trigger receiver
new Receiver type: "generic-oidc" (previously only generic and generic-hmac)
Secure Secretless reactivity for your gitops workflows (git, oci, buckets, artifact-gen)
nice symmetry with project values: fast extensible secure
We've got a lot going on across the project, and we've got to make sure people know about it! haha
We're thinking 6 blog posts
Plan:
Blog Concepts:
Flux 2.9 release
we need our traditional post to cover everything in the release.
we can have a subnote pointing people to use flux-mirror for their HelmChart workflows, since HelmRepo/HelmChart are showing their age, and flux-mirror can act as both an OCI and HTTP chart supply chain diode -- note can say "blog post to come!".
Notably, we have some big features that won't be getting posts immediately:
Flux 10 Year Anniversary!
Our beloved project is turning 10. This is a massive symbol of everything all of maintainers, contributors, end-users, and community members have poured into the project over the years and we should look back on it fondly, knowing we have ,unquestionably, another decade in front of us.
Flux Mirror
Flux mirror primary use-case is something everyone needs:
These are using the new Plugin system :)
Flux Schema
Another really solid tool shipped as a plugin that fits into your GitOps workflows --
flux-schema solves a common gap in people's setups where you need to pre-validate the resulting YAML from your kustomization builds across all of your git repos, often offline on your laptop or in CI, and without direct access to your cluster controlplanes. A GitOps repo may use API's from many different kube clusters that may even be in an air-gapped network. Flux Schema provides a secure, OCI first way of solving this issue. The same supply-chain trust story applies.
OpenBao Integrations
Flux <3 workload identity, and we've added controller-level and object-level SA support for authenticating to an OpenBao instance!
We're also now making sure that our e2e tests are covering both OpenBao and Vault.
Flux always aims to be extensible and secure, and when it comes to pulling secrets into your workflow, whether it's ahead of time, or at runtime, we've got you covered.
New Receiver Workflows
flux trigger receivernew Receiver type: "generic-oidc" (previously only generic and generic-hmac)
Secure Secretless reactivity for your gitops workflows (git, oci, buckets, artifact-gen)
nice symmetry with project values: fast extensible secure