Audit Default Admission Controllers for Storage

[saad-ali]

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind bug

/kind feature

What happened:
PR #58684 adds a set of Admission Controllers that are on by default.

What you expected to happen:
We should make sure that list of controllers makes sense for storage.

Storage controllers include:

• persistentvolumelabel
• defaultstorageclass
• storageprotection
• volumeresize

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

• Kubernetes version (use kubectl version):
• Cloud provider or hardware configuration:
• OS (e.g. from /etc/os-release):
• Kernel (e.g. uname -a):
• Install tools:
• Others:

[hzxuzhonghu]

We should make sure that list of controllers makes sense for storage.

What do you mean by this?

[gnufied]

I think @saad-ali meant that we should audit and make sure that features which are enabled by default and depend on certain admission controller, also have the required admission controller enabled by default.

For example - We are moving volume expansion to beta in 1.11 (#64288 ) and hence resize admission controller should be enabled by default.

[saad-ali]

Basically ensure that the correct set of storage admission controllers are enabled.

[hzxuzhonghu]

Yes, I think we can make it default enabled once beta.

[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.