Related

Join the DigitalOcean Community Community

Join 1M+ other developers and:

  • Get help and share knowledge in Q&A
  • Subscribe to topics of interest
  • Get courses & tools that help you grow as a developer or small business owner
 Join Now
After updating bind-address in /etc/msql/my.cnf file MySQL stops working Question Question
Node request for certain site results in ETIMEDOUT error most of the time. Why?? Question Question

Question

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

Posted August 25, 2019 1.6k views
Arch LinuxNetworkingKubernetes

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!

Add a comment
last61474
By:
last61474

Related

Join the DigitalOcean Community Community

Join 1M+ other developers and:

  • Get help and share knowledge in Q&A
  • Subscribe to topics of interest
  • Get courses & tools that help you grow as a developer or small business owner
 Join Now
After updating bind-address in /etc/msql/my.cnf file MySQL stops working Question Question
Node request for certain site results in ETIMEDOUT error most of the time. Why?? Question Question

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.

×
Submit an Answer
1 answer
jkwiatkoski August 26, 2019

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

Reply Report
  • kyawthetkhine January 8, 2021

    Is there now this kind of communication between DOKS and exernal droplet in the same VPC? I like to setup like this scenario. And DO support this feature yet?

    Reply Report

Related

Looking for something else?

Ask a new question Search for more help