[bitnami/mongodb] metrics readiness/liveness probe

[aeber]

Name and Version

bitnami/mongodb v13.6.4

What is the problem this feature will solve?

When the amount of data in the database increases, the query to the /metrics endpoint might take longer than the specified timeout of the readiness and liveness probes (for example see: #12717)

The readiness and liveness probes currently query /metrics due to upstream changes in the mongodb-exporter v0.33.0: #11398

What is the feature you are proposing to solve the problem?

Release v0.36.0 of the mongodb-exporter added a handler for / and this version is already distributed since the bitnami/mongodb chart v13.6.3.

So it should be possible to switch back to using / for readiness and liveness probes. This should also improve stability as the readiness probe should no longer fail when the amount of data in the database increases.

What alternatives have you considered?

Increasing timeouts of readiness and liveness probes each time the amount of data in the db increases query time of /metrics over the timeout threshold.

[javsalgar]

Hi,

Thank you so much for the input. Would you like to submit a PR changing the probe?

[aeber]

Yeah sure, i just created one: #14573

[javsalgar]

Thank you so much!

[ckittelmann]

I had the same issue with timeouts. In 13.6.6 the timeout was increased to 10s by #14539 but I think to change to / is a good solution to reduce requests to /metrics which is done very often (by default every 5 seconds for liveness and readiness probes)