<p>If java/spring boot microservice A (deployed in its own container &amp; with its own Kubernetes Service of type ClusterIP) needs to send a REST request to Java/spring boot microservice B (has its own Kubernetes Service of type ClusterIP) in the same Kubernetes cluster, what's the best way for A to determine B's kubernetes service IP (especially if B is redeployed)?  Note: internal call where  B doesn't have a NodePort or LoadBalancer nor an Ingress.  </p>

Meta
<p>The right way to do this is to have a <code>Service</code> for <code>B</code>, and have <code>A</code> use the name of that service to access <code>B</code>. This way, <code>B</code> will be accessible to <code>A</code> regardless of its address.</p>
