Alert Slack on Kubernetes pod status changes
Build a workflow that polls the Kubernetes API (or consumes events) for pod status changes in target namespaces. On meaningful transitions (e.g., CrashLoopBackOff, Failed, restarts), post a Slack message with pod, namespace, reason, and recent events. Track last-seen states to avoid duplicate alerts, filter noise from normal scheduling, and handle API auth/errors. Output the status changes detected and alerts sent.
What this prompt builds
Post to Slack whenever Kubernetes pods change state so teams catch deploys and crashes fast.
The problem
Pod crashes, restarts, and failed rollouts can go unnoticed until users complain, because watching kubectl isn't a monitoring strategy. Teams need pod-state changes pushed to where they work.
Solution and impact
This workflow watches Kubernetes pod status changes and posts them to Slack, surfacing deployments, restarts, and errors in real time. Engineers see problems as they happen and respond before impact spreads.