A payments API Pod must finish a database schema migration before the main container starts listening. Which multi-container pattern enforces that gate?
Select an answer to reveal the explanation.
Short Explanation
Init containers are the warm-up act: the headliner (your app) does not walk on stage until the warm-up finishes and exits cleanly. Perfect for “migrate first, then listen.”
Full Explanation
Init containers run to completion sequentially before application containers start. A migration init that exits successfully gates readiness of the main process. Sidecars keep running alongside the app and are the wrong tool for a one-shot prerequisite. Lifecycle hooks on Services and ambassador proxies do not provide this ordered startup gate.