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
Since the last update to release-0.15, I've been getting readiness probe failed occasionally on my Grafana Pod.
I found out that it is caused by reaching the limit when the Pod needs more than 200Mi of memory.
I checked the official Grafana documentation and found the minimum requirements for deploying on kubernetes, so I changed the Requests and Limits of the Pod accordingly.
Since then, I no longer get the error I mentioned earlier.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi.
Since the last update to release-0.15, I've been getting readiness probe failed occasionally on my Grafana Pod.
I found out that it is caused by reaching the limit when the Pod needs more than 200Mi of memory.
I checked the official Grafana documentation and found the minimum requirements for deploying on kubernetes, so I changed the Requests and Limits of the Pod accordingly.
Since then, I no longer get the error I mentioned earlier.
(https://grafana.com/docs/grafana/latest/setup-grafana/installation/kubernetes/#minimum-hardware-requirements)
I have a question, why does the manifest (grafana-deployment.yaml) here adopt the following configuration values?
(for example, in previous versions, the following were minimum requirements)
I've looked through the issues and discussions here, but couldn't find anything that looked like it.
Does anyone know of any?
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions