GitOps on the Edge: Maintaining Infrastructure of Sovereign Clients
summary
Customer implements GitOps on-prem for 280 potential edge sites with sovereign clients and banned public cloud, replacing zip scripts with a git repo, package repo and ansible-pull agents. 34 office locations reach basic deployment in about three quarters of a year; systemd services later migrate to Docker containers. Secrets use Mozilla SOPS, metrics use Prometheus remote write with Grafana, and a self-hosted CDN handles poor bandwidth — solution is working but still rolling out.
AI-written summary · about
chapters (10)
- 0:00Introduction to GitOps on Edge
- 1:30Why GitOps for distributed setups
- 4:19About my employer Iteratec
- 7:12Problem: Non-functional requirements
- 12:13Six challenges of sovereign clients
- 20:21Solving the infrastructure puzzle
- 24:56GitOps with Ansible Pull
- 27:27Architecture and security
- 28:52Results and next steps
- 31:39Q&A session
