debug-buttercup

Diagnose Buttercup CRS crashes and Redis outages in Kubernetes by running the diagnose.sh script in a Bash environment with kubectl. It collects a full health snapshot across the crs namespace to guide triage, log analysis, and queue inspection for actionable fixes.

Triage cascading service failures across Buttercup pods by analyzing pod status, events, and restart patterns to identify failing components. This workflow determines whether Redis I/O, DinD storage, or queue backlogs are the root cause of tandem pod restarts.

Yes, you need kubectl to inspect Redis streams and consumer groups in the crs namespace. The diagnostic process requires a Bash environment, kubectl access, and the diagnose.sh script to collect diagnostics and monitor queue depths for bottlenecks.

Yes, you can use this triage workflow for all Buttercup components. It applies to Kubernetes deployments across infra, orchestration, fuzzing, analysis, and UI components to diagnose crashes, inspect queues, and resolve cascade failures.

This Kubernetes diagnostic process requires a Bash environment to execute the diagnose.sh script. The script automates the collection of diagnostic data across the crs namespace, which is then analyzed for failure-pattern guidance and actionable root cause identification.