Remove some unneeded teams

[cblecker]

• Remove @kubernetes/examples-reviewers: it contains one person, that person is already a maintainer, and it doesn't provide any permissions.
• Remove @kubernetes/kubernetes-reviewers: team provides no additional access, and isn't useful for mentioning.
• Remove @kubernetes/kubernetes-admins: All members of this group still have write access via kubernetes-maintainers, and admin access shouldn't be needed -- releases are cut by kubernetes-release-managers.

/cc @kubernetes/owners
/hold

[nikhita]

/lgtm

[justaugustus]

/lgtm
/approve

[idvoretskyi]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cblecker, idvoretskyi, justaugustus, nikhita

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 [cblecker,idvoretskyi,nikhita]

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

[spiffxp]

/lgtm

[idvoretskyi]

@cblecker anything that blocks us from merging?

[cblecker]

/hold cancel

[lavalamp]

This locked me out of merging to the rate-limiting feature branch.

[cblecker]

@lavalamp Do tests not pass on that branch?

[lavalamp]

They pass at the moment. The issue is kubernetes/test-infra#12303 effectively prevents merging master back into the branch.

[cblecker]

Ohhhh, okay I get it. Working on solution..

[lavalamp]

The solution we have at the moment is kubernetes/kubernetes#77652 but that prevents merging the feature branch back into master...

Also, I think there's no way now to create feature branches?

[lavalamp]

(previously I just did that)

[cblecker]

@lavalamp I just opened #804 to create a group to delegate this permission to you. We should figure out better solutions to these, but I don't want to block active work.

[lavalamp]

Thanks!