Platform internals

This section is for platform admins and platform developers — how the platform is built, configured and operated. If you deploy applications on the platform, the Docs section is for you; nothing here is required reading.

The organizing rule between the two sections: developer pages teach one task in the reader's terms; the moment a page explains how the platform provides something, it belongs here.

The platform in one page

The platform is two git repositories, and every change to it is a merge:

• The infrastructure repository (binero-clusters) — OpenTofu + Talos. Declares the clusters themselves: networks, machines, Kubernetes bootstrap, buckets, load balancers. Applied per cluster with tofu apply.
• The platform repository (binero-platform) — everything running on the clusters, as rendered manifests. apps/<name>/ holds each system component (pinned upstream chart + values + local config chart
  • network policies); clusters/<name>/cluster.yaml declares each cluster's facts and which apps it runs; render.sh renders all of it into rendered/<cluster>/ — the exact manifests, reviewable in every merge request.

On the cluster, ArgoCD syncs rendered/<cluster>/ — an app-of-apps generated from the registry in root/chart/values.yaml. What is in git is what runs; there is no other deployment path.

apps/ + clusters/<name>/cluster.yaml
        │  render.sh
        ▼
rendered/<cluster>/        ← reviewed in the MR, byte-exact
        │  ArgoCD sync
        ▼
   the cluster

Sections

• Architecture — the repositories, the render pipeline, cluster anatomy.
• Platform apps — the playbook for building and changing a platform component.
• Runbooks — operational procedures.
• Decisions — the design decision log.