During a municipal release, the CD must ship a new image tag for the DNA health API consumer without breaking callers that already use the stable ClusterIP name. What should change?
Select an answer to reveal the explanation.
Short Explanation
Swap the truck’s cargo; keep the street address on the building. The Deployment rolls the new tag; the Service name stays the front door other hops already call.
Full Explanation
Integration means the Kubernetes Deployment or equivalent workload points at the new image tag while the Service—stable name and ClusterIP—remains the address other hops already call. Recreating a new Service name on every release breaks the prebuilt path. Underlay HSRP or host-network detours are outside this CD integration skill.