harbor-helm
harbor-helm copied to clipboard
Added control to registry for readinessProbe and livenessProbe options
My registry restarts frequently. But it is not even used yet, there are enough resources. registry CPU and memory consumes much less than what it was allocated. However, it still restarts due to livenessProbe:
Warning Unhealthy 6s kubelet Readiness probe failed: Get "http://10.246.6.157:5000/": dial tcp 10.246.6.157:5000: connect: connection refused
Warning Unhealthy 2s kubelet Liveness probe failed: Get "http://10.246.6.157:5000/": dial tcp 10.246.6.157:5000: connect: connection refused
I would like to be able to control the livenessProbe and redinessProbe options. In particular timeoutSeconds and failureThreshold.
hi, it seems the network issue in your environment, is this PR can really solve your issue?