Skip to main content
The k8s canary plants a fake kubeconfig file with the cluster server URL pointed at Snare. Any kubectl command or Kubernetes SDK call using this kubeconfig fires the callback.

What gets planted

~/.kube/staging-deploy.yaml
insecure-skip-tls-verify: true is common in real staging configs (and required here since Snare isn’t a real Kubernetes API server). The kubeconfig lives in ~/.kube/ but with a non-default filename so it doesn’t interfere with real kubeconfigs.

Trigger conditions

  • kubectl --kubeconfig ~/.kube/staging-deploy.yaml get pods
  • Any Kubernetes SDK that reads this kubeconfig
  • An agent scanning ~/.kube/ for available cluster configs

Confirmed working

Tested with kubectl v1.35.1 — alert fires with user agent:

False positive risk

Near zero — only fires if something explicitly uses this kubeconfig file or scans ~/.kube/ and attempts connections.