[Bug] nslookup in apachepulsar/pulsar:3.3.0 isn't compatible with kubernetes search domains

[lhotari]

Search before asking

• I searched in the issues and found nothing similar.

Read release policy

• I understand that unsupported versions don't get bug fixes. I will attempt to reproduce the issue on a supported version of Pulsar client and Pulsar broker.

Version

apachepulsar/pulsar:3.3.0 image

Minimal reproduce step

See lhotari/pulsar-helm-chart#10

What did you expect to see?

Pulsar cluster would start up without errors.

What did you see instead?

Init containers waiting for Zookeeper to come available are failing:

Server:        10.96.0.10
Address:    10.96.0.10:53

** server can't find pulsar-ci-zookeeper-0.pulsar-ci-zookeeper.pulsar: NXDOMAIN

** server can't find pulsar-ci-zookeeper-0.pulsar-ci-zookeeper.pulsar: NXDOMAIN

Anything else?

Debugged the problem. FQDN nslookup works, partial domain name doesn't.

pulsar-ci-pulsar-init-pfdv8:/pulsar$ nslookup pulsar-ci-zookeeper-0.pulsar-ci-zookeeper.pulsar.svc.cluster.local
Server:         10.96.0.10
Address:        10.96.0.10:53

Name:   pulsar-ci-zookeeper-0.pulsar-ci-zookeeper.pulsar.svc.cluster.local
Address: 10.244.1.17


pulsar-ci-pulsar-init-pfdv8:/pulsar$ nslookup pulsar-ci-zookeeper-0.pulsar-ci-zookeeper.pulsar
Server:         10.96.0.10
Address:        10.96.0.10:53

** server can't find pulsar-ci-zookeeper-0.pulsar-ci-zookeeper.pulsar: NXDOMAIN

** server can't find pulsar-ci-zookeeper-0.pulsar-ci-zookeeper.pulsar: NXDOMAIN

/etc/resolv.conf is

search pulsar.svc.cluster.local svc.cluster.local cluster.local 1evhaya2a4vu1idbbq22av5vmh.bx.internal.cloudapp.net
nameserver 10.96.0.10
options ndots:5

The busybox nslookup isn't compatible with search domains and ndots. It is necessary to install bind-tools package with apk add bind-tools. Found this information in docker-library/busybox#48 (comment)

Are you willing to submit a PR?

• I'm willing to submit a PR!