Devops Observability Quality
4 sectionsDevOps, Observability & Quality Gates
TL;DR
The Platform runs on a self-managed Kubernetes cluster (K3s) on Hetzner, in a single dloizides namespace, with a separate staging cluster used to run nightly tests against production. Container images are built, pushed to a private registry…
Read →How it works
The whole system is a loop: you change code, verify it through Tilt-driven gates, deploy a digest-pinned image with manage.sh, and then watch the deployed result through observability and smoke tooling. Here is the high-level pipeline.
Read →How to use it
The day-to-day developer loop is change → verify → deploy → watch.
Read →Key takeaways
runs the nightly tests against production (keeping test load off prod). - Digest-pinned deploys (@sha256:<digest>, not mutable tags) make every deploy reproducible and every rollback exact; images travel through a private registry over
Read →