-
Bug
-
Resolution: Done
-
Critical
-
None
-
4.10.z
Description of problem:
Compliance Operator pod was CrashLooping due to OOM after upgrading to 0.1.57. Memory was increased to 2gb and the pod still OOM'd before fully starting. Memory was increased to 4gb and the pod started at 2.2gb. After about a week, the pod is up to 3.1gb $ oc adm top pod NAME CPU(cores) MEMORY(bytes) compliance-operator-5f496ccb79-j2l97 8m 3109Mi In smaller clusters, they started with 500mb of memory, but ended up OOM killed about 10 days later. Memory was upped to 1gb.
Version-Release number of selected component (if applicable):
0.1.57
How reproducible:
Always in this cluster
Steps to Reproduce:
1. Default config 2. 3.
Actual results:
Memory increase and OOM
Expected results:
Stable memory profile
Additional info:
- links to