Kubernetes monitoring and alerting test

What this Scenario does

This Scenario runs four sequential resource experiments targeting your Kubernetes pods, each generating a short spike in a different resource: CPU, disk I/O, memory, and network latency. This validates that your observability stack has full visibility into Kubernetes-orchestrated workloads.

‍

Why run this Scenario?

• Verify that your monitoring tools capture pod-level and node-level resource metrics across your Kubernetes cluster.
• Detect gaps in alert coverage specific to Kubernetes workloads, including pod resource requests and limits.
• Validate that Kubernetes-native monitoring (such as metrics-server or Prometheus) is correctly configured.
• Build confidence that resource pressure in your Kubernetes environment will be detected and surfaced before it impacts application health.

‍

Expected outcome

As each experiment runs within a Kubernetes pod, your monitoring tools show corresponding spikes in CPU, disk I/O, memory usage, and packet latency with minimal delay.