Service defined without a selector?

[Lars Kellogg-Stedman]

I've created a postgres cluster using PGO v5.0.3. I wanted to port-forward the service to my local machine to interact directly with the database, but the command failed:

$ oc port-forward service/netbox-primary 5432:5432

error: cannot attach to *v1.Service: invalid service 'netbox-primary': Service is defined without a selector

And indeed, the service has no "selector":

$ oc get service netbox-primary -o yaml

apiVersion: v1

kind: Service

metadata:

  labels:

    postgres-operator.crunchydata.com/cluster: netbox

    postgres-operator.crunchydata.com/role: primary

  name: netbox-primary

  namespace: netbox

spec:

  clusterIP: None

  clusterIPs:

  - None

  ipFamilies:

  - IPv4

  - IPv6

  ipFamilyPolicy: RequireDualStack

  ports:

  - name: postgres

    port: 5432

    targetPort: postgres

Is that expected? The corresponding -replicas and -pods services have selectors. The -ha service does not.

[Jonathan S. Katz]

Yes, this is a property of setting up headless Services for Statefulsets.[1][2]

The PGO quickstart describes how to connect via a port-forward locally with a one-ish liner:

https://access.crunchydata.com/documentation/postgres-operator/v5/quickstart/#connect-using-a-port-forward

Thanks,

Jonathan

[1] https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#limitations

[2] https://kubernetes.io/docs/concepts/services-networking/service/#headless-services 

[Nigel Jones]

Thanks,

In the end I created  LoadBalancer service and added this crucial element to the service selector:

 postgres-operator.crunchydata.com/role=master

as it seems this is what the operator manages to label the current master pod

(A bit new to postgres deployment & this operator -- this is only for dev use in any case)