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.
An nginx Deployment runs fine, but its address returns an error. Trace the path from the Ingress to the Pod and fix the manifests.
You are containerizing the dev workflows of a legacy Python service and you need to find out which external services its test suite talks to. Can you think of an easy way to do it?
Ad-hoc containers are a handy way to run command-line tools without installing them on the host. Use one to access a production Redis server and turn off a feature flag. But beware of the gotcha: the production server can only be tunneled to the localhost.
Explore the container networks of a freshly installed Docker host: find the default network, its subnet and gateway, and the Linux interface behind it.
Can you get several builds of an app running side by side without port conflicts, so you can test them simultaneously?
A common setup for small deployments: two servers (VM or bare-metal), each with a public and a private IP. The app listens on the public port but wants to talk to Redis over the private network. Can you set it up?
Practice accessing a containerized service directly from the Docker host using its IP address.
Learn how to keep a database available to an app running on your workstation without exposing its port to other machines on the network.
The storefront APIs are served through a Traefik Ingress with TLS and two path rules. Reproduce that configuration with a Gateway and an HTTPRoute on the same hostname, cut traffic over to it, and retire the Ingress.