5 ms·
There was that other long thread about using a general purpose language to generate Kubernetes manifests. However, just looking at this briefly, this may have a
by hosh 2y ago
There was that other long thread about using a general purpose language to generate Kubernetes manifests. However, just looking at this briefly, this may have all the features I care about from general-purpose languages.
Although it looks like it is a better replacement for HCL (Terraform), I'm thinking this may end up working better than Helm.
- hbogert 2y agoHave you seen timoni? it ticks all my boxes. It uses cuelang which admittedly is a steeper learning curve, but o boi, its conceptual model is so nice once it 'clicks' https://timoni.sh/ https://timoni.sh/
- aliasxneo 2y agoWe've been using Timoni in production for six months now. What a breath of fresh air (and sanity) coming from Helm. It's not perfect, but I'll take immature imperfections (that are improving by the month) over the YAML/Go templating nightmare that is Helm.
- hosh 2y agoI have not. However, looking at it now, it falls into the same problems all template generators have. Those are things solved by using general purpose languages generate rather than templating manifests. KCL is in the middle ground. The Ruby mixins I can use for manifest generation can has an equivalence with KCL's union. I can see Timoni's appeal as it looks like an improvement over Helm and integrates building artifacts.
- hbogert 2y agoOh, now I'm eager to now why you think KCL is middle ground, but cuelang and timoni are not. What is inherent to KCL that is so powerful that you can not due in CUE?