Enable VAC feature gate for Kustomize deployments

[ConnorJC3]

What type of PR is this?

/kind feature

What is this PR about? / Why do we need it?

Fixes #2238

After discussion, we decided for a consistent experience and because the downsides are significant if a user attempts to use it while disabled on the sidecars, we will enable the VAC feature gate for the Kustomize deployment.

How was this change tested?

Manually tested + CI

Does this PR introduce a user-facing change?

[TODO AFTER GENERATING RELEASE NOTES: Move to "Urgent Upgrade Notes" section] Enables the `VolumeAttributesClass` by default for the Kustomize deployment. If you are deploying using the Kustomize manifests on a cluster that does not have the `VolumeAttributesClass` feature gate enabled on the control plane, you may see harmless extra failures related to the feature in the csi-provisioner and/or csi-resizer logs.

[github-actions]

Code Coverage Diff

This PR does not change the code coverage

[AndrewSirenko]

you may see harmless extra failures related to the feature in the csi-provisioner and/or csi-resizer logs

Did we confirm this in the manual test? Or should I spin up a non-VAC enabled cluster

[ConnorJC3]

Did we confirm this in the manual test? Or should I spin up a non-VAC enabled cluster

I did a super basic test but extra eyes cannot hurt.

[torredil]

/retest

[ConnorJC3]

/test

[k8s-ci-robot]

@ConnorJC3: The /test command needs one or more targets.
The following commands are available to trigger required jobs:

• /test pull-aws-ebs-csi-driver-e2e-multi-az
• /test pull-aws-ebs-csi-driver-e2e-single-az
• /test pull-aws-ebs-csi-driver-external-test
• /test pull-aws-ebs-csi-driver-external-test-eks
• /test pull-aws-ebs-csi-driver-test-e2e-external-eks-windows
• /test pull-aws-ebs-csi-driver-test-helm-chart
• /test pull-aws-ebs-csi-driver-unit
• /test pull-aws-ebs-csi-driver-verify

The following commands are available to trigger optional jobs:

• /test pull-aws-ebs-csi-driver-external-test-arm64

Use /test all to run all jobs.

In response to this:

/test

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.

[ConnorJC3]

Tested make e2e/external-kustomize locally because this PR won't run the kustomize job:

Ran 91 of 6899 Specs in 314.219 seconds
SUCCESS! -- 91 Passed | 0 Failed | 0 Pending | 6808 Skipped

[torredil]

/lgtm

[ElijahQuinones]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ElijahQuinones

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 [ElijahQuinones]

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