Skip to content
First post ships with first cohort

Build logs. Post-mortems.

No fluff. No tutorials. Real lessons from running the reference Beelab build. First post lands with the first cohort.

Queued posts

  • Architecture

    Why sovereign clusters need multiple Kubernetes flavors, not one

    Production immutability, lab iteration, and edge deployment ask different things from the cluster. Why running Talos, K3s, and Docker side by side is the durable on-prem pattern.

  • Compliance

    PARSO-SAMAD in practice: a ten-pillar self-assessment checklist for on-prem racks

    Portable, Automated, Recoverable, Secure, Observable, Scalable, Auditable, Maintainable, Accessible, Durable. The framework Beelab is self-assessed against, broken down with the verification commands that prove each pillar.

  • GitOps

    How GitOps changes the runbook posture on a private Kubernetes cluster

    When every change lives in Git and ArgoCD reconciles drift continuously, the runbook stops being a checklist and becomes a code review. What that shifts about on-call, change windows, and audit trails.