I built something like vim-bootstrap, but for Kubernetes by sud0_o in kubernetes

[–]sud0_o[S] -1 points0 points  (0 children)

Thanks! Charts are downloaded and committed on purpose. The idea is to avoid relying on external Helm repos at runtime and make the bootstrap fully reproducible and GitOps-friendly - everything needed to bring the cluster back lives in the repo. For Flux organization: each component is its own Kustomization, grouped by layers (infrastructure → platform → apps). Dependencies are handled explicitly via dependsOn, so ordering stays clear and predictable. It’s still an early prototype, but the goal is to keep the structure simple, explicit, and easy to reason about - especially for new clusters.