6 ms·

I was looking at Helm the other day for merging common base values with per-cluster specific overrides but this looks like a simpler solution and integrated int

• dilyevsky 7y ago
  Which part of helm (I’m assuming v2) is integrated into kubectl? It has its own client and installs its own server component (tiller) which is difficult to secure.
  • dlor 7y ago
    I think the op is saying that kustomize is integrated into kubectl, not helm.
• skboosh 7y ago
  That's one problem sugarkube[1] aims to solve. But it goes further and allows you to spin up k8s clusters from scratch and install all your stuff onto them. It can bootstrap an AWS account first (e.g. to create S3 buckets for kops/terraform), handles templating files, and gives you a hierarchical configuration. It's still under development but should be very flexible once it's at MVP in a month or so. The aim of all this is to allow you to avoid tricky in-place cluster upgrades and to just spin up a new cluster, direct traffic to it and tear down the old one. An extra benefit is that it would allow you to give each dev their own k8s cluster in parity with your live envs, but they could select only a subset of charts. Check out the sample project[2] for more of an idea about how to use it (but the actual sample is probably broken since it's under heavy development at the moment). [1] https://github.com/sugarkube/sugarkube/ https://github.com/sugarkube/sugarkube/ [2] https://github.com/sugarkube/sample-project/ https://github.com/sugarkube/sample-project/