[redis-cluster] zombie processes caused by health checks

[viceice]

Which chart:
redis-cluster v4.2.8

Describe the bug
Same issue as in #2441 getting zombie processes because of healthchecks

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Version of Helm and Kubernetes:

• Output of helm version:

(paste your output here)

• Output of kubectl version:

(paste your output here)

Additional context
Add any other context about the problem here.

[viceice]

4048359 ?        Sl     2:15 /var/lib/rancher/k3s/data/8f4b194129852507eab4a55117fc942e0688ec9a70ffdaa5911ccc6652220f76/bin/containerd-shim-runc-v2 -namespace k8s.io -id 2a5e10a7dc5f15c22433da7d65fb9
4048380 ?        Ss     0:00  \_ /pause
4048477 ?        Ssl    1:16  \_ redis-server *:6379
1693178 ?        Z      0:00      \_ [ping_readiness_] <defunct>
2805839 ?        Z      0:00      \_ [ping_readiness_] <defunct>

[FraPazGal]

Thanks for pointing this @viceice! I have created a PR to fix this that should be merged shortly.

[viceice]

I'v again strange zombie issues

image:
  registry: gcr.io
  repository: bitnami-containers/redis-cluster
  tag: 6.0.10

cluster:
  nodes: 6
  replicas: 1

redis:
  resources:
    requests:
      memory: 10Mi
    limits:
      memory: 32Mi
  tolerations:
    - key: kriese.eu/hosted
      operator: Exists
      effect: NoSchedule

persistence:
  enabled: false

existingSecretPasswordKey: password
usePasswordFile: true

existingSecret is passed via set, chart version is 4.3.1

[alemorcuq]

Thanks, @viceice. I will create a PR implementing these changes done in the past for the Redis chart in the Redis Cluster chart: #3559

[viceice]

Do i now need to set shareProcessNamespace: true to solve my issue ?

[alemorcuq]

That should do the trick.

[stale]

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]

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.