I can't increase Prometheus startupProbe failureThreshold value about cluster-monitoring-operator HOT 6 CLOSED

The startup probe delay should be 1h already in 4.11. Isn't it sufficient in your case?
There's no workaround except moving CMO to unmanaged state.

from cluster-monitoring-operator.

The startup probe delay should be 1h already in 4.11. Isn't it sufficient in your case?

At the moment, Prometheus has the following probe:

startupProbe:
  exec:
    command:
      - sh
      - '-c'
      - >-
        if [ -x "$(command -v curl)" ]; then exec curl --fail
        http://localhost:9090/-/ready; elif [ -x "$(command -v wget)"
        ]; then exec wget -q -O /dev/null
        http://localhost:9090/-/ready; else exit 1; fi
  timeoutSeconds: 3
  periodSeconds: 15
  successThreshold: 1
  failureThreshold: 60

If I am right, Prometheus will have a maximum of 60 * 15 seconds to complete its startup.

There's no workaround except moving CMO to unmanaged state.

Would that let me modify startupProbe parameters?

from cluster-monitoring-operator.

the startup probe timeout has been increased to 60m in 0bfc262 which is included in OCP 4.11.21 (https://access.redhat.com/errata/RHSA-2022:9107). If you're on OKD, I'm not sure about the corresponding version.

from cluster-monitoring-operator.

My Cluster OCP 4.11.12, that is why my parameters are so low.

Guess I'll have to give up to update probes parameters and just update my 4.11.12 Cluster to at least 4.11.21.

Thank you very much @simonpasquier

from cluster-monitoring-operator.

/close

from cluster-monitoring-operator.

@simonpasquier: Closing this issue.

from cluster-monitoring-operator.