Closed ahjing99 closed 1 year ago
It's not a network issue, the service mysql-ndllsk-mysql
doesn't match with any endpoints. Please check the service selector and the health status of pods.
kg svc
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
kubebench-exporter ClusterIP None <none> 9187/TCP 114m
kubernetes ClusterIP 10.24.0.1 <none> 443/TCP 3h47m
mysql-ndllsk-mysql ClusterIP 10.24.15.91 <none> 3306/TCP 87m
mysql-ndllsk-mysql-headless ClusterIP None <none> 3306/TCP,9104/TCP,3501/TCP,50001/TCP 87m
mysql-tlyubr-mysql ClusterIP 10.24.9.30 <none> 3306/TCP 39m
mysql-tlyubr-mysql-headless ClusterIP None <none> 3306/TCP,9104/TCP,3501/TCP,50001/TCP 39m
kg ep
NAME ENDPOINTS AGE
kubebench-exporter 10.20.0.28:9187,10.20.1.16:9187,10.20.2.15:9187 115m
kubernetes 10.128.0.24:443 3h48m
mysql-ndllsk-mysql <none> 88m
mysql-ndllsk-mysql-headless 10.20.0.25:3501,10.20.0.25:3306,10.20.0.25:50001 + 1 more... 88m
mysql-tlyubr-mysql <none> 40m
mysql-tlyubr-mysql-headless 10.20.1.20:3501,10.20.2.14:3501,10.20.1.20:3306 + 5 more... 40m
➜ ~ kbcli version Kubernetes: v1.27.3-gke.100 KubeBlocks: 0.7.0-alpha.13 kbcli: 0.7.0-alpha.13