Upgrades do not drop SSH
dpipe owns the file descriptor, not dproxy. Connection lifetime is deliberately decoupled from the lifetime of the process that accepted it, so shipping a new dproxy disconnects nobody.
Architecture
- physical host
- microVM
- Go binary
- container
- database
- network device
- kernel ruleset
A diagram of the dummie architecture: a control plane on the left, reached by clients, and a QEMU host on the right running the ingress proxies, the per-run policy services and the microVMs. Each component is a button; activating one shows a description beside it.
https · /api/v1
control plane run once
reads and writes
control assigns work to dclient
public ingress
unix socket · fd passing
bytes to the guest
every packet and every name meets policy
per-run policy
starts and configures all of the above
Point at any box — or tap it — to read what that piece does.
Things the picture does not say
Guest do not need any credentials
Credentials are injected in realtime into requests by intproxy, so the guest VMs can operate without having any keys on them
Restarts do not disconnect anyone
Every single compoenet (with the obvious exception of microVMs) can be restarted without affecting workloads running on the VM
Best viewed on a desktop