consistent setting to container's livenessProbe/readinessProbe.timeoutSeconds

[danielzhanghl]

Overview

configurable container's livenessProbe/readinessProbe.timeoutSeconds

Right now on database pod, only database container's timeoutSeconds is configurable by patroni.syncPeriodSeconds, the other container's timeoutSeconds still set to default(1s), which may not suit for some environment.

could all that container's timeoutSeconds could be configurable? otherwise, the pod will be unstable in some environment. similar to repo-host pod, it's also need to set livenessProbe/readinessProbe.timeoutSeconds configurable.

the same logic to database container should be enough(controlled by patroni.syncPeriodSeconds setting).

thanks.

containers:

• command: ... livenessProbe: failureThreshold: 3 httpGet: path: /liveness port: 8008 scheme: HTTPS initialDelaySeconds: 3 periodSeconds: 10 successThreshold: 1 timeoutSeconds: 5 name: database ports:

  • containerPort: 5432 name: postgres protocol: TCP readinessProbe: failureThreshold: 3 httpGet: path: /readiness port: 8008 scheme: HTTPS initialDelaySeconds: 3 periodSeconds: 10 successThreshold: 1 timeoutSeconds: 5

• command: .. name: pgbackrest livenessProbe: exec: command: - pgbackrest - server-ping failureThreshold: 3 periodSeconds: 10 successThreshold: 1 timeoutSeconds: 1