A Container in Prod Is Mining Crypto
A pod is pegging CPU running a crypto miner. A teammate wants to kubectl delete it and move on. Defend the real response.
Answer key reviewed by Branko Petric
Read first: Kubernetes RBAC and Security
Your decision
You discover a pod in your production cluster is running a crypto miner and making outbound connections to an unknown host. A teammate says just kubectl delete the pod and we are done. How do you actually respond?
The situation
Monitoring flags a pod pinning CPU. You exec in and find a crypto miner running, with steady outbound connections to an IP you do not recognize.
Context
The pod runs a public-facing service and has a mounted service account token and access to a few secrets. You do not yet know how it was compromised. A teammate wants to simply kubectl delete the pod so CPU returns to normal and the alert clears.
Related challenges
- An EKS Pod Needs AWS Access. Attach It to the Node Role?
A pod needs to read S3, and a teammate wants to add the permission to the EKS node role to unblock it. Defend the least-privilege approach.
- ArgoCD Says OutOfSync Forever. Ignore the Secret Diff and Move On?
A third-party Helm chart moved to ArgoCD now shows OutOfSync forever, resets its admin password and broke its database and agents after one sync. Defend the real fix over the shortcuts.
- Pod Stuck in CrashLoopBackOff After a Deploy
A new deploy leaves a pod in CrashLoopBackOff. A teammate wants to bump CPU and memory. Defend how you actually diagnose it.
- Service A Intermittently Cannot Reach Service B
One in twenty calls between two services fails. A teammate wants to add retries and move on. Defend how you actually find the cause.