Service selector is empty when launching timescaledb-single with one replica

[theelderbeever]

What happened? The service selector for the master node is not populated when replica count is set to 1. Seems to have something to do with not promoting a master? Manually adding selectors for role: master, app: ..., etc works however, changes to the release will remove these again.

Did you expect to see something different? The service selector should work regardless of the number of replicas provisioned.

How to reproduce it (as minimally and precisely as possible): Set replicas: 1 in the helm chart and launch. Then check the master service or try to port-forward to it. No endpoints exist.

Environment

• Which helm chart and what version are you using? timescaledb-single revision 1

• What is in your values.yaml ? replicas: 1

• Kubernetes version information:

  kubectl version

Server Version: version.Info{Major:"1", Minor:"23+", GitVersion:"v1.23.7-eks-4721010"

Tested on Microk8s 1.25 and OCI 1.23 as well

• Kubernetes cluster kind:

  EKS and Microk8s

Anything else we need to know?:

[agronholm]

Duplicate of #394?

[theelderbeever]

Looks like a partial duplicate. My bad on issue searching. That said I don't think the issue is related to the load balancer. I am running with load balancers. The replica count is what I have sourced it to.