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
We have the default value settings for the cpu/memory resources as per the values.yaml. However we noticed that after a few days the pod goes to Evicted status.
We have a very low utilization right now and using the developer portal just for a trial.
Can you please provide any suggestion on these params?
Would 512MiB memory and 100m cpu request be reasonable?
Thanks,
Bhuvan!
The text was updated successfully, but these errors were encountered:
Which pod is being evicted? We are running quite a few instances on Kubernetes, and very seldom we run into OOM problems with the standard settings, and I must admit I have never seen Evicted. If you do a kubectl describe pod of the pod which was evicted, it should tell you why that happened; what does it say?
Good Morning, Martin.
We have the default value settings for the cpu/memory resources as per the values.yaml. However we noticed that after a few days the pod goes to Evicted status.
We have a very low utilization right now and using the developer portal just for a trial.
Can you please provide any suggestion on these params?
Would 512MiB memory and 100m cpu request be reasonable?
Thanks,
Bhuvan!
The text was updated successfully, but these errors were encountered: