timoni

Timoni is a package manager for Kubernetes, powered by CUE and inspired by Helm.

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.

Get started

To get started with Timoni please visit the documentation website at timoni.sh.

Concepts

If you are familiar with Helm, a Timoni module is the equivalent of a chart, a Timoni bundle is the equivalent of an umbrella chart, and a Timoni instance is the equivalent of a Helm release.

Timoni Modules

A Timoni module contains a set of CUE definitions and constraints organised into a CUE module with an opinionated structure. A module accepts a set of values supplied by the user as values.cue files, and outputs a set of Kubernetes objects that Timoni deploys on Kubernetes.

Module structure:

├── cue.mod
│   ├── gen # Kubernetes types
│   └── module.cue # Module metadata
├── templates
│   ├── config.cue # Config schema and default values
│   ├── deployment.cue # Kubernetes Deployment template
│   └── service.cue # Kubernetes Service template
├── timoni.cue # Timoni entry point
└── values.cue # Timoni values placeholder

Module examples can be found at examples/podinfo and examples/redis.

Commands for working with local modules:

• timoni mod init <module-name>
• timoni mod lint <path/to/module>
• timoni build <name> <path/to/module> -n <namespace>
• timoni apply <name> <path/to/module> -f <path/to/values.cue> --dry-run --diff

Timoni modules are distributed as OCI artifacts and can be stored in container registries.

Commands for working with remote modules:

• timoni mod push <path/to/module> oci://<module-url> -v <semver>
• timoni mod pull oci://<module-url> -v <semver> -o <path/to/module>
• timoni mod list oci://<module-url>

To learn more about modules, please read the docs.

Timoni Instances

A Timoni instance represent a module instantiation on a Kubernetes cluster. A module can be installed multiple times on a cluster by giving its instances unique names per namespace.

When instantiating a module, users can supply their own values.cue that gets merged with the defaults included in the module:

values: {
	ingress: {
		enabled:   true
		className: "nginx"
		host:      "app.example.com"
	}
	autoscaling: enabled: true
	monitoring: enabled:  true
}

Commands for working with instances:

• timoni apply <name> oci://<module-url> -v <semver> -f <path/to/values.cue>
• timoni delete <name> -n <namespace>
• timoni list -n <namespace>
• timoni inspect [module|values|resources] <name> -n <namespace>
• timoni status <name> -n <namespace>

To learn more about instances, please read the docs.

Timoni Bundles

Timoni bundles offer a declarative way of managing the lifecycle of applications and their infra dependencies.

A Timoni bundle is a CUE file for defining a group of instances together with their values and module references:

bundle: {
	apiVersion: "v1alpha1"
	name: "podinfo"
	instances: {
		redis: {
			module: {
				url:     "oci://ghcr.io/stefanprodan/modules/redis"
				version: "7.0.12"
			}
			namespace: "podinfo"
			values: maxmemory: 256
		}
		podinfo: {
			module: url:     "oci://ghcr.io/stefanprodan/modules/podinfo"
			module: version: "6.3.5"
			namespace: "podinfo"
			values: caching: {
				enabled:  true
				redisURL: "tcp://redis:6379"
			}
		}
	}
}

In the bundle files you can use arithmetic operations, string interpolation and everything else that CUE std lib supports.

Commands for working with bundles:

• timoni bundle lint -f bundle.cue
• timoni bundle apply -f bundle.cue -f bundle_extras.cue --dry-run --diff
• timoni bundle delete -f bundle.cue -f bundle_extras.cue
• timoni bundle build -f bundle.cue -f bundle_extras.cue

To learn more about bundles, please see the Bundle API documentation.

Contributing

Timoni is Apache 2.0 licensed and accepts contributions via GitHub pull requests. Please see the contributing guide for more information.