PodDisruptionBudgetAtLimit alert depending on the context may be actionable sometimes and may not be actionable sometimes. Let's take the scenario of maxUnavailable: 0, which means we need to have healthy pods all the time. Say, if all the replicas are running and healthy, we would still fire alert which perhaps is not actionable but maxUnavailable is 1, the alert will become actionable. So, opening this bug to track situations like this and to decide the future of this alert.

• Should have this alert in first place
• If we decide to have it, how to cope with scenarios mentioned above. Should alerts be configured based on PDB tracking or identify if PDB is wrongly configured.

Porting https://bugzilla.redhat.com/show_bug.cgi?id=1970403