I use kubenix at work every day. I manage two Kubernetes clusters with it, and will soon manage two more. The design patterns I use are entirely improvised; property tests, vendored charts, secrets scanning on generated output via nix/git hooks, oauth2-proxy helpers for apps that don't bring their own, GitOps secret management, and all the typical cloud native / non-kubenix stuff like what components go into a service mesh. And my infinite backlog is still super interesting; I still don't vendor and CVE-scan all images, I don't vulnix my cluster's toolchain, my Keycloak realm is only fully declarative in one cluster (looking to try Zitadel for better multi-tenancy).
Using Nix to manage your Kubernetes feels like cheating because there's so much knowledge transfer and synergy from my existing Nix workflows. Having Nix as the glue rather than "super Helm charts", having natural multi-repo support, having all of nixpkgs available at any point, is OP. Kubenix also assume you've already paid 500 hours to the Nix gods.
My goal for co-maintaining kubenix (as it is for terranix) is to expand the documentation to make it truly accessible. My work as a contributor so far has, however, only involved making small tooling improvements. I've been holding back on rapidly expanding docs/ because I don't know exactly what to put in it yet.
Instead of taking a guess, I think having office hours would be a cool way to knowledge share among veteran users (I'm still just an intermediate user with a lot of ideas), and a place for newcomers to get a head start.
I propose to start with a monthly evening session (I live in UTC+1).
The goal for me is to knowledge share with the purpose of documenting.
But bring your own goal.
I use kubenix at work every day. I manage two Kubernetes clusters with it, and will soon manage two more. The design patterns I use are entirely improvised; property tests, vendored charts, secrets scanning on generated output via nix/git hooks, oauth2-proxy helpers for apps that don't bring their own, GitOps secret management, and all the typical cloud native / non-kubenix stuff like what components go into a service mesh. And my infinite backlog is still super interesting; I still don't vendor and CVE-scan all images, I don't vulnix my cluster's toolchain, my Keycloak realm is only fully declarative in one cluster (looking to try Zitadel for better multi-tenancy).
Using Nix to manage your Kubernetes feels like cheating because there's so much knowledge transfer and synergy from my existing Nix workflows. Having Nix as the glue rather than "super Helm charts", having natural multi-repo support, having all of nixpkgs available at any point, is OP. Kubenix also assume you've already paid 500 hours to the Nix gods.
My goal for co-maintaining kubenix (as it is for terranix) is to expand the documentation to make it truly accessible. My work as a contributor so far has, however, only involved making small tooling improvements. I've been holding back on rapidly expanding docs/ because I don't know exactly what to put in it yet.
Instead of taking a guess, I think having office hours would be a cool way to knowledge share among veteran users (I'm still just an intermediate user with a lot of ideas), and a place for newcomers to get a head start.
I propose to start with a monthly evening session (I live in UTC+1).
The goal for me is to knowledge share with the purpose of documenting.
But bring your own goal.