A permits desk app must talk to a legacy database that runs outside…

Question

A permits desk app must talk to a legacy database that runs outside the cluster at a fixed IP. Which Service approach maps a stable in-cluster DNS name to that external backend?

Accepted Answer

Create a selector-less Service and a matching Endpoints (or EndpointSlice) object that lists the external database IP and port. — When the backend is not a Pod, you hand-wire the address book. A Service with no selector plus a manual Endpoints (or EndpointSlice) entry points cluster DNS at that external DB IP. Selectors alone cannot invent Pods that do not exist.

Answer

Create a ClusterIP Service with a selector matching nonexistent Pod labels and hope DNS invents the IP.

Answer

Use only a NodePort Service without Endpoints so kube-proxy invents an external route.

Answer

Expose the database with an Ingress path and skip Service and Endpoints objects entirely.

A permits desk app must talk to a legacy database that runs outside the cluster at a fixed IP. Which Service approach maps a stable in-cluster DNS name to that external backend?

Short Explanation

Full Explanation