3 ms·

Then I assume you have a custom Kubernetes LB that can handle non-HTTP TCP and UDP traffic because you choosing Kubernetes and the design restrictions that com

Then I assume you have a custom Kubernetes LB that can handle non-HTTP TCP and UDP traffic because you choosing Kubernetes and the design restrictions that comes with it does not affect how the dev solves problems? The underlying orchestrator definitely affects how the software needs to behave and is definitely not irrelevant.

znpy 3y ago
> Then I assume you have a custom Kubernetes LB that can handle non-HTTP TCP and UDP traffic because you choosing Kubernetes and the design restrictions that comes with it does not affect how the dev solves problems? nginx-ingress-controller does that. no custom stuff required. https://kubernetes.github.io/ingress-nginx/user-guide/exposing-tcp-udp-services/ https://kubernetes.github.io/ingress-nginx/user-guide/exposi...
ongy 3y ago
Which LB doesn't support non-http flows?
jameshart 3y ago
Follow the signposts laid out by https://12factor.net https://12factor.net. Think about how to apply those ideas to containerized applications. Consider that such applications can be run in the same way locally, on a server, or in an autoscaled cluster. Not sure why TCP/UDP load balancing complicates matters.