dragonfly-operator-test-connection pod has bad address and fails

[urbaman]

Hi,

Just installed in dragonfly-db with default values, it creates a dragonfly-operator-test-connection pod in the defualt namespace trying to connect to the operator, but it has a wrong address.

Resources in dragonfly-db namespace:

$ kubectl get all -n dragonfly-db
NAME                                                   READY   STATUS    RESTARTS   AGE
pod/dragonfly-db-dragonfly-operator-6886d56867-4v8lx   2/2     Running   0          58s

NAME                                                     TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)             AGE
service/dragonfly-db-dragonfly-operator-controller-svc   ClusterIP   10.110.216.23   <none>        8443/TCP,8080/TCP   58s

NAME                                              READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/dragonfly-db-dragonfly-operator   1/1     1            1           58s

NAME                                                         DESIRED   CURRENT   READY   AGE
replicaset.apps/dragonfly-db-dragonfly-operator-6886d56867   1         1         1       58s

dragonfly-operator-test-connection pod logs:

$ kubectl logs dragonfly-db-dragonfly-operator-test-connection
wget: bad address 'dragonfly-db-dragonfly-operator:8443'

[Abhra303]

can you share more info? I don't see dragonfly-db-dragonfly-operator-test-connection pod in the list. Can you share the config yaml you used and also the operator logs?

Also share instructions to reproduce it locally.

[urbaman]

Hi,

I'm looking at this test pod here, actually run by the helm install if I remember right (it refers to helm values): https://github.com/dragonflydb/dragonfly-operator/blob/main/charts/dragonfly-operator/templates/tests/test-connection.yaml

[urbaman]

Trying to ne a little more on point: if I helm install the Operator in a specific namespace, the test pod non being namespaces gets deployed in the default namespace.
At this point, the wget url in the test command is wrong, not having the namespace pointing to the Operator.

My opinion is, if the test pod is actually needed, to make it namespaced as the rest of the helm deployment and/or adding the namespace to the wget command, depending on the kind of test to make.

[Abhra303]

The test config already has namespace: {{ include "dragonfly-operator.namespace" . }} in the namespace field. I am not sure how it can be created in a different namespace.

[Abhra303]

I think you didn't have the latest helm chart. This is the fix that were merged #420.