Adjust liveness and readiness probe timout and periodseconds #184
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds custom liveness and readiness probe to prometheus container.
The prometheus restarted few times in past days and while investigating its the readiness probe failed with 503. The prometheus is slow is responding sometimes due to having more data, more scrape and more serviceMonitors. Until we find the solution to handle, Increasing the timeoutSeconds from 3(default from chart) to 6 will allow slow prometheus to respond to probe before it is considered as failure.
This PR also changes the periodSeconds from 5 to 8 so the probe doesnt start before the previous one is finished.