Open gregbanks opened 6 years ago
this is happening in the current v2 implementation and was happening in the v1 implementation as well.
anecdotally, this seems to only happen on provision. bouncing the container fixes the issue.
func (b *KubernetesPerNodeBackend) Ready() bool { return cache.WaitForCacheSync(b.stopCh, b.kubeEndpointListerSynced, b.serviceListerSynced) }
note, there is actually very little happening before Ready gets called, which may point to a race or inconsistency elsewhere.
Ready
this is happening in the current v2 implementation and was happening in the v1 implementation as well.
anecdotally, this seems to only happen on provision. bouncing the container fixes the issue.
note, there is actually very little happening before
Ready
gets called, which may point to a race or inconsistency elsewhere.