Update driver to use csi proxy filesystem v1beta1

[jingxu97]

1 Update driver to use lastest csi proxy with filesystem v1beta1
2 Update csi-proxy vendor
3 Update psp for windows to use v1beta1 for filesystem pipe
4 update service account for windows

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:

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

NONE

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jingxu97

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

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

[jingxu97]

cc @msau42

[mattcary]

/lgtm

[mattcary]

Looks like the v1beta for filesystem isn't updated in vendor?

[jingxu97]

Looks like the v1beta for filesystem isn't updated in vendor?

my mistake. forgot to git add those files..

[jingxu97]

/test pull-gcp-compute-persistent-disk-csi-driver-e2e-windows-ltsc2019

/test pull-gcp-compute-persistent-disk-csi-driver-e2e-windows-1909

[k8s-ci-robot]

@jingxu97: The specified target(s) for /test were not found.
The following commands are available to trigger jobs:

• /test pull-gcp-compute-persistent-disk-csi-driver-e2e
• /test pull-gcp-compute-persistent-disk-csi-driver-sanity
• /test pull-gcp-compute-persistent-disk-csi-driver-unit
• /test pull-gcp-compute-persistent-disk-csi-driver-verify
• /test pull-gcp-compute-persistent-disk-csi-driver-kubernetes-integration
• /test pull-gcp-compute-persistent-disk-csi-driver-e2e-win2019
• /test pull-gcp-compute-persistent-disk-csi-driver-e2e-win1909
• /test pull-gcp-compute-persistent-disk-csi-driver-e2e-windows-1-19

Use /test all to run the following jobs:

• pull-gcp-compute-persistent-disk-csi-driver-e2e
• pull-gcp-compute-persistent-disk-csi-driver-sanity
• pull-gcp-compute-persistent-disk-csi-driver-unit
• pull-gcp-compute-persistent-disk-csi-driver-verify
• pull-gcp-compute-persistent-disk-csi-driver-kubernetes-integration

In response to this:

/test pull-gcp-compute-persistent-disk-csi-driver-e2e-windows-ltsc2019

/test pull-gcp-compute-persistent-disk-csi-driver-e2e-windows-1909

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.

[jingxu97]

/test pull-gcp-compute-persistent-disk-csi-driver-e2e-win2019
/test pull-gcp-compute-persistent-disk-csi-driver-e2e-win1909

[jingxu97]

cc @mattcary I added vendor file. PTAL. Thanks!

[mattcary]

It doesn't look like those windows e2e tests have much history? Maybe windows machines need more startup time or whatever & the timeouts are too low?

[jingxu97]

I think that's because I recently changed the test name to have version information. The tests now are broken I need to fix some multi-arch build issue.

I plan to have a separate PR to fix test issue. So could we merge this one first?

[jingxu97]

cc @mattcary @msau42 PTAL. thanks!

[mattcary]

/lgtm

Sure, sgtm

[k8s-ci-robot]

@jingxu97: The following test failed, say /retest to rerun all failed tests:

Test name	Commit	Details	Rerun command
pull-gcp-compute-persistent-disk-csi-driver-e2e-win2019	ac253f3	link	/test pull-gcp-compute-persistent-disk-csi-driver-e2e-win2019

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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. I understand the commands that are listed here.

[jingxu97]

/retest