Zookeeper authentication failed

Nobody has claimed this yet.

Hello, I'm trying to connect to a zookeeper server, and am noticing I am able to connect to the server IP, but subsequently receive authentication failure issues. I am trying to diagnose if this something Burrow related, or related to my internal zookeeper address.

Obviously for public visibility I've muted my explicit zookeeper/kafka address, but have confirmed they exist and are indeed accesible services on Kubernetes.

Here's a simplified burrow log

**Burrow.log**

│ burrow-7cbc6fbfd9-khq8t {"level":"info","ts":1678824749.858517,"msg":"Connected to host:port","type":"coordinator","name":"zookeeper"} │ │
│ burrow-7cbc6fbfd9-khq8t {"level":"info","ts":1678824749.859253,"msg":"authentication failed: EOF","type":"coordinator","name":"zookeeper"} │ │
│ burrow-7cbc6fbfd9-khq8t {"level":"error","ts":1678824749.8593042,"msg":"cannot create root path","type":"coordinator","name":"zookeeper","error":"zk: could not connect to a server"}

Here's my **Burrow.toml**

[zookeeper]
servers=["host:port"]
rootpath="/etc/burrow"
timeout=6

[kafka]
brokers=["host:port"]

Start with the Burrow.log authentication failure and the [zookeeper] and [kafka] sections of Burrow.toml. Determine whether the failure originates in Burrow or the Kubernetes-hosted ZooKeeper address, and document the configuration or diagnostic result that explains the authentication error.

Written by the indexing model from the issue text.