Default values for livenessProbe shows too much aggressive #3267
Description
Bug Report
What did you do?
Create an ansible operator with 0.18.1 with more than one Kind
What did you expect to see?
All worked fine
What did you see instead? Under which circumstances?
5m27s Warning Unhealthy pod/pricelist-operator-58c4467966-nf9wn Liveness probe failed: Get http://10.130.2.69:6789/healthz: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
When I run the operator with many kinds in the OCP the default values for the livenessProbe values shows too much aggressive.
Environment
- operator-sdk version: 0.18.1
- Kubernetes cluster kind: OCP 4.3.3
- Are you writing your operator in ansible, helm, or go? Ansible
Possible Solution
So changing the livenessProbe to this worked...
livenessProbe:
httpGet:
path: /healthz
port: 6789
scheme: HTTP
initialDelaySeconds: 10
timeoutSeconds: 5
periodSeconds: 10
successThreshold: 1
failureThreshold: 3
Additional context
Came from: #3216
PS.: Raised a new issue to make clear because many other points/issues were discussed in the original
Users that faced it and checked that the above values solve are: @christianh814 and @madorn