argo-rollouts: kubectl argo rollouts dashboard OOM kill
Summary
What happened/what you expected to happen?
kubectl argo rollouts dashboard high memory usage.

before long time, this pod OOM kill!!
Diagnostics
kubectl-argo-rollouts: v1.2.1+51c874c
BuildDate: 2022-05-13T20:40:45Z
GitCommit: 51c874cb18e6adccf677766ac561c3dbf69a8ec1
GitTreeState: clean
GoVersion: go1.17.6
Compiler: gc
Platform: linux/amd64
Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritize the issues with the most 👍.
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 8
- Comments: 18 (7 by maintainers)
Commits related to this issue
- fix(dashboard): cleanup viewcontroller after each request. Fixes #2095 — committed to unrolled/argo-rollouts by unrolled 2 years ago
- fix(dashboard): cleanup viewcontroller after each request. Fixes #2095 Signed-off-by: Cory Jacobsen <cory@7shifts.com> — committed to unrolled/argo-rollouts by unrolled 2 years ago
- fix(dashboard): Cleanup viewcontroller after each request. Fixes #2095 (#3966) fix(dashboard): cleanup viewcontroller after each request. Fixes #2095 Signed-off-by: Cory Jacobsen <cory@7shifts.com... — committed to y-rabie/argo-rollouts by unrolled 2 years ago
- fix(dashboard): Cleanup viewcontroller after each request. Fixes #2095 (#3966) fix(dashboard): cleanup viewcontroller after each request. Fixes #2095 Signed-off-by: Cory Jacobsen <cory@7shifts.com... — committed to Rizwana777/argo-rollouts by unrolled 2 years ago
- fix(dashboard): Cleanup viewcontroller after each request. Fixes #2095 (#3966) fix(dashboard): cleanup viewcontroller after each request. Fixes #2095 Signed-off-by: Cory Jacobsen <cory@7shifts.com... — committed to CircleCI-Public/argo-rollouts by unrolled 2 years ago
- fix(dashboard): Cleanup viewcontroller after each request. Fixes #2095 (#3966) fix(dashboard): cleanup viewcontroller after each request. Fixes #2095 Signed-off-by: Cory Jacobsen <cory@7shifts.com... — committed to tperdue321/argo-rollouts by unrolled 2 years ago
It appears that even in the latest version 1.7.2, there is still a memory leak in the Argo Rollouts dashboard. With just 9 rollouts across 2 applications, after only an hour of simple browsing, it starts consuming over 200MB of RAM.
Just a quick update: I investigated the cause of the RAM usage increase, and it seems that each time a Rollout is in progress, something is being added to memory and not cleared afterward. This might be related to specific strategy parameters, as we don’t observe this behavior on the staging cluster.
Upd 2: it looks like the issue is when Rollout with unlimited pause is processing ( - pause: {} )
你好,我已经收到邮件!