Has anyone seen issues with the helm chart deploy of cockroachdb with peer-finder init container hanging? We are deploying to a non-default namespace and providing the proper namespace and domain args. It works fine for the first 2 nodes, but hangs on init for the 3rd.
Executing dig and nslookup commands on the pod return the peer list successfully.
A teammate has suggested it may be from this issue in go in the underlying peer-finder image: