3 ms·
Why can you not have downtime-free deploys? You tell your applications to drain connections and gracefully exit on SIGTERM. https://pkg.go.dev/net/http#Server.S
by ferdowsi 5y ago
Why can you not have downtime-free deploys? You tell your applications to drain connections and gracefully exit on SIGTERM. https://pkg.go.dev/net/http#Server.Shutdown https://pkg.go.dev/net/http#Server.Shutdown
If your server is incapable of gracefully exiting, that's not a K8s problem.
- afrodc_ 5y ago> Why can you not have downtime-free deploys? You tell your applications to drain connections and gracefully exit on SIGTERM. https://pkg.go.dev/net/http#Server.Shutdown https://pkg.go.dev/net/http#Server.Shutdown > If your server is incapable of gracefully exiting, that's not a K8s problem. Also whatever load balancer/service mesh you have can be configured for 503 rerouting within DC as necessary too.
- bajsejohannes 5y ago> You tell your applications to drain connections and gracefully exit on SIGTERM. The problem is that k8s will send requests to your application after SIGTERM. So you have to wait some amount of time before shutting down to allow for that. This was at least the case last time I used k8s, and it seemed like it was due to the distributed architecture, so something that was more than a mere bugfix away.