Something is wrong in the probes when using dragonfly operator

[JoniJnm]

Hi,

When using a dragonfly helm chart seems like the --wait and probes are working:

script:

helm delete dragonfly-test --ignore-not-found --wait
helm upgrade --install dragonfly-test \
  oci://ghcr.io/dragonflydb/dragonfly/helm/dragonfly \
  --wait \
  --version v1.33.1
redis-cli -h "$(kubectl get services dragonfly-test -o jsonpath="{.spec.clusterIP}")" ping

output:

release "dragonfly-test" uninstalled
Release "dragonfly-test" does not exist. Installing it now.
Pulled: ghcr.io/dragonflydb/dragonfly/helm/dragonfly:v1.33.1
Digest: sha256:8d9918c0ba312350b6ce03ca5fc892fd86aba7c80e7300a28f9f4bfb4daf457a
NAME: dragonfly-test
LAST DEPLOYED: Tue Sep 23 13:17:42 2025
NAMESPACE: default
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
1. Get the application URL by running these commands:
  export POD_NAME=$(kubectl get pods --namespace default -l "app.kubernetes.io/name=dragonfly,app.kubernetes.io/instance=dragonfly-test" -o jsonpath="{.items[0].metadata.name}")
  export CONTAINER_PORT=$(kubectl get pod --namespace default $POD_NAME -o jsonpath="{.spec.containers[0].ports[0].containerPort}")
  echo "You can use redis-cli to connect against localhost:6379"
  kubectl --namespace default port-forward $POD_NAME 6379:$CONTAINER_PORT
PONG

But when using the resource and the operator the wait is not working?

Chart.yaml:

apiVersion: v2
name: dragonfly-test
appVersion: 1.0.0
version: 1.0.0

templates/dragonfly.yaml:

apiVersion: dragonflydb.io/v1alpha1
kind: Dragonfly
metadata:
  name: dragonfly-test
spec:
  image: docker.dragonflydb.io/dragonflydb/dragonfly:v1.33.1
  replicas: 1
  resources:
    requests:
      cpu: 50m
      memory: 100Mi
    limits:
      cpu: 1000m
      memory: 321Mi

script:

helm delete dragonfly-test --ignore-not-found --wait
helm upgrade dragonfly-test --install --wait .
redis-cli -h "$(kubectl get services dragonfly-test -o jsonpath="{.spec.clusterIP}")" ping

output:

release "dragonfly-test" uninstalled
Release "dragonfly-test" does not exist. Installing it now.
NAME: dragonfly-test
LAST DEPLOYED: Tue Sep 23 13:21:59 2025
NAMESPACE: default
STATUS: deployed
REVISION: 1
TEST SUITE: None
Could not connect to Redis at 10.152.183.118:6379: Connection refused

after X seconds:

$ redis-cli -h "$(kubectl get services dragonfly-test -o jsonpath="{.spec.clusterIP}")" ping
PONG

seems like the steatefulset uses the right probes but not the CDR itself? Or is this an known issue in k8s or helm related with CDRs?

I installed the operator with:

helm upgrade --install dragonfly \
  oci://ghcr.io/dragonflydb/dragonfly-operator/helm/dragonfly-operator \
  -n dragonfly-operator \
  --wait \
  --create-namespace \
  --version v1.2.1

[JoniJnm]

Maybe related with helm/helm#11717 (comment)