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
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):
The text was updated successfully, but these errors were encountered:
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:
kubectl version
):/etc/os-release
):The text was updated successfully, but these errors were encountered: