not sure if kuberesolver would be open to changing their logging, but we could ask the spicedb behavior seems reasonable for initial startup. we don't want to fail fast on connecting to dispatch peers (kube api is not expected to be as highly available as spicedb). we should probably have some metrics that you can hang alerts off of so that you know if the peer list isn't being updated arguably we should fall back to hitting the datastore directly if dispatch is unavailable, but I think at best that should be a flag since that could cascade a spicedb node failure into much higher than normal datastore load and potentially affect the entire spicedb cluster