You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
// FIXME: it would probably be good to filter this a little instead of just
// updating on all changes.
c.worker.EnqueueJob(&UpdateConfigJob{})
}
The function is called by several informers, for example nodeInformer, endpointsInformer and networkPoliciesInformer.
The problem is that this causes the function to be called several times on startup which in turn creates UpdateConfigJobs. An UpdateConfigJob is therefore run before even one SyncServiceJob has been successfully executed.
This results in an empty config to be pushed to the agent on startup.
Possible solutions:
Subscribe to the informers only after all services have been synced once
Increase timeout for UpdateConfigJob scheduling (enough time so that the job is not executed before the ``SyncServiceJobs`)
?
The text was updated successfully, but these errors were encountered:
The
handleAuxUpdated
function of the controller enqueues aUpdateConfigJob
:ch-k8s-lbaas/internal/controller/controller.go
Lines 309 to 313 in 84662aa
The function is called by several informers, for example
nodeInformer
,endpointsInformer
andnetworkPoliciesInformer
.The problem is that this causes the function to be called several times on startup which in turn creates
UpdateConfigJobs
. AnUpdateConfigJob
is therefore run before even oneSyncServiceJob
has been successfully executed.This results in an empty config to be pushed to the agent on startup.
Possible solutions:
UpdateConfigJob
scheduling (enough time so that the job is not executed before the ``SyncServiceJobs`)The text was updated successfully, but these errors were encountered: