advancedSpring Boot on Kubernetes: Health Probes, Config, Scaling & Observability

What is the purpose of a startup probe vs a liveness probe?

The liveness probe runs throughout the Pod's lifetime to detect hangs and trigger restarts. The startup probe runs only during startup and gives the application time to initialize. Without a startup probe, the liveness probe's timeout applies from the first second, killing newly started Pods before they finish JVM warm-up, data loading, or connection pool establishment.

Ready to master this question?

Generate a complete walkthrough — background, the full answer in plain language, a working code example explained line by line, a real-world scenario, common mistakes, and how this same question gets asked in different ways.

Sign in to generate a response

Next Step

Continue to How does server.shutdown: graceful work in Kubernetes?← Back to all Kubernetes questions