Cluster became ready when svc EXTERNAL-IP is still in pending state.
General
Escalation
General
Escalation
Description
As I can see user case: I use static ip and configure it in my app, for example. I check the cluster status before start to send requests to this ip. As the result I see that status is READY but requests are failed.
marukovich@Natalias-MacBook-Pro percona-xtradb-cluster-operator [main] $ kg pxc
NAME ENDPOINT STATUS PXC PROXYSQL HAPROXY AGE
cluster1 ready 3 3 75m
marukovich@Natalias-MacBook-Pro percona-xtradb-cluster-operator [main] $ kg svc
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
cluster1-haproxy LoadBalancer 10.40.10.81 <pending> 3306:31469/TCP,3309:32452/TCP,33062:30434/TCP,33060:30145/TCP 73m
cluster1-haproxy-replicas LoadBalancer 10.40.6.238 <pending> 3306:30929/TCP 73m
cluster1-pxc ClusterIP None <none> 3306/TCP,33062/TCP,33060/TCP 75m
cluster1-pxc-unready ClusterIP None <none> 3306/TCP,33062/TCP,33060/TCP 75m
kubernetes ClusterIP 10.40.0.1 <none> 443/TCP 155m
percona-xtradb-cluster-operator ClusterIP 10.40.9.48 <none> 443/TCP 142m
As I can see user case:
I use static ip and configure it in my app, for example. I check the cluster status before start to send requests to this ip. As the result I see that status is READY but requests are failed.
marukovich@Natalias-MacBook-Pro percona-xtradb-cluster-operator [main] $ kg pxc NAME ENDPOINT STATUS PXC PROXYSQL HAPROXY AGE cluster1 ready 3 3 75m marukovich@Natalias-MacBook-Pro percona-xtradb-cluster-operator [main] $ kg svc NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE cluster1-haproxy LoadBalancer 10.40.10.81 <pending> 3306:31469/TCP,3309:32452/TCP,33062:30434/TCP,33060:30145/TCP 73m cluster1-haproxy-replicas LoadBalancer 10.40.6.238 <pending> 3306:30929/TCP 73m cluster1-pxc ClusterIP None <none> 3306/TCP,33062/TCP,33060/TCP 75m cluster1-pxc-unready ClusterIP None <none> 3306/TCP,33062/TCP,33060/TCP 75m kubernetes ClusterIP 10.40.0.1 <none> 443/TCP 155m percona-xtradb-cluster-operator ClusterIP 10.40.9.48 <none> 443/TCP 142m