Service selector incorrect for single instance

[fernandezcuesta]

When we set replicas: 1 in the Dragonfly Custom Resource, it turns out that the pod is lacking the role: master label.

As a workaround, we can explicitly set that label in the CR spec, but the service selector should not require role: master label being present when replicas == 1.

[Abhra303]

Hi @fernandezcuesta, can you elaborate more? What do you mean the pod is lacking role=master? Do you mean this label is missing in the master pod?

[fernandezcuesta]

Exactly, this only happens when the number of replicas is 1, if I explicitly set the label it works. The service selects the pod with that label, so in that case we get a service with no endpoints attached even though the only (main) pod is up and running.

Either labeling the pod manually or explicitly from the Custom resource, it works as expected though.

[peterrooze]

I can confirm i'm having the same issue. Without the master label and replica: 1 the instance is not getting a svc endpoint.

kubectl -n oht-acceptatieruimte get endpoints dragonfly-audio -o wide
NAME              ENDPOINTS   AGE
dragonfly-audio   <none>      4h4m