We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
just installed multus on a cluster and getting OOM killed directly
cluster:
All pod are just about 50Mb, while the limit 50.
│ kube-multus-ds-5s4g2 ● 1/1 Running 0 0 53 0 0 107 53 192.168.41.27 srv27 3m33s │ │ kube-multus-ds-cvtp2 ● 1/1 Running 0 0 54 0 0 109 54 192.168.41.21 srv21 3m33s │ │ kube-multus-ds-hz676 ● 1/1 Running 0 1 53 1 1 107 53 192.168.41.25 srv25 3m33s │ │ kube-multus-ds-jlnp9 ● 1/1 Running 0 1 53 1 1 107 53 192.168.41.26 srv26 3m33s │ │ kube-multus-ds-zjv5v ● 1/1 Running 0 1 54 1 1 109 54 192.168.41.22 srv22 3m33s
The text was updated successfully, but these errors were encountered:
You should consider modifying the default install yaml to fit your environment and see if you can get it to run in your environment.
...but, maybe the default is too low.
Sorry, something went wrong.
yep, I did changed the limit because pods were killed straight away. Now I see that pods are starting using ~53Mb
This is why I created the issue, it should probably be increase a bit. Now I'm wondering why nobody saw that before 🤔
No branches or pull requests
just installed multus on a cluster and getting OOM killed directly
cluster:
All pod are just about 50Mb, while the limit 50.
The text was updated successfully, but these errors were encountered: