Report this

What is the reason for this report?

Communication with k8s/loadbalancer and a droplet in same DC - billed?

Posted on January 8, 2020

Hello, I have a scenario like this: https://www.digitalocean.com/community/questions/private-communication-between-a-external-droplet-and-a-pod-in-k8-cluster

It seems the only way to address the cluster is via the load balanced (and therefore public) IP.

I can do this from a droplet in the same DC (at <1ms latency), so it works, and I can use a firewall to limit access.

My question is, will I be billed for this communication, since it technically uses the public IP address, even though the machines are in the same DC?

Thanks!



This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Hi,

Yes, that would count against your bandwidth allowance. Any traffic that goes over the public interface is billed, regardless of the destination.

The documentation on bandwidth billing was recently updated to clarify that:

Any data transfer sent by a Droplet using a public network interface will count against the transfer pool for that Droplet’s account. All IPv6 traffic uses the public interface. Data transfer between Droplets over the private network uses a private network interface.

The developer cloud

Scale up as you grow — whether you're running one virtual machine or ten thousand.

Get started for free

Sign up and get $200 in credit for your first 60 days with DigitalOcean.*

*This promotional offer applies to new accounts only.