Platform Architecture

platform-architecture Doc

architecture pal-e-platform mermaid

Project

Platform Architecture

The pal-e platform runs on a single archbox k3s cluster with Tailscale networking. Everything is self-hosted.

Three Pillars

pal-e-platform — k3s foundation, Tailscale, monitoring, self-hosting infrastructure. Done.
pal-e-services — ArgoCD, service onboarding, namespace management. Nearly done.
pal-e-docs — Queryable knowledge mechanism for agents. In progress.

Infrastructure

Compute: Single archbox running k3s
Networking: Tailscale funnels for ingress and TLS termination. No cert-manager, no Traefik.
Registry: Harbor (self-hosted container registry)
CI: Woodpecker CI on Forgejo
CD: ArgoCD with Image Updater for GitOps
Source: Forgejo (self-hosted Git) for service repos, GitHub for dev tools

Key Principle

Everything self-hosted. No external cloud dependencies except Tailscale for networking.

Procedures

sop-deploy-recovery — recovery procedure when deployments fail or pods crash
sop-ci-pipeline-recovery — recovery procedure when Woodpecker CI pipelines break
sop-postgres-restore — PostgreSQL backup restore procedure for CNPG-managed databases
sop-secrets-management — procedure for adding, rotating, or recovering secrets via Salt pillar pipeline