3 ms·

> solving a specific problem The problem to me is that Kubernetes is not solving a specific problem, but a whole slew of problems. And some of them it's solvin

> solving a specific problem The problem to me is that Kubernetes is not solving a specific problem, but a whole slew of problems. And some of them it's solving really poorly. For example, you can't really have downtime-free deploys in kubernetes (set a longish timer from SIGTERM to increase the chance that there's no downtime). Instead I'd rather solve each problem in a good way. It's not that hard. I'm not implementing it from scratch, but with good tools that exists outside of kubernetes and actually solve a specific problem.

hnjst 5y ago
You can actually renew/upgrade your whole cluster with no downtime if you care enough to tackle the annoying bits that cost a few minutes in YOLO mode.
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.
rhacker 5y ago
K8s has like, probably the most complete support for readiness/no downtime deploys in the whole damn industry so it's surprising to hear that... https://cloud.google.com/blog/products/containers-kubernetes/kubernetes-best-practices-setting-up-health-checks-with-readiness-and-liveness-probes https://cloud.google.com/blog/products/containers-kubernetes...

hnjst 5y ago

You can actually renew/upgrade your whole cluster with no downtime if you care enough to tackle the annoying bits that cost a few minutes in YOLO mode.

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.

rhacker 5y ago

K8s has like, probably the most complete support for readiness/no downtime deploys in the whole damn industry so it's surprising to hear that... https://cloud.google.com/blog/products/containers-kubernetes/kubernetes-best-practices-setting-up-health-checks-with-readiness-and-liveness-probes https://cloud.google.com/blog/products/containers-kubernetes...