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
Some sort of egress gateway could be really useful for whitelisting purpose and hidding the real server ips.
Yes, yes, yes, a thousand times yes. I need this. I got an app that has to connect to external APIs from a whitelisted IP. So I need either this, or K8SX-I-4. To accomplish this so I can finally migrate away from a normal droplet with a floating IP configured for outbound to K8.
Yep, this is really needed. The workaround of adding each IP individually to whitelist on external services is really time consuming, not to mention downtimes are practically guaranteed upon node reboot.
I did whitelist the node ips so it was able to receive data from an api. After that I did upgrade my nodes to newer kubernetes version and now I have new ips. I think this is a issue more people have. Please add this feature it is needed
Just had this same problem, every time the k8s nodes reboot, the ip address for the nodes change and therefore have to update the external service that only allows whitelisted IP's. For this reason DO kubernetes doesn't work for us yet for production.
You won't be notified about changes to this idea.