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
watch -n 0.1 time oc -n cilium get ConfigMap cilium-olm -o jsonpath='"{ .metadata.resourceVersion }"'
shows the .metadata.resourceVersion increasing by 10–15 units every 2 seconds. (We can see that oc command is nearly instant, from the digits of time moving while the .metadata.resourceVersion stays fixed for a while, then increases as described.)
Lowering the Deployment's replicas to 0 stops the increase, at least until our OpenShift olm operator restores the replica count to 1.
The text was updated successfully, but these errors were encountered:
domq
changed the title
cilium-olm operator rewrites the cilium-olm ConfigMap at a very high ratecilium-olm operator rewrites the cilium-olm ConfigMap about once every 2 seconds
Mar 8, 2024
2 seconds is the defaultRetryPeriod in leader elections, which might indicate a problem there (since a successful leader presumably shouldn't have to retry?).
shows the
.metadata.resourceVersion
increasing by 10–15 units every 2 seconds. (We can see thatoc
command is nearly instant, from the digits oftime
moving while the.metadata.resourceVersion
stays fixed for a while, then increases as described.)Lowering the Deployment's
replicas
to 0 stops the increase, at least until our OpenShift olm operator restores the replica count to 1.The text was updated successfully, but these errors were encountered: