A property-tax batch importer on OKE needs several minutes to load reference data on first boot, and liveness keeps killing it mid-load. What should the team add?
Select an answer to reveal the explanation.
Short Explanation
Startup is a soft "still unpacking" window for slow first boots. While startup is running, liveness stays out of the way; once startup succeeds, liveness and readiness take over. That stops property-tax importers from being killed mid-load.
Full Explanation
A startup probe protects long first-time initialization. Until it succeeds, liveness does not terminate the container for appearing unready. After startup passes, normal liveness and readiness probes apply. Raising maxSurge or removing probes does not solve premature liveness kills, and readiness alone does not suspend liveness during a slow boot.