Challenge on ,
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.
Be a networking Sherlock Holmes - find out which port a Kubernetes app uses and send a request to it.