gloo-mesh
gloo-mesh copied to clipboard
gloo-mesh networking errors all input resources on boot
Describe the bug currently, gloo-mesh does not wait to process/create clients for all registered clusters before it begins reconciling. therefore, the first few iterations of the reconciler will produce the error:
- 'write error: failed to get client for cluster mgmt-cluster: Failed to get manager
for cluster mgmt-cluster'
which will put all input resources into an errored state.
To Reproduce
start a kubectl watch
on any input resource for gloo-mesh
restart gloo mesh networking pod
Expected behavior gloo mesh should wait for all clusters to "warm" (process the whole set of registered clusters) before reconciling input resources
Additional context this is a generic skv2 problem with our multicluster approach
previous to #1087 we were not seeing these errors get reported to input resources because we were simply logging the error and dropping them