[bitnami/redis] redis pod not ready

QQandWX commented 2 months ago

Name and Version

bitnami/redis

What architecture are you using?

None

What steps will reproduce the bug?

bitnami/redis chart version: latest image: bitnami/redis:7.0.5-debian-11-r7

$ kubectl get pod -n redis
NAME               READY   STATUS    RESTARTS   AGE
redis-master-0     0/1     Running   0          73s
redis-replicas-0   0/1     Running   0          73s

0/1 not ready

pod events:

Events:
  Type     Reason                  Age                    From                     Message
  ----     ------                  ----                   ----                     -------
  Normal   Scheduled               9m42s                  default-scheduler        Successfully assigned redis/redis-replicas-0 to master1
  Normal   SuccessfulAttachVolume  9m42s                  attachdetach-controller  AttachVolume.Attach succeeded for volume "pvc-27780ff9-605f-42ea-b4d2-96e231897889"
  Normal   AddedInterface          9m33s                  multus                   Add eth0 [10.233.97.224/32] from k8s-pod-network
  Normal   Pulled                  8m10s (x2 over 9m33s)  kubelet                  Container image "dockerhub.kubekey.local:7443/dupf/redis:7.0.5-debian-11-r7" already present on machine
  Normal   Created                 8m10s (x2 over 9m33s)  kubelet                  Created container redis
  Normal   Killing                 8m10s                  kubelet                  Container redis failed liveness probe, will be restarted
  Warning  Unhealthy               8m10s (x2 over 8m10s)  kubelet                  Readiness probe failed: cannot exec in a stopped state: unknown
  Warning  Unhealthy               8m8s                   kubelet                  Readiness probe errored: rpc error: code = Unknown desc = container not running (afe3b59e64fb35bc37d21c46c00d77ca2ed5078632d3c5e34bbdaa66a1fb095e)
  Normal   Started                 8m4s (x2 over 9m28s)   kubelet                  Started container redis
  Warning  Unhealthy               7m30s (x8 over 9m6s)   kubelet                  Readiness probe failed:
  Warning  Unhealthy               4m30s (x18 over 9m2s)  kubelet                  Liveness probe failed:

carrodher commented 2 months ago

You can fine-tunning the liveness and readiness probe values to configure them for your specific environment, just in case it is needed to set custom values instead of the default ones.

github-actions[bot] commented 2 months ago

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

github-actions[bot] commented 1 month ago

Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.

bitnami / charts