Hi Brandon,
Thanks for the link! Good to hear that it will be fixed in version 1.7. I will
try out the alpha version.
NodePort is working fine, the only drawback of it for my use case is that it
opens a port on all kubernetes nodes.
Thanks for the help!
On Tuesday, June 6, 2017 at 6:23:24
HostPort should be fixed in CNI and should be fixed-fixed in Kubernetes
1.7:
https://github.com/kubernetes/kubernetes/issues/23920#issuecomment-299535316
NodePort should work though, are you experiencing issues with that?
Brandon
On Tue, Jun 6, 2017 at 7:08 AM wrote:
>
Hi Brandon,
Thanks for the response.
Kafka is publishing a message to a topic in two-step process:
a. Connect to a broker which is a pod running on a kubernetes worker and get
metadata about the topic i.e. who is the leader of the topics partitions (info
stored in zookeeper)
b. Connect to
Find a Kubernetes Pod by Label Selector and Port-forward Locally
Given a namespace "your-namespace" and a label query that identifies the
pods you are interested in connect to a particular pod instance. If the
label selector doesn't find a unique pod it will connect to the first pod
by name.
Hello everybody,
I've setup a 3 node kafka cluster running on kubernetes using stateful sets and
headless services.
The problem is now I want read/write data from/to the cluster from outside the
cluster.
I have found a couple of suggestions here