Query: Could you please explain "cluster1-proxysql-unready" .

I am very new for mysqI and operator stuff.
I have installed pxc operator on local kubernetes environment.I can see all pods are up and running. 

# k get  pods  NAME                                               READY   STATUS    RESTARTS   AGEcluster1-proxysql-0                                3/3     Running   0          10mcluster1-proxysql-1                                3/3     Running   0          10mcluster1-proxysql-2                                3/3     Running   0          10mcluster1-pxc-0                                     1/1     Running   0          10mcluster1-pxc-1                                     1/1     Running   0          8m58scluster1-pxc-2                                     1/1     Running   0          8m10spercona-xtradb-cluster-operator-55c54448b6-9pxfg   1/1     Running   0          11m
====================================================
k get svc  NAME                        TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)             AGEcluster1-proxysql           ClusterIP   10.98.167.128   <none>        3306/TCP            11mcluster1-proxysql-unready   ClusterIP   None            <none>        3306/TCP,6032/TCP   11mcluster1-pxc                ClusterIP   None            <none>        3306/TCP            11mcluster1-pxc-unready        ClusterIP   None            <none>        3306/TCP            11m
=======================================================

Could you please elaborate about Service  cluster1-proxysql-unready and cluster1-pxc-unready. 
It is used for failover?  if we face  any  issue during opeartion?





Hi
Thank you for your question.
‘unready’ service is needed for pod address discovery during the application startup regardless the pod state. Proxysql and pxc pods should know about each other before the database become fully operational. The unready service has no public IP address assigned and is unavailable outside the cluster.
Such a behavior governs by service.alpha.kubernetes.io/tolerate-unready-endpoints: ‘true’ annotation. 

Thanks @IvanPylypenko for explaining