Nomad rolling update leaves TCP connections unresolved during migration
Goal: Determine whether Nomad's default rolling update behavior, which waits for a new allocation to pass its health check before stopping the old one, ensures zero‑downtime for small applications that rely on long‑lived TCP connections. Constraints: The update stanza can be tuned with max_parallel and health check intervals, but Nomad does not offer a built
nomad