A public-health pod never starts its main app because an init container failed. Where should the administrator look first for the failure details?
Select an answer to reveal the explanation.
Short Explanation
Init runs the pre-game—if it fumbles, the app never takes the field. Grab logs from the init container itself, not just the main app that never started.
Full Explanation
Init containers must succeed before app containers start. Failures require inspecting the init container's logs via kubectl logs -c <init-name>. Main-app logs may be empty or absent, and unrelated Endpoints or StorageClass logs do not explain init failures.