Get the orders rollout unstuck
- Certification
- ACE
- Format
- Artifact workspace
- Difficulty
- medium
- Estimated time
- 18 min
- Automated checks
- 8
SCENARIO
The orders API rollout is stuck: replacement Pods start, but traffic never reaches them. The image is known good and serves HTTP on port 8080. It reports ready at /ready only after warming its cache. The existing three-replica capacity and workload identity must survive the repair.
TASK
Repair orders.yaml so Service port 80 reaches the orders container on port 8080 named http, and traffic reaches only Pods ready at /ready.
- Keep the supplied namespace, image, workload identity, service account, and three replicas.
- The rollout must preserve all three serving replicas and allow at most one temporary
Pod.