2 ms·
You were talking about cloud, now you are talking about bare metal? Of course you have to route traffic to your cluster, but you are implying some cloud based
by verdverm 4y ago
You were talking about cloud, now you are talking about bare metal?
Of course you have to route traffic to your cluster, but you are implying some cloud based load balancer lockin which just isn't true
- chucky_z 4y agoI believe the OP is talking about LoadBalancer (https://kubernetes.io/docs/tasks/access-application-cluster/create-external-load-balancer/ https://kubernetes.io/docs/tasks/access-application-cluster/...), and I believe you're talking about Ingress (https://kubernetes.io/docs/concepts/services-networking/ingress/ https://kubernetes.io/docs/concepts/services-networking/ingr...).
- verdverm 4y agoIt's still an optional, rarely used service config, and does not imply lockin
- buzer 4y agoIt's very commonly used by the ingress controllers. You can get things working with hostNetwork or custom service port ranges, but that's a lot rarer than doing it via load balancer. Third option would be to expose pods directly in the network. EKS does this by default, but from my experience it's quite rare for people to leverage it.
- verdverm 4y agoYes, an ingress resource will typically create a load balancer if you are in the cloud, but not a service resource.