himanshug edited a comment on issue #9496: druid management ui in kubernetes fails if more than one coordinator/overlord process URL: https://github.com/apache/druid/issues/9496#issuecomment-598355639 you can't point to service, druid(actually zookeeper client) needs to have all of zookeeper hosts individually listed like it is done in non-k8s deployments as well. (unless your zookeeper replica count is 1) if you deployed zookeeper using a stateful set, make sure to add `serviceName` (as in https://github.com/druid-io/druid-operator/blob/master/examples/tiny-cluster-zk.yaml#L29 ) in the StatefulSet. It is the magic attribute that sets `spec.subdomain` in launched pods which in turn leads to k8s cluster dns resolving fulling qualified zk pods names e.g. "tiny-cluster-zk-0.tiny-cluster-zk, tiny-cluster-zk-1.tiny-cluster-zk .. etc" https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/#pod-s-hostname-and-subdomain-fields doc describes same for pods. Note: you might have to make your service a "headless service" but it might work with non-headless service as well so try that first, make sure "nslookup <fully qualified zk pod name>" works on all druid pods. See https://github.com/kubernetes/website/pull/16376
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@druid.apache.org For additional commands, e-mail: commits-h...@druid.apache.org