Sovereign docs
summary
Claim: publishing docs as containers yields a practical sovereign stack. Implementation uses MkDocs rendered into containers, per-component repos and a docs repo, CI/CD with Flux (and options like Woodpecker or Semaphore), container builds via Docker/Podman, registries like Harbor, and Trivy vulnerability scanning. Deployments support local preview, remote preview and air‑gapped sites across three distinct platforms and hyperscaler alternatives (Exoscale, Clever Cloud, OVHcloud, Open Telekom). The setup runs in production and materially reduces dependence on US cloud control. MkDocs in containers Flux for CD Trivy vulnerability scanning
AI-written summary · about
chapters (15)
- 0:00Sovereign Docs talk intro
- 1:50Why docs as code
- 3:35What is sovereign data and why it matters
- 8:55Containers and portable publishing
- 15:39Sovereign stack recipe
- 16:22Choosing free and open-source software
- 19:13Collaboration and CI/CD
- 21:27Container tools and management
- 24:15Hyperscalers vs sovereign hosting
- 26:47Next steps and summary
- 28:13Q&A: Cloud Act and encryption
- 29:57Q&A: Encryption and security
- 31:02Q&A: Multi-container use cases
- 32:27Q&A: Funding and tool control
- 33:31Q&A: Public docs and security
related talks
23mTreating Documentation like Code: a Practical Account
01h 01mClosing the documentation gap with Backstage.io
25mBuilding Docs like Code: Continuous Integration for Documentation
40mLet Your Software Supply Chain Ride with Kubernetes CI/CD
27mHigh-Security, Zero-Connectivity & Air-Gapped Clouds: Delivering Complex Software with the Open Component Model & Flux
16mFrom Podman to Prod: Building Trusted Container Images with Konflux on OpenShift
36mContainer Security Made Easy – Tools and Techniques for Developers
29mContainer Factory for Aerospace & Defense Enterprises