The Timoni project strives to improve the UX of authoring Kubernetes configs. Instead of mingling Go templates with YAML like Helm, or layering YAML on top of each-other like Kustomize, Timoni relies on cuelang's type safety, code generation and data validation features to offer a better experience of creating, packaging and delivering apps to Kubernetes.
Note that Timoni in under active development and is still in its infancy. The APIs and command-line interface may change in a backwards incompatible manner.
To get started with Timoni please visit the documentation website at timoni.sh.
- Module - App definition containing Kubernetes CUE templates and configuration schema, distributed as OCI artifacts.
- Instance - App instantiation referencing the module and workloads deployed on a Kubernetes cluster.
- Bundle - App composition bundling multiple modules and configurations into a deployable unit.
- OCI Artifact - Packaging format used for distributing modules and bundles to container registries.
App Packaging and Distribution
Timoni enables software vendors to define complex application deployments, packaged as Modules, using type-safe Kubernetes templates and rich customisation options for end-users.
The app configuration packaged in a Module is distributed as an Open Container Initiative (OCI) artifact, next to the app images, in a container registry. Timoni Modules are semantically versioned and cryptographically signed.
With Timoni, platform engineers can manage the lifecycle of Kubernetes controllers, including the upgrade of CRDs. Module authors can import CRD schemas from YAML files and incorporate Kubernetes custom resources in their app deployments.
App Lifecycle Management
With Timoni, users can manage the whole lifecycle of applications deployed on Kubernetes. From highly customised installation to seamless upgrades, end-to-end testing, safe rollback and uninstallation.
With Timoni, users can bundle microservices and distributed monoliths into a deployable unit. The Timoni Bundle offers a declarative way of managing the app delivery across clusters, where secrets and other environment-specific config values are dynamically loaded during installation or upgrades.