Sunsetting Kubernetes SIG service accounts

[Ihor Dvoretskyi]

Hello everyone,

As a result of discussions within the SIG-ContribX, we’ve decided to sunset the GitHub Service accounts previously used by the SIG’s for diversifying the discussion topics and GitHub notifications. We’ve found the existing procedure too complicated.

Instructions on using the SIG Service accounts during the process of creating a new SIG have already been removed from GitHub [1], now we would like to clean up GitHub from the bot accounts that have been created with the purpose, described above.

If you are an owner of the credentials for `k8s-mirror-foo-*` GitHub users, listed here[2], please, work on deleting a GitHub account of the user.

Also, if the `kubernetes-sig-foo-*` mailing lists (except the `kubernetes-sig-foo` and `kubernetes-sig-foo-leads` lists, which are mandatory for every SIG) are not actively used by the SIG, please delete the ML as well.

Thanks,
Ihor

PS. The umbrella issue - https://github.com/kubernetes/community/issues/2324 

1. https://github.com/kubernetes/community/commit/62beba8bda62306788786cb1c2704878b2e1b14c#diff-71b276bd7a0a5bfb7b75af76a0ca20d1 

2. https://github.com/kubernetes/community/issues/2324#issue-336333976 

[Aaron Crickenberger]

Additionally, I've gone ahead and removed the google group links for each of these accounts from SIG READMEs

https://github.com/kubernetes/community/pull/2500

- aaron