A library catalog frontend must call the search backend on OKE, but search Pod IPs change whenever replicas restart. What orchestration concern gives callers a stable name that tracks currently healthy replicas?
Select an answer to reveal the explanation.
Short Explanation
Replica IPs are revolving doors; a service name is the lobby directory. Callers use that stable name while the orchestrator keeps the healthy-member list current. Hard-coded Pod IPs go stale the moment a replica moves.
Full Explanation
Orchestration provides service discovery so clients address a stable logical name rather than ephemeral Pod IPs. The service abstraction maintains endpoints for currently ready replicas. Baking IPs into images or spreadsheets recreates the anti-pattern orchestration exists to remove. NodePort exposure is a different networking concern and still should not rely on fixed replica IPs in app config.