As I try to install the Prometheus Stack Helm chart v33 on a Kubernetes 1.20 cluster, I see the "main" pod that, among other things, manages the TSDB database, go through the process of processing WAL segments. This frequently takes a very long time, and the process is interrupted and restarted and so on for ever.
In the events list for the pod I see this: *Normal Killing pod/prometheus-prometheus-kube-prometheus-prometheus-0 Container prometheus failed startup probe, will be restarted* Now, the deployment YAML for this pod shows a startup probe config with 60 checks every 15sec. This implies a total of 15min till the pod is declared problematic. Is there a way for me to increase the startup config, so as to allow for more than 15min? This very likely would eliminate the restarts. Yet in the values file of the chart I can't see how I can enter such probe settings. Thanks for your help. -- You received this message because you are subscribed to the Google Groups "Prometheus Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/73551892-9b5d-4d53-955e-faf1fe85b58en%40googlegroups.com.
