Question

A backend team runs three Pods created by a Deployment. Frontend Pods in the same cluster need to reach the backend reliably, but the backend Pods are frequently rescheduled, so their IP addresses keep changing. The team does not want to expose the backend outside the cluster. Which approach provides a stable internal address for the frontend to use?

Accepted Answer

Create a ClusterIP Service that selects the backend Pods, and have the frontend connect to the Service name

Answer

Configure the frontend to connect directly to each backend Pod IP listed in the Deployment status

Answer

Create a NodePort Service so the frontend can reach the backend through the node's external port

Answer

Hard-code the backend ReplicaSet name in the frontend configuration so it always resolves the Pods