debug-buttercup

Diagnose Kubernetes pod crash loops by running the diagnostic script to analyze pod restart patterns, inspect event warnings, and generate a full system snapshot of logs and resource usage across the crs namespace.

Redis stream consumer group lag causes fuzzer-bot queue backlogs when task processing stalls. Inspect stream lengths, consumer group lag, and task registry health using kubectl to identify and resolve the processing backlog.

Troubleshoot Kubernetes resource contention and disk saturation by inspecting pod resource limits, node capacity, and event warnings via kubectl to identify bottlenecks causing scheduler service disruptions.

You need kubectl access and standard Linux utilities to perform SRE triage on a Cyber Reasoning System Kubernetes environment, enabling log analysis, resource inspection, and stream monitoring across the cluster.

The best way to monitor Redis queue health in Kubernetes is by inspecting stream lengths and consumer group lag through a structured diagnostic framework that queries the task registry and captures real-time stream metrics.

When fuzzer-bot and scheduler services keep crashing, execute the diagnostic script to determine if the root cause is a Redis connection failure or disk saturation, then review the generated system state report.