Create aggregated ClusterRole for API Servers to allow getting Namespaces and Admission Webhooks

[xmudrii]

I'm moving discussion from #65206 (comment) to this issue.

We think it would be a good idea to provide the aggregated ClusterRole, allowing the aggregated API servers to get, list and watch Namespaces and Admission Webhooks. This role is generic for all API servers, and we're already using this pattern for the auth delegator.

In this case, the API server operator would only have to create the appropriate ClusterRoleBinding, such as this one (example from sample-apiserver), compared to creating both the ClusterRole and the ClusterRoleBinding.

In #65206, we have added an example manifest to the sample-apiserver repo, but as described above and as this is a generic role for all API servers, maybe we can make Kubernetes handle it.

Without that role, the API server fails to start with the permissions errors (see #65206 for details).

I would like to take on this issue if this sounds okay.

/cc @deads2k @sttts @kubernetes/sig-auth-misc
/sig api-machinery
/sig auth
/kind feature

[k8s-ci-robot]

@xmudrii: Reiterating the mentions to trigger a notification:
@kubernetes/sig-auth-misc

In response to this:

I'm moving discussion from #65206 (comment) to this issue.

We think it would be a good idea to provide the aggregated ClusterRole, allowing the aggregated API servers to get, list and watch Namespaces and Admission Webhooks. This role is generic for all API servers, and we're already using this pattern for the auth delegator.

In this case, the API server operator would only have to create the appropriate ClusterRoleBinding, such as this one (example from sample-apiserver), compared to creating both the ClusterRole and the ClusterRoleBinding.

In #65206, we have added an example manifest to the sample-apiserver repo, but as described above and as this is a generic role for all API servers, maybe we can make Kubernetes handle it.

Without that role, the API server fails to start with the permissions errors (see #65206 for details).

/cc @deads2k @sttts @kubernetes/sig-auth-misc
/sig api-machinery
/sig auth
/kind feature

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.

[fedebongio]

/cc @cheftako

[sttts]

+1 we should do that. Otherwise, aggregated API server builders will ship those roles. Not sure we want that from a security point of view.

[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

[nikhita]

/remove-lifecycle stale

[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

[xmudrii]

/remove-lifecycle stale

[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

[xmudrii]

/remove-lifecycle stale

[enj]

/priority important-longterm

[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

[xmudrii]

/remove-lifecycle rotten

[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

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

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

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

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

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.