Ask HN: How to scale long-lived connections with Kubernetes?
My application serves users via long lived TCP connections and users are quite volatile. They come and go without any obvious patterns. And my current approach of scaling based on CPU/memory usage are too damn barbaric. I should not break active connections, but I also need to control the cost. On top my head, I can think of writing a custom middleware to manage connections and pods. Are there any ready-to-use solutions or approaches to tackle similar problems? Thanks