Create monitoring for CrashLooping Pods
During incident production#5480 (closed) the engineer was focused on the wrong source of issues simply due to the order for which troubleshooting started. Had we known Pods were in state CrashLooping, this would've triggered an entirely different set of troubleshooting steps.
Utilize this issue to determine how to appropriately alert on Pods that are stuck in a Crashlooping status. This is important for deployments, so it would be wise to alert for this in our staging environment.