Reporting periodic jobs failures to slack channel after number of consequent failures

[MadhavJivrajani]

Original Issue: kubernetes/test-infra#32687

---

What would you like to be added:
We would like to add a Slack reporter for failed jobs to our cluster-api Slack channel. However, we are concerned about the potential for excessive notifications, as every failure would generate a message in the channel. It would be beneficial to implement a parameter similar to testgrid-num-failures-to-alert:5 for Slack reporters. Currently, this parameter only works for email notifications

Why is this needed:
To manage the frequency of Slack notifications by only sending alerts after a specified number of failures. This will reduce noise and prevent the Slack channel from becoming overwhelmed with failure messages.

[MadhavJivrajani]

/sig contributor-experience

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale