The on-call owner at fictional Parcel Line needs its dispatch Service restored on port 8080. Retain the original routing evidence, repair its selector without changing the client port, test reachability and state the maintained configuration change.
A logistics service exists, and its application Pods are running, but the stable address has no useful backend. You'll save the Service and endpoint inventory, inspect the selector, then identify and repair the routing boundary. Creating another Service with a similar name would leave the original client address broken. Each step retains the incident evidence and the workload. The final task requires a successful local reachability probe and a checked recommendation, so a plausible written diagnosis can't pass by itself. This case isolates a selector mismatch; other incidents can have ready endpoints and still fail because the target port or a traffic policy is wrong.