Description of problem:
Similer to BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1924137
but with hco-operator and hco-webhook.
We manually update the initialprobe delay to 45 sec on both deployment to make the pods up and running, but after a while, the operator put back the original values ( which is normal, since the operator is managing both deployment ).
Version-Release number of selected component (if applicable): 2.6
Steps to Reproduce:
1.Change hco-operator and hco-webhook initialprobe delay from 15 to 45
hco-operator and hco-webhook initialprobe is 15, and when changed operator reset it back(expected result for the operator)
Change hco-operator and hco-webhook initialprobe to 45
Re-assigning this to the Install component. Please feel free to override this if you feel this is in error.
The current value for initialDelaySeconds is 5 seconds for both the readiness and liveness probes container so the first checks are going to be executed 5 seconds after the container has started.
failureThreshold is currently set to 1 so the first failure will restart the container and this can potentially cause an endless loop on really overloaded clusters.
I'm proposing to increase initialDelaySeconds to 10 seconds to maintain a certain responsiveness but raising failureThreshold to 3 so that the pod will not be restarted in the first 30 seconds.