3 ms·
>> As an aside, the current ingresses (including the Nginx one and Google's own GLB one) all have annoying deficiencies Agree, this is along the lines of what
by mephitix 9y ago
>> As an aside, the current ingresses (including the Nginx one and Google's own GLB one) all have annoying deficiencies
Agree, this is along the lines of what I meant. For example GCE ingress allows you to reference a global static IP while this is not possible with solely nginx ingress due to limitations with the TCP load balancer. There are separate ingress annotations for GKE/nginx/haproxy, etc. If I want to use the global-static-ip GCE annotation, this will make it a little harder to move to Azure.
- bonesss 9y agoTotally fair points, and vendor lock-in is something to be highly vigilant of. For some context, though: the ingress functionality is rather recent in Kubernetes and is still fleshing out in terms of demands in the market and across cloud providers. Another year or two will do a lot for equality and saner networking solutions for small-scale and bespoke K8s deployments. I got a little shock that I had to set up an ingress controller on each of my nodes (on our VMWare cluster), but going through the nuts and bolts of it I can see why it's hanging a bit behind the rest of the product. I think the devs are being smart letting the ecosystem mature a little instead of pushing out something half-baked and prematurely limiting.
- manigandham 9y agoYou can always layer these. Have a simple global ingress pointing to a service or daemon set of nginx/haproxy.