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
From a fresh OKD installation with Cilium as CNI, I saw a high CPU usage on cilium-olm operator pod.
After checking issues, I'm not alone. It looks like, it's ok for other users of this operator to use 1 CPU nonstop.
Hello,
From a fresh OKD installation with Cilium as CNI, I saw a high CPU usage on cilium-olm operator pod.
After checking issues, I'm not alone. It looks like, it's ok for other users of this operator to use 1 CPU nonstop.
Here a list of open issues:
cilium-olm
operator rewrites thecilium-olm
ConfigMap about once every 2 seconds #88My solution was to delete this operator (all pods are deleted), and re-installed with Helm.
It solves the issue because cilium-olm no longer exists.
Plus, Helm version is more up to date than this repo, currently 1.15.1 vs 1.16.2.
The text was updated successfully, but these errors were encountered: