Scalable compute services.
Simple object storage.
Run managed Kubernetes clusters.
Tools & Integrations
Automate your infrastructure.
Deploy pre-built applications.
Connect, share and learn
DevOps and development guides
Questions & Answers
Development and systems Q&A
by Justin Ellingwood
not only droplets but also load balancers should be put behind the firewalls
Internal load balancers are desperatly needed when load balancing internal services (like search servers). And DNS load balancing doesn't cut it :-/
Can't reiterate enough the need for this feature. Having control over private IP's within the VPC would be excellent as well. Which would allow for keepalived to float private IP's between hosts.
Hey DO, this is a big one for us as well, pushing to go live with a new platform and would love to use your load balancing service - however, need it to be able to sit behind a firewall. Cheers.
Kubernetes in combination with VPC is useless if there is no sane way to create a private loadbalancer.
Same here, it's a really important feature for me and my clients. Do you have any on a release date ?
It's really a mandatory feature for my clients to switch to Digital Ocean, any way to make that happen in the close future?
we need this asap. WE are deploying our dev & staging env on K8 & would not wait these Env to be accessible from public internet & to be locked down to our office IP or VPN
This would have been very useful in our case: our traffic is proxied through Cloudflare, so I want to ensure all requests to the load balancer come from Cloudflare's servers (IP ranges).
You won't be notified about changes to this idea.