0

I am using a vendor solution that gets deployed as a DaemonSet in my Kubernetes cluster. These pods expose a service on a TCP port.

I would like to author a DaemonSet that would connect this service endpoint. I would like all of my DaemonSet pod instances to connect to the local vendor DaemonSet pod instance so that I can have 100% coverage. This will also be more efficient as the data won't travel over the network (the service endpoint generates alot of data). What is the best way to discover the local IP of the vendor DaemonSet pod instance from my DaemonSet pod instance?

I found a few solution that recommend using HostIP (how to communicate with daemonset pod from another pod in the same node?). The issue is that this service port is not mapped to a host port. As I don't own the vendor DaemonSet, I can't update it to use this model.

0 Answers0