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

Current memory limit causes OOM #233

Closed
jhead-slg opened this issue Apr 16, 2021 · 1 comment · Fixed by #234
Closed

Current memory limit causes OOM #233

jhead-slg opened this issue Apr 16, 2021 · 1 comment · Fixed by #234

Comments

@jhead-slg
Copy link
Contributor

What steps did you take and what happened:
With larger clusters (100+) machines and a lot of machine deployments happening the container uses up to ~35Mi of memory. It was getting OOM killed until I modified the limit to be 50Mi instead of the current 30Mi.

What did you expect to happen:
The pod should not OOM.

Anything else you would like to add:
N/A

Environment:

  • cluster-api-provider-packet version: v0.3.9
  • Kubernetes version: (use kubectl version):
  • OS (e.g. from /etc/os-release):
@detiber
Copy link
Member

detiber commented Apr 16, 2021

@jhead-slg thanks for reporting this, I went ahead and created #234 to address it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants