Configuring the timeoutSeconds value for the livenessProbe is not possible in v1.16.0-rc2

Summary

Setting the timeoutSeconds value for the livenessProbes is not applied to the Stateful set in v1.16.0-rc2

Current Behaviour

According to the documentation, setting the timeoutSeconds value under SGcluster.spec.pods.livenessProbe.timeoutSeconds should be possible in v1.16.0-rc2.

Setting this value is not applied to the Stateful set.

Steps to reproduce

This can be reproduced by setting e.g.

apiVersion: stackgres.io/v1
kind: SGCluster
spec:
  pods:
    livenessProbe:
      timeoutSeconds: 10

When checking the Stateful set, I still get

livenessProbe:
  failureThreshold: 6
  httpGet:
    path: /controller/liveness
    port: 8080
    scheme: HTTP
  initialDelaySeconds: 20
  periodSeconds: 20
  successThreshold: 1
  timeoutSeconds: 1

Expected Behaviour

The timeoutSeconds value for the liveness Probe should reflect the 10 seconds being set in the SGcluser resource

livenessProbe:
  failureThreshold: 6
  httpGet:
    path: /controller/liveness
    port: 8080
    scheme: HTTP
  initialDelaySeconds: 20
  periodSeconds: 20
  successThreshold: 1
  timeoutSeconds: 10

Possible Solution

This is probably fixed when adding similar section to the livenessProbe like it was done for the readinessProbe here: https://gitlab.com/ongresinc/stackgres/-/blob/release-1.16.0-rc2/stackgres-k8s/src/operator/src/main/java/io/stackgres/operator/conciliation/factory/cluster/patroni/Patroni.java?ref_type=heads#L232

Environment

• StackGres version: 1.16.0-rc2

• Kubernetes version: 1.29.10

• Cloud provider or hardware configuration:

Relevant logs and/or screenshots

n/a