Feat: Automatic Priority Label Assignment

[knabben]

Description

The Release Signal handbook defines specific priority labels (priority/critical-urgent, priority/important-soon, priority/important-longterm) based on test failure patterns and flake rates. Currently, all issues require manual priority assignment.

Requirements

• Implement priority assignment logic based on handbook criteria:
  • priority/critical-urgent: Consistently failing tests, >20% flake rate in blocking dashboards
  • priority/important-soon: >2% flake rate in blocking jobs, failures in informing jobs
  • priority/important-longterm: Lower urgency issues
• Calculate flake rates from TestGrid or Triage data
• Automatically add priority labels to generated issues
• Support manual override if needed

Acceptance Criteria

• Priority labels are automatically assigned based on failure patterns
• Flake rate calculation works for blocking and informing dashboards
• Priority labels are included in GitHub issue creation
• Priority assignment logic matches handbook criteria
• Unit tests for priority assignment logic
• Integration tests with real test data

Implementation Notes

• Calculate flake rate: flake_count / total_runs
• Check if dashboard is blocking or informing
• Consider failure count and consistency
• Default to priority/critical-urgent if uncertain (per handbook)

[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