Report this

What is the reason for this report?

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

Posted on August 25, 2019

Hello!

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.

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 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(https://github.com/kubernetes/ingress-nginx) , and then configure ingress rules using ingress objects(https://kubernetes.io/docs/concepts/services-networking/ingress/).

By using this you can setup a whitelist on the ingress controller and whitelist your external droplet’s IP: https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/annotations/#whitelist-source-range

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

Regards,

John Kwiatkoski Senior Developer Support Engineer

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.