Troubleshoot an Ingress That Returns 503 Service Unavailable
A railway app publishes two endpoints through an Ingress, and both return 503. Find out why and make both endpoints answer again.
Focused, hands-on DevOps and server-side problems with hints, feedback, and automated solution checks.
A railway app publishes two endpoints through an Ingress, and both return 503. Find out why and make both endpoints answer again.
A new intern learning about probes wrote a small Pod manifest. The exec command and the application are both correct, but the Pod never becomes Ready because one probe parameter is missing. Find it and add it.
A webapp deployment in the prod namespace is stuck in CrashLoopBackOff. The application's startup probe checks that its existing config directory is intact before the container is marked healthy. Fix the deployment so configuration is injected correctly and the pod reaches Running state with its health check endpoint responding on port 8080.
A deployment is running without health probes or graceful shutdown configuration. Add startup, liveness, and readiness probes plus a preStop hook and terminationGracePeriodSeconds to make it ready for real traffic.
Add HTTP-based liveness and readiness probes to an existing Kubernetes Deployment and verify application health and availability.