Bitnami WordPress Helm Chart Fails Liveness / Readiness Probes

The update to wordpress 5.8 has resulted in all helm deployments failing due to liveness and readiness probe failures.

  Type     Reason            Age                 From               Message
  ----     ------            ----                ----               -------
  Warning  FailedScheduling  19m                 default-scheduler  0/2 nodes are available: 2 pod has unbound immediate PersistentVolumeClaims.
  Normal   Scheduled         19m                 default-scheduler  Successfully assigned default/bigfootwa-wordpress-55555cfdcc-j642w to
  Normal   Pulling           19m                 kubelet            Pulling image ""
  Normal   Pulled            18m                 kubelet            Successfully pulled image "" in 25.121679209s
  Normal   Created           18m                 kubelet            Created container wordpress
  Normal   Started           18m                 kubelet            Started container wordpress
  Warning  Unhealthy         16m (x14 over 18m)  kubelet            Readiness probe failed: Get "": dial tcp connect: connection refused
  Warning  Unhealthy         16m (x6 over 16m)   kubelet            Liveness probe failed: Get "": dial tcp connect: connection refused
  Normal   Killing           16m                 kubelet            Container wordpress failed liveness probe, will be restarted

The problem seems to be that if the wordpressScheme is set to https, the liveness/readiness probes use http and fail to stabilize the container. I submitted a PR that was merged to fix this so that the liveness/readiness probes will use the wordpressScheme for their checks here.



, , ,




Leave a Reply

Your email address will not be published. Required fields are marked *