Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I’m at a crossroads and evaluating whether to introduce jsonnet to my org. We are doing a massive conversion of legacy yaml manifests from a proprietary vendor format, and there are not a lot of chances like this where you can make such a change at scale. Any experience reports or advice on jsonnet would be appreciated.


At Grafana Labs we're using jsonnet at scale, while being a powerful functional language it is also excellent for rendering JSON/YAML config. We have developed Tanka[0] to work with Kubernetes, for other purposes I can recommend this course[1] (authored by me).

[0] https://tanka.dev/

[1] https://jsonnet-libs.github.io/jsonnet-training-course/


Wow I love it here. Where else can you post something and get a project leader chiming in within hours?

We are at a crossroads in moving towards GitOps and a CD vendor change, and are forced into some manifest conversion. From where we are coming from Helm is the obvious choice, but I do think we can do better, especially for debugging, readability, and inheritance.

ArgoCD’s support for jsonnet turned me onto it and Tanka, and now I’m going to take it for a more serious spin. I’m early days with it but I’m curious about how life is with having a compiled language for an infra development. I had the same reluctance when thinking about making the Typescript leap, but that turned out just fine. I kinda want to jsonnet all the things if it works out well, but I worry the compilation steps would make it cumbersome for some use cases.


Hit me up on the #jsonnet channel on Kubernetes Slack or the #tanka channel on Grafana Slack if you want to go a bit more in depth.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: