Identify the Source of Unexpected Requests in a Kubernetes Cluster
An internal service started receiving requests from unexpected IP addresses. Identify the unexpected sources and find out which workloads and teams are behind them.
Focused, hands-on DevOps and server-side problems with hints, feedback, and automated solution checks.
An internal service started receiving requests from unexpected IP addresses. Identify the unexpected sources and find out which workloads and teams are behind them.
The production Kubernetes cluster lives inside a private VPC, and its API server has no public endpoint. Turn an SSH connection to the bastion host into a SOCKS proxy and teach kubectl to use it, so the cluster becomes manageable from your workstation.
A Deployment is running in the platform namespace with 3 replicas. Each pod has configuration files at /app/config/. Copy those files to /home/laborant/config/ on the local machine.
A Pod runs NGINX behind a NodePort Service. Copy an HTML page from dev-machine into the running Pod so NGINX serves it as the default page, without changing the Pod or the Service.
Identify and fix deprecated API versions in a Kubernetes manifest using the kubectl-convert plugin, then deploy the updated manifest.
Practice configuring Kubernetes to pull images from a private registry and run Pods with authenticated registry access.
Practice the fundamental lifecycle of a Kubernetes Pod: creation, inspection (IP, node), interaction (executing commands, checking logs), and deletion.
An ultimate Kubernetes troubleshooting challenge: can you copy files to/from a running Pod that doesn't have a shell or other command line tools installed?
Practice copying files to/from running Kubernetes Pods to become a Kubernetes troubleshooting ninja.
Can you edit a file in a running Kubernetes pod? What if there is no shell inside and the container's user lacks the write permission?