Kubeneko
kubeneko is a POC reactive Kubernetes framework using signals, built around CUE and Go. It aims to provide a more declarative, type-safe way to define and manage Kubernetes resources via schemas and signals.
I started designing this during the development of DeployCat when I noticed that existing tools like Crossplane are reaching their limits as they were built for simple Cloud automations, but not for building comprehensive plattforms. I needed something more flexible, pluggable and extendable but also fault tolerant without the overhead of having a microservice for every cloud automation/function. I like calling this the "Glue Code Operator" or "IaCaaS".
In fact you could implement some basic Operators with this, as long as the output is representable in kubeapi ressources. Everything that is managed is in the etcd state - by design nothing outside can be managed to follow a functional pattern. You need external Operators to implement external state.
What is this
This is an early-stage proof of concept.
The go-cue branch combines Go and CUE to validate and generate Kubernetes manifests based on schema constraints, making manifest definitions safer and less error-prone.
The idea: define resource shape and constraints with CUE, then leverage code generation / validation in Go for rendering or verifying Kubernetes YAML / manifest files.
Using CUE for Kubernetes manifests is a known pattern: the CUE ecosystem offers Kubernetes schema support for types and CRDs, enabling validation and structured config generation.
Why CUE + Kubernetes
CUE is a data-constraint language that works well with structured configuration instead of free-form YAML.
With this setup you can define strong typing / validation for Kubernetes manifests. This reduces runtime errors compared to plain YAML.
Good foundation for building a reactive framework around Kubernetes, where "signals" or config changes generate or reconcile resources automatically.
Status & What’s Missing
This is not production-ready — it’s a POC / early prototype.
No published releases or package distributions yet.
Limited documentation and usage examples so far.