Closed bryanchriswhite closed 1 year ago
This seems to only apply in scenarios where the indexer is running in a different cluster than the fetchd node it is querying.
Closing as this is a known phenomenon related to network security mechanisms of fetchd and has limited applicability (i.e. non-production environments).
Background
This is the error occurs frequently and causes the deployment to go into crashloop backoff: