Fix deprecated storage class annotations

[rpanduranga]

What this PR does / why we need it:
Fix deprecated storage class annotations

Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #

Testing done:
A PR must be marked "[WIP]", if no test result is provided. A WIP PR won't be reviewed, nor merged.
The requester can determine a sufficient test, e.g. build for a cosmetic change, E2E test in a predeployed setup, etc.
For new features, new tests should be done, in addition to regression tests.
If jtest is used to trigger precheckin tests, paste the result after jtest completes and remove [WIP] in the PR subject.
The review cycle will start, only after "[WIP]" is removed from the PR subject.

Special notes for your reviewer:

Release note:

[k8s-ci-robot]

Hi @rpanduranga. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[svcbot-qecnsdp]

Started Vanilla file pre-checkin pipeline... Build Number: 566

[svcbot-qecnsdp]

Started Vanilla file pre-checkin pipeline... Build Number: 567

[svcbot-qecnsdp]

Started Vanilla file pre-checkin pipeline... Build Number: 568

[svcbot-qecnsdp]

Started Vanilla file pre-checkin pipeline... Build Number: 569

[svcbot-qecnsdp]

Started Vanilla file pre-checkin pipeline... Build Number: 570

[svcbot-qecnsdp]

Started Vanilla file pre-checkin pipeline... Build Number: 571

[svcbot-qecnsdp]

Started Vanilla file pre-checkin pipeline... Build Number: 572

[svcbot-qecnsdp]

Started Vanilla file pre-checkin pipeline... Build Number: 575

[svcbot-qecnsdp]

Started Vanilla file pre-checkin pipeline... Build Number: 576

[svcbot-qecnsdp]

Build ID: 576
File vanilla build status: FAILURE 
Stage before exit: e2e-tests 
Jenkins E2E Test Results: 
FAIL! -- 0 Passed | 2 Failed | 0 Pending | 736 Skipped
--- FAIL: TestE2E (661.42s)
FAIL

Ginkgo ran 1 suite in 12m4.207126631s

Test Suite Failed
make: Leaving directory `/home/worker/workspace/csi-file-vanilla-pre-check-in/576/vsphere-csi-driver`

[svcbot-qecnsdp]

Started Vanilla file pre-checkin pipeline... Build Number: 577

[svcbot-qecnsdp]

Build ID: 577
File vanilla build status: FAILURE 
Stage before exit: e2e-tests 
Jenkins E2E Test Results: 
FAIL! -- 0 Passed | 2 Failed | 0 Pending | 736 Skipped
--- FAIL: TestE2E (656.42s)
FAIL

Ginkgo ran 1 suite in 12m2.494010505s

Test Suite Failed
make: Leaving directory `/home/worker/workspace/csi-file-vanilla-pre-check-in/577/vsphere-csi-driver`

[svcbot-qecnsdp]

Started Vanilla file pre-checkin pipeline... Build Number: 578

[svcbot-qecnsdp]

Build ID: 578
File vanilla build status: FAILURE 
Stage before exit: e2e-tests 
Jenkins E2E Test Results: 
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 737 Skipped
--- FAIL: TestE2E (928.68s)
FAIL

Ginkgo ran 1 suite in 16m41.188444798s

Test Suite Failed
make: Leaving directory `/home/worker/workspace/csi-file-vanilla-pre-check-in/578/vsphere-csi-driver`

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: rpanduranga
Once this PR has been reviewed and has the lgtm label, please assign sashrith for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• tests/e2e/OWNERS

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

[k8s-ci-robot]

PR needs rebase.

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.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle rotten
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Reopen this PR with /reopen
• Mark this PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

[k8s-ci-robot]

@k8s-triage-robot: Closed this PR.

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Reopen this PR with /reopen
• Mark this PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

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