The K8s slack channel is pretty good for things like this.
You can either bind the container to a host port and register the ip of the node (or use the k8s dns or api to find the ips). Otherwise register a service with a nodeport and all the nodes will accept traffic and load balance internally.
You can get a list of ips from the DNS (instead of just the service ip), and I think that interacts appropriately with host ports.
You can either bind the container to a host port and register the ip of the node (or use the k8s dns or api to find the ips). Otherwise register a service with a nodeport and all the nodes will accept traffic and load balance internally.
You can get a list of ips from the DNS (instead of just the service ip), and I think that interacts appropriately with host ports.