Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Image Cleaner Plugin Crashes due to OOMKill #3600

Open
tshaiman opened this issue Apr 11, 2023 · 4 comments
Open

Image Cleaner Plugin Crashes due to OOMKill #3600

tshaiman opened this issue Apr 11, 2023 · 4 comments
Assignees

Comments

@tshaiman
Copy link

Describe the bug

  • when image cleaner runs on our cluster it crashes due to OOMKill
  • since this is a plugin, we cannot control its resource allocation

To Reproduce
Steps to reproduce the behavior:

  1. enable the plugin on large AKS Cluster ( few hundrerd Pods)
  2. wait for OOMLill
  3. investigate the Resource allocation : the pod has max of 100Mi RAM ,which for large clusters is insufficient

Expected behavior

  • consider release this component as Helm chart so customers can choose their own Mem allocations
  • increase Mem allocation on the plugin to at least 250Mi

Screenshots
image
image

Environment (please complete the following information):

  • Kubernetes version : 1.25.5
@tshaiman tshaiman added the bug label Apr 11, 2023
@ghost ghost added the action-required label May 6, 2023
@ghost
Copy link

ghost commented May 11, 2023

Action required from @Azure/aks-pm

@ghost ghost added the Needs Attention 👋 Issues needs attention/assignee/owner label May 11, 2023
@ghost
Copy link

ghost commented May 26, 2023

Issue needing attention of @Azure/aks-leads

@jiashun0011
Copy link

jiashun0011 commented May 30, 2023

@tshaiman we have fixed this issue in our April release and can you help confirm then we can close it.

@ghost ghost removed action-required Needs Attention 👋 Issues needs attention/assignee/owner labels May 30, 2023
@ghost ghost added the action-required label Jun 28, 2023
Copy link
Contributor

This issue has been automatically marked as stale because it has not had any activity for 30 days. It will be closed if no further activity occurs within 7 days of this comment. @jiashun0011, @CocoWang-wql, @miwithro

@microsoft-github-policy-service microsoft-github-policy-service bot added the stale Stale issue label Feb 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants