Services

Here is everything the cluster runs today, grouped by what it provides. Hostnames use the opi5cluster.co.uk domain. Every group has an overview page, and every service has its own page with configuration and trade-offs. The Discord bots are listed here for completeness; their configuration stays private and they document themselves under Discord Bots.

How a service repo is laid out

Most services live in their own repo and follow the same shape, so once you have read one service you can read them all. A few are different on purpose: the media stack is a single umbrella chart, PostgreSQL vendors its upstream chart, and ArgoCD itself is configuration rather than an application.

{service-name}/
├── Chart.yaml                Chart Metadata and Version
├── values.yaml               Image tag, Database Name, Log level, Resources
├── .gitlab-ci.yml            Hadolint + Multi-arch buildx (linux/amd64, linux/arm64)
├── .helmignore
│
├── app/                      Python source (baked into the image or ConfigMap-injected)
│   ├── {component}/          API or UI or Bot or Any other
│   │   └── {files}.py        e.g. Handlers, background workers
│   └── {component}/          API or UI or Bot or any other
│       └── {files}.py        e.g. Discord commands, moderation rules
├── docker/                   Image build
│   ├── Dockerfile            Base image + uv (no pip) + apk upgrade + non-root uid 1000
│   └── {service}-image.sh    Buildx multi-arch push to registry.opi5cluster.co.uk/{service}:$VERSION + :latest
│
└── templates/                Helm chart (root-level: one Rollout per release)
    ├── rollout.yaml          Argo Rollout: replicas=1, canary 25/50/100 (unused but pinned)
    ├── external-secret.yaml  ESO -> Vault (cluster secret store) for the bot token
    ├── secret-postgres.yaml  ESO -> Vault, builds DATABASE_URL postgresql://...sslmode=require
    ├── service-account.yaml  {{ .Release.Namespace }}-sa
    └── {Other Manifest Files}

Platform & Infrastructure

The plumbing. Most of these exist so everything else can exist.

GitOps & Delivery

Nothing is deployed by hand. ArgoCD reconciles every application from Git.

Observability & Dashboard

Metrics, logs, and one dashboard for everything above.

Data & Streaming

State and streams. The data layer everything else reads and writes.

AI Stack

Local inference. No cloud API keys in the request path.

Media

A full self-hosted media pipeline, pinned to a single node with local SSD storage.

Decommissioned Services

Services that have run on the cluster in the past. Kept for reference: their configuration is frozen as it last deployed.

Discord Bots

Every Blocksensus bot runs on the cluster, deployed the same way as the services above. Bots do not get configuration pages here; each bot documents itself on its own product page instead.