Connect a Local Container Registry to a kind Cluster
A local registry and a kind cluster run on the same Docker host but on separate networks. Learn how to connect them by attaching a running container to an additional Docker network.
Focused, hands-on DevOps and server-side problems with hints, feedback, and automated solution checks.
A local registry and a kind cluster run on the same Docker host but on separate networks. Learn how to connect them by attaching a running container to an additional Docker network.
A containerized application uses separate frontend and backend networks, but its database can still reach the internet. Make the backend network internal while keeping the application's access to external services.
A reverse proxy, application, and its database share one Docker network. Split the setup across two bridge networks, connecting the application to both so the proxy can reach the application but not the database.
A Docker container cannot reach a service running on the host because the firewall is blocking the connection. Learn how to troubleshoot container-to-host connectivity and allow the traffic without exposing the service to the network.
The management VPN is down, but you urgently need SSH access to a datacenter server that is still reachable through its application network. Find an alternative path to SSH using a routing trick and Linux's weak end host behavior.
On a dual-homed Linux server, a service bound to one network's IP address may still be reachable from another network. Learn how to prevent this unexpected access without disrupting legitimate connections.
A payment service subscribes to payment requests through NATS. Run the checkout team's test script as a Job in the checkout namespace, with the required settings, and make sure the payment request arrives.
Learn how to access a service bound to localhost of the Docker host from a bridge-networked container, without exposing the service to the local network or disabling network isolation.
A railway app publishes two endpoints through an Ingress, and both return 503. Find out why and make both endpoints answer again.
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?