Developer documentation

Helm And Kind

MVP 10 Kubernetes packaging and local chart proof.

The Helm chart packages the core runtime so the MVP can move from Compose into Kubernetes without changing the product contracts. The important goal is continuity: the same service names, route expectations, workspace behavior, and analytics path should survive the deployment target change.

The app-local chart lives at:

deploy/helm/workspace-app

It packages the core runtime services with fixed in-cluster service names that match existing gateway, OpenResty, and worker contracts.

Chart Checks

Chart checks are the fast packaging guardrail. They confirm the Kubernetes objects render before a full runtime smoke tries to prove behavior.

helm lint deploy/helm/workspace-app
helm template workspace-app deploy/helm/workspace-app \
  -f deploy/helm/workspace-app/values-kind.yaml

Kind Smoke

The Kind smoke proves the chart as a running system, not only as YAML. It checks that a workspace can be created, public content can be written through the workspace path, OpenResty can serve it, and Matomo bootstrap state exists.

python3 dev/smoke_mvp10_helm.py

The smoke builds local images, loads them into Kind, installs the chart, creates a workspace, writes public content through the workspace pod, serves it through OpenResty, and verifies Matomo bootstrap state.

Production Direction

values-production.example.yaml shows the intended production override shape:

• real registry image references
• longhorn-workspace storage
• existing Kubernetes Secret for operational secrets
• QUANTA_DATABASE_URL sourced from a Secret for Postgres

The chart is still an MVP hardening step. Longhorn-backed local Talos/libvirt proof, backup jobs, dashboards, alerts, and security review remain separate acceptance work.