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
{{ message }}
This repository has been archived by the owner on May 16, 2023. It is now read-only.
Hi @nikitakazantsev12,
Can you add more details?
Knowing which chart you are mentioning and what use case would need it would help us to be able to answer you.
@jmlrt, sorry I didn't realize that's a general charts topic. So, I am talking about the Kibana chart. There is a readiness probe implemented, but no liveness probe, so we have to roll it out additionally patching existing Helm deployment, which is not exactly comfortable.
The use case:
We have sometimes troubles with an Elasticsearch cluster because of some development/testing activities. That makes a Kibana to come into a failure state (503 Error in GUI). After restarting a Pod the Kibana comes up healthy. A Liveness-Probe would let us automate that process to increase an availability.
jmlrt
changed the title
livenessProbe
Create Kibana livenessProbe
Aug 27, 2020
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
I would like to suggest an implementation of a livenessProbe into the chart. Might be useful for this or that use case.
The text was updated successfully, but these errors were encountered: