3 ms·
I was a big believer in Helm for generating Kubernetes resources until I looked up and saw that we had created an impossible-to-validate, impossible-to-reason-a
by btmiller 3y ago
I was a big believer in Helm for generating Kubernetes resources until I looked up and saw that we had created an impossible-to-validate, impossible-to-reason-about DSL in our values.yaml and that's when I realized we were at the end of our rope with Helm. We switched to Pkl for our Kubernetes resource generation -- it's delightful to maintain and reason about our deployments before execution time :)
- e12e 3y agoCurious if you have experience with terraform/open tofu/hcl for k8s?
- wktmeow 3y agoThis is the use case I am most interested in as well, templating strings into yaml always felt super clunky to me.
- jowf8fa9sdf 3y agoAfter spending 5,000+ hours in helm charts, I still hate helm. I've looked at cdk8s but I hate the tsconfig culture, why can't it be simple like Go?
- shepherdjerred 3y agoTry Deno with CDK8s! It's such a fantastic experience. Here's a repo for my home server: https://github.com/shepherdjerred/servers/tree/main/cdk8s https://github.com/shepherdjerred/servers/tree/main/cdk8s