but the issue here isn't really hedging, it's that...
# spicedb
e
but the issue here isn't really hedging, it's that grpc isn't able to find any endpoints to talk to with the config it's been given I think that if we make the node unavailable until it gets an initial dispatch peer list + some metrics you could alert on if dispatch isn't able to refresh the peer list for some period of time would fix the issue? You wouldn't see requests hang because the spicedb pods wouldn't be available until they could get the peers from the kube api, but once they have that list they use the peers they have and just make noise if they have trouble keeping up