Parks staff created an ExternalName Service pointing at an in-cluster app hostname instead of using a normal selector-based Service. What is wrong with that choice?
Select an answer to reveal the explanation.
Short Explanation
ExternalName is a DNS nickname for something outside—or at least a CNAME target—not a Pod picker. For in-cluster apps, use a selector-based Service, not a CNAME costume.
Full Explanation
An ExternalName Service publishes a CNAME to a configured external name rather than programming Pod endpoints via selectors. Using it for ordinary in-cluster workloads skips the Endpoints/dataplane model operators expect. It is not PVC-bound, not namespace-forbidden in default, and does not auto-become LoadBalancer.