Follow up to PR 248 for automation of google groups

[dims]

• Extract k8s-infra- prefix requested by @spiffxp
• Search for a way to constrain this to groups created solely by this service account instead of or in addition to blacklisting by name requested by @spiffxp
• Pick Authoritative model vs Opportunistic model requested by @cblecker
• Make lists settings for security customizable
• Ability to specify "owner"/"manager"/"member" for a google group

[dims]

/assign @dims

[dims]

cc @spiffxp @thockin @cblecker

[spiffxp]

ref: #228

[spiffxp]

/area access

[dims]

/unassign

[thockin]

This is now totally unassigned. Is it important? Can we throw a prio tag on it?

[dims]

/priority backlog

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[cblecker]

/remove-lifecycle rotten
/close

Everything in here is done already.

[k8s-ci-robot]

@cblecker: Closing this issue.

In response to this:

/remove-lifecycle rotten
/close

Everything in here is done already.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.