解决访问svc时svc没有绑定到未就绪的pod上——publishNotReadyAddresses

后端访问svc时svc没有绑定到pod上

问题背景： 在开发过程中遇到访问集群svc失败的问题。在后端做了pod状态判断后问题仍然存在。发现是因为后端访问svc时svc未绑定到pod上，当pod处于未就绪时，svc并不会与pod进行绑定，同时后端也在等待pod状态，当后端比svc的绑定访问更快时就会出现访问svc失败的问题。

**解决方法：**将svc spec字段中的publishNotReadyAddresses属性设置为true

 publishNotReadyAddresses <boolean>
     publishNotReadyAddresses indicates that any agent which deals with
     endpoints for this Service should disregard any indications of
     ready/not-ready. The primary use case for setting this field is for a
     StatefulSet's Headless Service to propagate SRV DNS records for its Pods
     for the purpose of peer discovery. The Kubernetes controllers that generate
     Endpoints and EndpointSlice resources for Services interpret this to mean
     that all endpoints are considered "ready" even if the Pods themselves are
     not. Agents which consume only Kubernetes generated endpoints through the
     Endpoints or EndpointSlice resources can safely assume this behavior.

该属性会使svc在pod未就绪时就与pod进行绑定。此时只需判断pod状态便可正常访问pod。