Open PGPAWAN opened 1 year ago
Why we don't have below parameter in patroni yaml when we are using external ETCD endpoint.
Internal ETCD with K8 cluster.
users:
zalandos:
options:
- CREATEDB
- NOLOGIN
password: ''
kubernetes:
bypass_api_service: true
labels:
application: spilo
port: tcp://10.23.0.1:443
port_443_tcp: tcp://10.23.0.1:443
port_443_tcp_addr: 10.23.0.1
port_443_tcp_port: '443'
port_443_tcp_proto: tcp
ports:
- name: postgresql
port: 5432
role_label: spilo-role
scope_label: cluster-name
service_host: 10.23.0.1
service_port: '443'
service_port_https: '443'
use_endpoints: true
namespace: pg-pgteststage2
postgresql:
authentication:
replication:
External Etcd.
users:
zalandos:
options:
- CREATEDB
- NOLOGIN
password: ''
etcd:
host: etcd.postgres-etcd1.svc.cluster.local:2379
postgresql:
authentication:
replication:
Issue: Patroni role is showing standby_leader when trying to use external etcd and getting connection refused with Node port.
Whereas when trying to connect with K8 internal etcd, its is showing role as master and able to make external connection as well.
In case
ETCD
PRIMARY DB CLUSTER ( Kubernetes Internal DCS on data center 1 )
STANDBY CLUSTER USING S3 ( External DCS on data center 2)
Endpoint:(Endpoint not registered)
POD LABEL:
ETCD LOG:
Postgres Operator Log: