go podcast() 078: Uncloud, bridging the gap between Docker and Kubernetes
4 snips
Mar 26, 2026 Pasha Zvideryski, a software developer who built Uncloud after work in infrastructure at Canva and JetBrains. He talks about simplifying deployments by bridging Docker and multi-machine setups. Discussions cover push vs pull deployment models, Compose-format production deployments, WireGuard mesh overlay networking, Caddy-based ingress and rolling updates, and Unregistry for image distribution.
AI Snips
Chapters
Transcript
Episode notes
Kubernetes Tradeoff Between Scale And Debuggability
- Kubernetes' reconciliation model scales but sacrifices visibility and troubleshooting, creating deep indirection when things fail.
- Pasha built Uncloud as a simpler alternative because Kubernetes often adds more problems than it solves for small-to-medium deployments.
Reuse Docker Compose To Reduce Friction
- Use familiar tooling to lower friction: Uncloud accepts Docker Compose spec so teams reuse existing manifests.
- Write a compose.yaml locally then run one deploy command to build and roll out containers to your servers.
Agent Mesh And Caddy Create Distributed Ingress
- Each machine runs an agent, forms a WireGuard full-mesh, and hosts Caddy as the ingress so any node can be an entry point.
- Public DNS or an external load balancer directs traffic to one or more Caddy instances which reverse-proxy to services.