CJW–07.5
apps that exercise the platform
personal lab
guide
V.0.5.0
services
services exist to prove the platform: source control, ci, developer portals with techdocs, monitoring, and a few real applications delivered through flux — not a shelf of containers with forgotten passwords.
01
platform services
the cluster continuously runs the control plane around apps: gitops, secrets, ingress, certificates, metrics, logs, alerts, and backup.
- —flux + gitea
- —vault + external secrets
- —ingress-nginx + cert-manager
- —prometheus / loki / grafana
- —velero
02
developer experience
gitea hosts the platform repo; gitea actions cover app ci; backstage-style portals and techdocs turn runbooks into something navigable instead of a pile of markdown only i can find.
- —gitea
- —gitea actions
- —backstage / portal
- —techdocs runbooks
03
applications
small real apps (portal, travel-planning, and similar) are deployed the same way platform components are — git merge, flux reconcile — so application delivery practices the paved road.
04
media & local ai
media stacks and local model serving still appear in the wider lab, but they are judged by ownership, backup, and network placement — and they do not redefine the kubernetes platform story.
- —media automation when useful
- —local model serving via the ai lab
05
operating idea
each service should answer ownership, backup, network path, and whether it is an experiment or something i actually rely on. adrs and runbooks are how that answer stays durable.