Feat: Special Handling for Meta-Stage Failures

[knabben]

Description

The handbook requires special handling for meta-stage failures (Up, Down, DumpClusterLogs, etc.) which should be tagged as SIG-Infra and created in k/test-infra. Currently, signalhound treats all failures the same.

Requirements

• Detect meta-stage failures (Up, Down, DumpClusterLogs, Setup, Teardown)
• Automatically tag as SIG-Infra
• Route to kubernetes/test-infra repository
• Assign priority/critical-urgent (infra failures are critical)
• Add special handling in issue templates

Acceptance Criteria

• Meta-stage failures are detected from test names
• Meta-stage failures are automatically tagged as SIG-Infra
• Meta-stage failures are routed to k/test-infra
• Priority is set to critical-urgent
• Issue templates indicate infra failure type
• Unit tests for meta-stage detection
• Integration tests with real meta-stage failures

Implementation Notes

• Define list of meta-stages: ["Up", "Down", "DumpClusterLogs", "Setup", "Teardown"]
• Check test name for meta-stage keywords
• Override SIG, repository, and priority for meta-stage failures

[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

[k8s-triage-robot]

The Kubernetes project currently lacks enough active 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 rotten
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle rotten