Open chocopowwwa opened 4 years ago
Totally agree!
For reference, we open source everything we need for our own infrastructure: https://github.com/grafana/jsonnet-libs. Keep in mind this might now be ready for general use, as it fits exactly our needs and has not yet been extended any further.
Beyond that, I agree the Jsonnet ecosystem is rather weak. I also once created https://github.com/sh0rez/awesome-libsonnet to track that.
I suggest for going forward, we use this jsonnet-libs/ecosystem
repository to collect the status quo, and also a roadmap of projects we need.
So, what do you think? Are you guys interested to start this project? I don't have any particular need for this at the moment, might be hard to test how the library (the name library sounds a bit awkward to me) perform in production, but I'm sure I can make it run on k8s and I'd be more than happy to contribute.
Hi, grafana/tanka is a great project, very cool. The jsonnet allows me to treat the configuration as an object, which then I can compose them with another object, very flexible, I love it. But the community adoption is slow, which makes us hesitate to use it in production. I think this is problem is due to the lack of off-the-shelf software like helm/charts did, which makes the adoption very easy and very fast.
But that project should start somewhere, usually the community starts it but no one does at this moment, I believe Grafana could improve this situation by creating a repo for the community to submit their Tanka configuration. The repo itself can be under the grafana organization or tanka-community, both are great but I believe piggybacking on Grafana's name would make the adoption much faster, but both are fine.
Initially, I think Grafana could start with something that are very common to deploy in kubernetes like nginx ingress, HAProxy, hello-world service, Redis, and obviously Grafana, Tanka, Corex and MetricTank must be included