flux2

kustomize is the less yolo version of helm: https://kubectl.docs.kubernetes.io/guides/introduction/kusto... It takes some "waaaaa?!" to change the mental model away from text generation and substitution, and I'll be straight that their docs could really use a LOT more CONCRETE examples, but in the end it does as advertised using only kubectl Then, to address the stateful bit of helm (e.g. helm ls) if one is already kustomize friendly then flux is good about using CRDs to track what things have been deployed: https://github.com/fluxcd/flux2#readme (Apache 2)

So far it seems fine, and the maintainers seem to be doing OK too. Is the project future at risk? https://github.com/fluxcd/flux2/discussions/4544

Your GitHub action can trigger a helm chart, or series thereof, or other infra tools. Declarative specifications, triggered procedurally with the context of the branch’s latest build. We use this pattern quite extensively for preview app workflows. As of a year ago this is possible in a fully declarative way with Flux 2, but there’s a lot more moving parts and security footguns - and the idea that the maintenance of this project has lost one of its primary sponsors is worrying at best. https://github.com/fluxcd/flux2/discussions/831 https://blog.kluctl.io/introducing-the-template-controller-a...

Flux has a pinned discussion for nearly a month now, to be as upfront as possible, without being able to disclose anything that might be privileged information, but anticipating that the news would get out about our backer sooner or later (aiming to avoid 100 threads about the same topic) https://github.com/fluxcd/flux2/discussions/ tl;dr: Flux is a graduated CNCF project and not going anywhere

Right. Flux was a handy little tool[1] that sync'd yaml manifests in git repos to live clusters. The concept was fascinating, and the tool was well done--small and efficient. Easy to learn. In 2019, they announced they'd be "merging" with argocd[2]. It seems the merge never really took place, and after that they deprecated flux and announced flux2[3]. The sudden changes of course were a little confusing and perhaps not too well communicated. 1: https://github.com/fluxcd/flux 2: https://discuss.kubernetes.io/t/flux-cd-joins-forces-with-ar... 3: https://github.com/fluxcd/flux2

Oh wow! This actually might be a good approach to an unrelated problem I've been having recently. Flux and its successor flux2 are really great tools everyone working with kubernetes should check out! https://github.com/fluxcd/flux2

Ironically I lately had a payment service provider handing me newly generated ecdsa ssh keys where ed25519 should be supported to the best of my knowledge. And fluxcd moved from rsa to ecdsa by https://github.com/fluxcd/flux2/releases/tag/v0.21.0. Kinda strange people are moving on to EC cipher - which is good, but to the cipher which has the NIST/NSA smell.