pulp-database-svc lacks IP

Version
pulp-operator:v1.0.0-beta.5
latest Pulp images

Describe the bug
A clear and concise description of what the bug is.
The IP field is None for the pulp-database-svc

Name:              pulp-database-svc
Namespace:         pulp
Labels:            app=pulp-database
                   app.kubernetes.io/component=database
                   app.kubernetes.io/instance=pulp-database-pulp
                   app.kubernetes.io/managed-by=pulp-operator
                   app.kubernetes.io/name=pulp-database
                   app.kubernetes.io/part-of=pulp
                   pulp_cr=pulp
Annotations:       <none>
Selector:          app.kubernetes.io/component=database,app.kubernetes.io/instance=pulp-database-pulp,app.kubernetes.io/managed-by=pulp-operator,app.kubernetes.io/name=pulp-database,app.kubernetes.io/part-of=pulp,app=pulp-database,pulp_cr=pulp
Type:              ClusterIP
IP Family Policy:  SingleStack
IP Families:       IPv4
IP:                None
IPs:               None
Port:              <unset>  5432/TCP
TargetPort:        5432/TCP
Endpoints:         10.2.1.141:5432
Session Affinity:  None
Events:            <none>

When I run PostgreSQL separately, the service address is there.

kubectl -n pulp describe service external-pulp-postgresql 
Name:              external-pulp-postgresql
Namespace:         pulp
Labels:            app=external-pulp-postgresql
Annotations:       <none>
Selector:          app=external-pulp-postgresql
Type:              ClusterIP
IP Family Policy:  SingleStack
IP Families:       IPv4
IP:                10.3.251.169
IPs:               10.3.251.169
Port:              external-pulp-postgresql  5432/TCP
TargetPort:        5432/TCP
Endpoints:         10.2.3.23:5432
Session Affinity:  None
Events:            <none>

To Reproduce
Install Pulp using pulp-operator with internal database.

Expected behavior
Service would have IP address

Additional context
Attempting to use Pulp operator backup feature. Because backup lacks external database support, try to get the internal one working.

All the other pulp-operator services have CLUSTER-IP field

NAME                                                       TYPE        CLUSTER-IP     EXTERNAL-IP   PORT(S)     AGE
service/external-pulp-postgresql                           ClusterIP   10.3.251.169   <none>        5432/TCP    76d
service/external-pulp-redis                                ClusterIP   10.3.176.233   <none>        6379/TCP    71d
service/pulp-api-svc                                       ClusterIP   10.3.75.19     <none>        24817/TCP   3h4m
service/pulp-content-svc                                   ClusterIP   10.3.165.43    <none>        24816/TCP   3h4m
service/pulp-database-svc                                  ClusterIP   None           <none>        5432/TCP    3h4m
service/pulp-operator-controller-manager-metrics-service   ClusterIP   10.3.104.118   <none>        8443/TCP    85d
service/pulp-web-svc                                       ClusterIP   10.3.36.163    <none>        24880/TCP   3h4m

Reproduce the installation with pulp-operator:v1.0.0-beta.5 and an internal database, then inspect how the pulp-database-svc service is created. Compare its configuration with the external-pulp-postgresql service and the other Pulp services; done means pulp-database-svc reports a ClusterIP instead of None while still exposing PostgreSQL on port 5432.