Kubernetes Startup Probe Timeout
Fixed an issue where application startup could fail on health probes; probes now have a bounded 3-second timeout instead of hanging when a dependency like the database or Redis stalls.
This includes:
Bounded 3-second timeout added to health probes
Clean response returned instead of hanging when a dependency stalls
How it benefits the Merchant
This reduces the risk of application startup failures during infrastructure hiccups, improving store uptime and deployment reliability.
Potential FAQs
Q: Does this affect my storefront's normal operation?
A: No — this affects internal application startup and health-check behavior, not the customer-facing storefront.
Q: What happens now if the database or Redis is temporarily unavailable during startup?
A: The health probe returns a clean response within 3 seconds instead of hanging indefinitely.
Last updated