Expose liveness & readiness probe parameters in the helm chart #2265

➹ New Feature implementation request

Is your feature request related to a problem?

As a secureCodeBox user i experience occasional restarts of the SecureCodeBox operator pod.

These restarts are caused by a failing readiness probe.

I0203 05:19:12.412872 1934 prober.go:121] "Probe failed" probeType="Readiness" pod="securecodebox/securecodebox-controller-manager-68c5b6c946-s4tgg" podUID=b5e51497-99ae-4217-ac85-1aaa8bcbad4f containerName="manager" probeResult=failure output="Get \"http://10.8.0.118:8081/readyz\": dial tcp 10.8.0.118:8081: connect: connection refused"

The readiness probe fails three times in a row and the pod is killed by Kubernetes.

I don't see a particular reason for these fails, except for expected load. In the most cases I can think of restarting the pod probably won't fix the load.

I would love to gain more control over the probes to test if these restarts can be reduced by increasing the timeout or failurethreshold values.

Describe the solution you'd like

Expose the following liveness and readiness fields to the user via helm variables:

• path
• port
• failureThreshold
• successThreshold
• initialDelaySeconds
• periodSeconds
• timeoutSeconds

Describe alternatives you've considered

N/A

Additional context

N/A