From: Dana Okafor, engineering lead, Brightwell Bakery
"Our new orders API goes live on Monday and the cluster is ready for it. Please set it up in its own namespace with its settings and database credentials, health checks and a stable name, prove it answers, ship the 2.4.1 fix without dropping below two Pods, and hand it to the checkout team.
The image is registry.example.com/bakery/orders-api; 2.3.1 is the audited launch build. Don't paste the database password into any manifest."
Done when: the API runs two healthy Pods behind its Service on 2.4.1, the smoke test and rollout history are saved under evidence/, and the Deployment names its owner.
Eight steps in one cluster, each building on the last: settings and credentials, the Deployment, health checks, a Service, a smoke test, a release without downtime and a handover. Every step keeps your earlier work; if a later change breaks an earlier result, the checker says which.
The first three moves of the launch.