@DPCLARK12 Yes, using startupProbe is a good idea if your container takes time to start. Without it, the livenessProbe might kill the container too early, thinking it's stuck when it's just starting up. The startupProbe runs first and gives your app time to finish loading. Only after it succeeds do the liveness and readiness probes begin. This avoids false restarts and helps with stability. You can set it with a high failureThreshold and longer periodSeconds to give your app enough buffer. For example, if your app takes up to 5 minutes, use failureThreshold: 30 and periodSeconds: 10. This gives 300 seconds for the app to get ready. It’s helpful for apps with slow boot, like Java or data-heavy workloads.