I noticed that when cluster dispatch is incorrectly setup (e.g. watch gets 403), calls to SpiceDB (e.g. zed permission check) would hang forever and never return. What I see in the logs is the following:

log: 2022/02/15 18:19:11 ERROR: kuberesolver: watching ended with error='invalid response code 403 for service spicedb-internal in namespace spicedb-staging', will reconnect again

Also noticed that the log from kuberesolver is not doing structured logging