Open ConnorJC3 opened 1 day ago
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: Once this PR has been reviewed and has the lgtm label, please ask for approval from connorjc3. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.
This PR does not change the code coverage
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
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.
/retest
/test
@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.
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
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?