kubernetes-admins group to help fight spam

[dims]

volunteering ✋🏾 to help cleanup spam. Deleting issues needs admin privs.

context some recent pokes to github admins for cleanup:

• https://kubernetes.slack.com/archives/C01672LSZL0/p1717176398639109
• https://kubernetes.slack.com/archives/C01672LSZL0/p1716209389720009
• https://kubernetes.slack.com/archives/C01672LSZL0/p1713264674072169
• https://kubernetes.slack.com/archives/C01672LSZL0/p1709499192141139
• https://kubernetes.slack.com/archives/C01672LSZL0/p1706446526481819

[jasonbraganza]

Considering @dims proactive yeoman work, this is a blindfolded yes

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dims, jasonbraganza

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• config/kubernetes/OWNERS [jasonbraganza]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[jasonbraganza]

/hold

will also wait for the other, more experienced folk, to weigh in

[MadhavJivrajani]

I am okay with this only if we can absolutely not come up with an alternative. I would prefer not adding admin privileges beyond the set of GH admins and required bots.

One solution that I am currently tinkering with is since the k8s-ci-robot has admin access already, a prow plugin that can recognise comments like /delete-issue and we can add in @dims as someone authorised to comment that and the k8s-ci-robot can handle the deletion for us.

[dims]

One solution that I am currently tinkering with is since the k8s-ci-robot has admin access already, a prow plugin that can recognise comments like /delete-issue and we can add in @dims as someone authorised to comment that and the k8s-ci-robot can handle the deletion for us.

works for me!