Private communication between a external droplet and a pod in k8 cluster


I am trying to figure out a means to have a private communication between a pod in k8 cluster and an external droplet in the same data centre from same account.

I know i can expose a loadbalancer/nodeport service from the pod and get access but i want a private networking between these and totally avoid public access.

Any insights are appreciated.


Submit an answer

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!

Sign In or Sign Up to Answer

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.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

Hi there!

Unfortunately, DOKS NodePort services only bind to the nodes public interface at this time. One option to control access is to use and ingress controller such as nginx( , and then configure ingress rules using ingress objects(

By using this you can setup a whitelist on the ingress controller and whitelist your external droplet’s IP:

This would allow you to expose that service publicly but only allow one IP to actually contact your service.


John Kwiatkoski Senior Developer Support Engineer