the0 Kubernetes Chart Is Now on Artifact Hub

The the0 Helm chart is now published through the public Helm repository and listed for discovery on Artifact Hub.

That sounds like a small packaging update, but it matters for anyone trying to understand whether the0 can be run seriously on Kubernetes.

What Changed

The chart release is the0-0.9.1, targeting app version 1.14.0.

The release added:

• Artifact Hub package metadata and repository ownership configuration.
• Chart annotations for links, images, and release changes.
• Artifact Hub badges in the repository and chart README.
• Clearer Kubernetes install documentation.
• A minikube walkthrough tested with PostgreSQL, MongoDB, NATS, and MinIO running inside the cluster.

The release PR is alexanderwanyoike/the0#293.

Installing the Chart

The repository can be added with Helm:

helm repo add the0 https://alexanderwanyoike.github.io/the0
helm repo update

From there, the important thing is not the command. It is the values file.

For production, the0 needs:

• PostgreSQL for application data.
• MongoDB for runtime desired state.
• S3-compatible object storage for bot packages, logs, and backtests.
• JWT signing configuration.
• A deployment-managed root admin email.
• A root admin password provided through a Kubernetes Secret.

NATS can run in the cluster from the chart, or you can point the deployment at an external NATS service.

That means a realistic production install looks more like this:

kubectl create namespace the0 --dry-run=client -o yaml | kubectl apply -f -
helm upgrade --install the0 the0/the0 --namespace the0 -f production-values.yaml

production-values.yaml should contain the application configuration and references to Secrets. It should not contain plaintext passwords.

Why Not a One-Liner?

Kubernetes makes it easy to write a one-line install command that looks good in a README.

For the0, that would be misleading.

the0 runs user-provided bots. It stores bot packages and logs. It needs databases, object storage, runtime coordination, auth configuration, and a known root admin. A one-liner that hides those details would make the first five minutes nicer and the next five hours worse.

So the Kubernetes guide now separates two paths:

• Minikube for learning the deployment locally, with all backing services inside the cluster.
• Production for real clusters, where operators provide PostgreSQL, MongoDB, S3-compatible object storage, Secrets, and a values file.

That is less magical, but it is the right shape for self-hosted infrastructure.

Start Here

Use the Kubernetes deployment guide:

docs.the0.app/deployment/kubernetes

The guide includes:

• A minikube quick start using direct minikube, docker, kubectl, and helm commands.
• A production values example.
• Secret-backed root admin configuration.
• External backing service configuration.
• Basic management and troubleshooting commands.