Which bookie, 0, 1, 2? This looks like bookie2 is unreachable from the other bookies. So I would a) confirm that is the case in the other bookie logs, b) Confirm that bookie2 process is healthy and listening on port 3181 using

kubectl log

etc, and c) check networking, i.e. does the

clusters-bookie-2.pulsar-clusters-bookie.pulsar-pcq-default.svc.cluster.local

name resolve to the correct IP in DNS lookup etc.