Hey friend, our load balancers are a managed service and team up nicely with our cloud firewalls, this is a route I’d suggest (and that we use for ourselves) and the firewalls will apply to the DOKS clusters–we’ll handle the LBs for you– you can find the firewall docs here: https://www.digitalocean.com/docs/networking/firewalls/

i tried loadBalancerSourceRanges: and it does not appear to be supported by DO.

I also tried DO Firewalls with no success. it is not clear how DO firewalls can limit load balancer traffic to our private IP addresses.

my objective for using the load balancer is to expose services to other kubernetes clusters (or other droplets) in the same region via static IP without exposing it publicly.

I’m also posting to confirm that loadBalancerSourceRanges did not work for me in the k8s LoadBalancer config. Since all traffic to the pods are directed through the Kubernetes controllers, it also means that we can’t rely on the normal firewall product (as the source IP’s are of the Kubernetes internal services).

As far as I can tell, you cannot currently use the firewall product with Kubernetes.

Looks like nor Firewall doesn’t work with k8s :(

Same here, how to limit the access to Ingress Ip which seem to be DO LoadBalncer product? this is quite critical feature

not having loadBalancerSourceRanges is quite a concern for us. Please look at implementing this DigitalOcean!

Same here. loadBalancerSourceRanges doesn’t work.

loadBalancerSourceRanges is our big concern about using kubernetes on DO!!! Hope it would be on the feature list…

Same here, it would be nice to have this option, as there is no direct way to secure the Ingress controller without getting fancy with the nginx configuration.

Yes, please all the load balancers to be ingress limited.
On a side note I just tried to “+1” which the system dismissed as spam… ;)