Skip to content

Update alert email for compatibility-versions Prow jobs to use a rotation and update OWNERS in experiments/compatibility-versions #34269

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
aaron-prindle opened this issue Feb 5, 2025 · 1 comment
Open

Update alert email for compatibility-versions Prow jobs to use a rotation and update OWNERS in experiments/compatibility-versions #34269

aaron-prindle opened this issue Feb 5, 2025 · 1 comment
Labels
kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery.

Comments

@aaron-prindle
Copy link
Contributor

The testgrid-alert-email annotation in several compatibility-versions Prow jobs is currently configured to send alerts to an individual email address ([email protected]). This is not ideal for long-term maintainability and team ownership of these jobs. Additionally the experiments/compatibility-versions OWNERS files should be updated with this same set of people/rotation.

/sig api-machinery
@aaron-prindle aaron-prindle added the kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. label Feb 5, 2025
@k8s-ci-robot k8s-ci-robot added the sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. label Feb 5, 2025
@aaron-prindle aaron-prindle mentioned this issue Feb 5, 2025
Merged
@k8s-triage-robot
Copy link

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-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@aaron-prindle @k8s-ci-robot @k8s-triage-robot