Jsonnet
Fewer than 5 people recommend it so far, so there's no written verdict. Here is what commenters said.
3recommend
1warn against
Nov 26, 2025first mention
Oct 17, 2026latest mention
Why people recommend it
“I use exclusively jsonnet (through kubecfg) when I can.”
“In the end we used jsonnet which turned out to be a safe choice”
Show 1 more
“JSON.Net was around by that point and was/is excellent”
Caveats and dissent
“And it's not this unusable mess that ksonnet or jsonnet is.”
Threads where it came up
- A skeptic's first contact with Kubernetes (2024) 1 mention
- Show HN: CEL by Example 1 mention
- Building Robust Helm Charts 1 mention
- Cue Does It All, but Can It Literate? 1 mention
- Reinventing how .NET builds and ships (again) 1 mention
Also written as Json.NET, jsonnet. Data: jsonnet.json. Quotes are verbatim; the verdict and theme labels are written by a model from these comments, and every clause links to its sources.
All comments 5
“I use exclusively jsonnet (through kubecfg) when I can.”
That's an anti pattern, at least the way we use it. If you need to add complexity, you define custom functions. If that's not enough, CEL probably isn't the right choice, and you'd be doing yourself no favors banging it into that square hole.
“And it's not this unusable mess that ksonnet or jsonnet is.”
“In the end we used jsonnet which turned out to be a safe choice”
“JSON.Net was around by that point and was/is excellent”