Kubernetes pods are discovered as a target for pod-based kubernetes attacks like Delete Pod. Kubernetes pod targets includes attributes describing their containers and other usefull attributes like the host where the pod is scheduled on.
Delete Pod
Supported Actions
Useful Templates (4 of 11)
Verify that an AppDynamics health violation alerts you when pods are not ready to accept traffic for a certain time.
Kubernetes features a readiness probe to determine whether your pod is ready to accept traffic. If it isn't becoming ready, Kubernetes tries to solve it by restarting the underlying container and hoping to achieve its readiness eventually. If this isn't working, Kubernetes will eventually back off to restart the container, and the Kubernetes resource remains non-functional.
First, check that the AppDynamics health violation responsible for tracking non-ready containers is in a non-violating state. As soon as one of the containers is crash looping, caused by the crash loop attack, the AppDynamics health violation should notify and escalate it to your on-call team.
Verify that a Datadog monitor alerts you when pods are not ready to accept traffic for a certain time.
First, check that the Datadog monitor responsible for tracking non-ready containers is in an 'okay' state. As soon as one of the containers is crash looping, caused by the crash loop attack, the Datadog monitor should alert and escalate it to your on-call team.
Verify that Dynatrace alerts you on pods not being ready to accept traffic for a certain amount of time.
First, check that Dynatrace has no problems for an entity and doesn't alert already on non-ready containers. As soon as one of the containers is crash looping, caused by the Steadybit attack crash loop, Dynatrace should detect the problem and alert to ensure your on-call team is taking action.
Verify that a Grafana alert rule alerts you when pods are not ready to accept traffic for a certain time.
First, check that the Grafana alert rule responsible for tracking non-ready containers is in an 'okay' state. As soon as one of the containers is crash looping, caused by the crash loop attack, the Grafana alert rule should fire and escalate it to your on-call team.
Get started with Steadybit, and you’ll get access to all of our features to discover the full power of Steadybit. Available for SaaS and on-prem!
No worries, our reliability experts are here to help: book a demo with them!
Target
Go back to list
