Dan Guns

I chose Rust for flux9s partly because I was learning it at the time. Go probably would have been quicker to get started with, but kube-rs had the Watch API support I needed, and it seemed like a good project to learn on. In the GA post on the Flux blog, I also mentioned that Rust works well with AI-assisted development. I think a lot of that comes down to the compiler. An agent can write something that looks reasonable but uses the wrong type, calls an API that doesn’t exist in the installed version of a crate, or tries to use a value after moving it. Running cargo check gives it something specific to fix. That is useful when you’re learning the language too, since you can work through the error and understand why the first attempt didn’t compile. ...

flux9s reached 1.0, and I wrote a post for the Flux blog about why I started it and how the Flux Operator’s web UI helped shape it. Read the post on fluxcd.io.

One of the things I have been occupied with lately is figuring out how to scale GitOps past the point where managing a Git repo, or many nested manifests per cluster, becomes unworkable. The answer we landed on is Flux Operator’s ResourceSet and ResourceSetInputProvider — specifically the ExternalService input type, which I helped contribute upstream. (There was already an issue open for exactly this when I looked!) The full writeup with working examples lives at dgunzy.github.io/flux-resourceset, but here’s the short version. ...