Why doesn't MetalLB publish a PostgreSQL port to node IPs on Kubernetes (Bare Metal)?

Question

Kubernetes

I install metallb

kubectl apply -f https://raw.githubusercontent.com/google/metallb/v0.7.3/manifests/metallb.yaml

Installing stolon

helm install --name stable-stolon stable/stolon --set persistence.storageClassName=local-storage,superuserPassword=password,replicationPassword=password

Getting the IP of the network card of the Kubernetes node

ip a | grep eth0
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    inet 10.233.60.149/24 brd 10.233.60.255 scope global dynamic eth0

I create a MetalLB configuration file metallb.yaml

apiVersion: v1
kind: ConfigMap
metadata:
  namespace: metallb-system
  name: config
data:
  config: |
    address-pools:
    - name: default
      protocol: layer2
      addresses:
      - 10.233.60.149

I create the MetalLB configuration file
kubectl create -f metallb.yaml
kubectl describe service stable-stolon-proxy

kubectl describe service  stable-stolon-proxy
Name:              stable-stolon-proxy
Namespace:         default
Labels:            app=stolon
                   chart=stolon-0.4.2
                   heritage=Tiller
                   release=stable-stolon
Annotations:       <none>
Selector:          app=stolon,component=stolon-proxy,release=stable-stolon
Type:              ClusterIP
IP:                10.233.60.119
Port:              proxy  5432/TCP
TargetPort:        5432/TCP
Endpoints:         10.233.104.137:5432,10.233.85.7:5432
Session Affinity:  None
Events:            <none>

expose deployment stable-stolon-proxy
kubectl expose deployment stable-stolon-proxy --type=LoadBalancer --name=stable-stolon-proxy
kubectl describe deployment stable-stolon-proxy

Name:                   stable-stolon-proxy
Namespace:              default
CreationTimestamp:      Sun, 21 Oct 2018 15:39:30 +0300
Labels:                 app=stolon
                        chart=stolon-0.4.2
                        heritage=Tiller
                        release=stable-stolon
Annotations:            deployment.kubernetes.io/revision: 1
Selector:               app=stolon,component=stolon-proxy,release=stable-stolon
Replicas:               2 desired | 2 updated | 2 total | 2 available | 0 unavailable
StrategyType:           RollingUpdate
MinReadySeconds:        0
RollingUpdateStrategy:  25% max unavailable, 25% max surge
Pod Template:
  Labels:           app=stolon
                    component=stolon-proxy
                    release=stable-stolon
                    stolon-cluster=stable-stolon
  Service Account:  stable-stolon
  Containers:
   stolon:
    Image:       sorintlab/stolon:v0.11.0-pg10
    Ports:       8080/TCP, 5432/TCP
    Host Ports:  0/TCP, 0/TCP
    Command:
      /bin/bash
      -ec
      exec gosu stolon stolon-proxy
      
    Readiness:  tcp-socket :5432 delay=10s timeout=5s period=10s #success=1 #failure=3
    Environment:
      POD_NAME:                         (v1:metadata.name)
      STPROXY_CLUSTER_NAME:            stable-stolon
      STPROXY_STORE_BACKEND:           kubernetes
      STPROXY_KUBE_RESOURCE_KIND:      configmap
      STPROXY_LISTEN_ADDRESS:          0.0.0.0
      STPROXY_METRICS_LISTEN_ADDRESS:  0.0.0.0:8080
      STPROXY_DEBUG:                   false
    Mounts:                            <none>
  Volumes:                             <none>
Conditions:
  Type           Status  Reason
  ----           ------  ------
  Available      True    MinimumReplicasAvailable
  Progressing    True    NewReplicaSetAvailable
OldReplicaSets:  <none>
NewReplicaSet:   stable-stolon-proxy-9b8c655c6 (2/2 replicas created)
Events:          <none>

telnet 10.233.60.149 5432

Trying 10.233.60.149...
telnet: connect to address 10.233.60.149: Connection refused