Cozystack Internals and Developer Guide

Mon, 01 Jan 0001 00:00:00 +0000

How it works

Cozystack is an operator-driven platform. The bootstrap and ongoing management are handled by a set of controllers that run inside the cluster. The high-level flow is:

Installer chart (packages/core/installer) is applied via helm install. It deploys the cozystack-operator Deployment into the cozy-system namespace.
cozystack-operator starts and performs one-time bootstrap:
- Installs Cozystack CRDs (Package, PackageSource) from embedded manifests (internal/crdinstall).
- Installs Flux components (source-controller, helm-controller, source-watcher) from embedded manifests (internal/fluxinstall).
- Creates the initial OCIRepository (cozystack-platform) from the platformSourceUrl and platformSourceRef values configured in the installer.
- Creates a PackageSource that references the initial OCIRepository.
Reconciliation loop takes over. The operator watches PackageSource and Package CRDs and translates them into Flux HelmRelease objects. Flux then installs and manages the actual Helm charts.

Cozystack Roadmap

Mon, 01 Jan 0001 00:00:00 +0000

You can view our roadmap on GitHub Project.

If you have some questions and comments about roadmap or need specific functionality, feel free to let us know.

Join our community meetings.

Cozystack v1 Documentation on Cozystack

Cozystack Internals and Developer Guide

How it works

Cozystack Roadmap