Enable VolumeAttributesClass feature gate for CI runs

[travisyx]

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:

/kind api-change

/kind bug

/kind cleanup
/kind design
/kind documentation
/kind failing-test
/kind feature
/kind flake

What this PR does / why we need it:

This PR fixes an issue where the CI tests do not have the feature gate for VolumeAttributesClass set. Additionally, duplicate definitions for --supports-dynamic-iops-provisioning and --supports-dynamic-throughput-provisioning are removed now that the command line arguments are default. ControllerModifyVolume has been replaced with VolumeAttributesClass in the user guide for clarity purposes.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

NONE

[k8s-ci-robot]

Hi @travisyx. 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-sigs/prow repository.

[amacaskill]

/ok-to-test

[amacaskill]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: amacaskill, travisyx

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:

• OWNERS [amacaskill]

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

[travisyx]

/cherry-pick release-1.15

[k8s-infra-cherrypick-robot]

@travisyx: only kubernetes-sigs org members may request cherry picks. If you are already part of the org, make sure to change your membership to public. Otherwise you can still do the cherry-pick manually.

In response to this:

/cherry-pick release-1.15

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-sigs/prow repository.

[amacaskill]

/cherry-pick release-1.15

[k8s-infra-cherrypick-robot]

@amacaskill: #1838 failed to apply on top of branch "release-1.15":

Applying: Enable VolumeAttributesClass feature gate for CI runs
Using index info to reconstruct a base tree...
A	deploy/kubernetes/overlays/prow-stable-sidecar-rc-master/driver-args.yaml
M	deploy/kubernetes/overlays/prow-stable-sidecar-rc-master/kustomization.yaml
M	test/run-k8s-integration-ci.sh
Falling back to patching base and 3-way merge...
Auto-merging test/run-k8s-integration-ci.sh
CONFLICT (content): Merge conflict in test/run-k8s-integration-ci.sh
CONFLICT (rename/delete): deploy/kubernetes/overlays/prow-stable-sidecar-rc-master/driver-args.yaml deleted in Enable VolumeAttributesClass feature gate for CI runs and renamed to deploy/kubernetes/overlays/dev/driver-args.yaml in HEAD. Version HEAD of deploy/kubernetes/overlays/dev/driver-args.yaml left in tree.
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 Enable VolumeAttributesClass feature gate for CI runs

In response to this:

/cherry-pick release-1.15

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-sigs/prow repository.