4 ms·

Deploying them is easy. Figuring out the correct incantations to bind a load balancer or ingress port to redis/kafka/mysql/whatever and/or expose them in some w

Deploying them is easy. Figuring out the correct incantations to bind a load balancer or ingress port to redis/kafka/mysql/whatever and/or expose them in some way other than "let the ingress figure out the host from headers/SNI and map to some thing in the Service" is somewhat less than intuitive. Sure, you could argue that you shouldn't expose backend services like that without an API endpoint at all, because one application->one namespace, or you could use a service mesh/consul to expose it to the things that need it, but it's an entirely different mindset from "I have a postgres cluster in public/private cloud"

kuschku 4y ago
The Gateway API is entering beta! It'll resolve pretty much what you're aiming for.
CameronNemo 4y ago
LoadBalancerIP seems pretty straightforward to me. No Ingress or Gateway needed. Just a plain old Service. I don't think that would cause issues with long lived connections. It is about as direct as you can get while actually load balancing. https://cloud.google.com/kubernetes-engine/docs/how-to/service-parameters https://cloud.google.com/kubernetes-engine/docs/how-to/servi...