Before the main container of a municipal records API starts on OKE, the team must run a one-shot schema migration against the database. Which Pod construct should they use?
Select an answer to reveal the explanation.
Short Explanation
An init container is like a stagehand who finishes set-up and leaves before the show starts. It runs to completion first, then the main app container begins—perfect for a one-shot schema migration.
Full Explanation
Kubernetes init containers run sequentially to completion before any application container starts. That makes them the documented place for dependency waits, schema migrations, or fetching a bootstrap file. A sidecar stays running alongside the app; a CronJob schedules recurring Jobs; readiness probes should not perform heavy one-time setup. Keep the migration in an init container and leave the main container focused on serving traffic.