Hi!
It seems kubenix is not maintained anymore (kubernetes 1.18 is latest supported version, but kubernetes is in 1.22 AFAICS)… is there some alternative or do I have to use old k8s?
From what I see, kubenix is a really great piece of nix tooling … been playing with it right now and it looks great!
Best,
1 Like
There was this thread earlier this year:
Can we make a joint effort to rejuvenate GitHub - xtruder/kubenix: Replaced by https://github.com/hall/kubenix ?
It seems like @offlinehacker has shifted priorities, yet this project is too valuable for connecting the nix ecosystem with the k8s ecosystem, for it not to have strong maintainership commitment.
I dare to guess, @offlinehacker would be pleased if anyone is willing to step up and take over ownership of this project, even if only temporary. Interest is temporary. Handing over reposit…
My current take has evolved and is the following:
JsonSchema or OpenAPI equivalents are ubiquitous
An extremely large portion of those are officially maintained by upstream tooling
This fits the exact same bill as kubenix / terranix. Kubenix has some extra “gruft” (“batteries”), that we might re-consider after the fact.
1 Like
opened 02:53PM - 15 Oct 21 UTC
**Is your feature request related to a problem? Please describe.**
- I have a… config management problem that might for example involve nomad job configs or kubernetes manifests.
- I want to use nix as my _single_ config management language.
- The only type system light that I have currently available is the `nixpkgs` (not `nix`!) module system.
- I have to re-implement config types manually.
- Error reporting UX of the `nixpkgs` module system is not acceptable for my "internal clients".
**Describe the solution you'd like**
- Since official json schemata are ubiquitously available either as schema or as `openapi` spec or similar
- I do `builtins.jsonSchemaValidate attrset ./path/to/schema.json` to validate my my config
- _without_ IFD
- _with_ great error provenance reporting
**Describe alternatives you've considered**
- IFD with `ajv`
- Does not solve the problem of error provenance reporting.
**Additional context**
- https://github.com/fluidattacks/makes/issues/619
---
There are a few candidate json schema validate C++ libs that I've found on https://json-schema.org/
<ul>
<li><a href="https://github.com/KayEss/json-schema">f5-json-schema</a> <em>draft-07</em> (Boost Software License 1.0)</li>
<li><a href="https://github.com/pboettch/json-schema-validator">JSON schema validator for JSON for Modern C++</a> <em>draft-07</em> (MIT)</li>
<li><a href="https://github.com/tristanpenman/valijson">Valijson</a> <em>draft-07</em> header-only library, works with many JSON parser implementations (BSD-2-Clause)</li>
<li><a href="https://github.com/danielaparker/jsoncons/blob/master/doc/ref/jsonschema/jsonschema.md">jsoncons</a> <em>draft-07</em> Header-only library(Boost Software License 1.0)</li>
</ul>
/cc @kamadorueda
If anybody has skills and interest to spare, please coordinate on that issue.
1 Like