Update Failures due to Readiness Probes

[carpenike]

hi,

Curious how you handle updates of NzbHydra. A recent update took a little over 2 minutes for me (JVM was doing the update, 44 seconds to start the service once done).

2019-12-19 16:35:55.050 INFO --- [ main] org.nzbhydra.NzbHydra : Started NzbHydra in 44.761 seconds (JVM running for 123.698)

However, the helm chart has readiness probes defaulting at 10 seconds with 3 failures allowed before killing the pod:

        livenessProbe:
          failureThreshold: 3
          httpGet:
            path: /
            port: http
            scheme: HTTP
          periodSeconds: 10
          successThreshold: 1
          timeoutSeconds: 1
        name: nzbhydra2
        ports:
        - containerPort: 5076
          name: http
          protocol: TCP
        readinessProbe:
          failureThreshold: 3
          httpGet:
            path: /
            port: http
            scheme: HTTP
          periodSeconds: 10
          successThreshold: 1
          timeoutSeconds: 1

[halkeye]

$ kubectl logs -n nzbhydra2 nzbhydra2-6d77589bff-9ljk9 | grep Started
2019-12-19 18:14:17.694  INFO --- [           main] org.nzbhydra.NzbHydra                    : Started NzbHydra in 6.791 seconds (JVM running for 14.201)

I apparently have also had issues with the pod restarting due to timeouts, looks like 21 times over the last 35 hours. Generally its been working so I havn't put much thought into it.