Change:
container.Args = []string{ "mounttest", fmt.Sprintf("--new_file_0644=%v", file), <del> fmt.Sprintf("--file_mode=%v", file), </del> } <ins> // See issue https://github.com/kubernetes/kubernetes/issues/94237 about file_mode // not working well on Windows // TODO: remove this check after issue is resolved if !framework.NodeOSDistroIs("windows") { container.Args = append(container.Args, fmt.Sprintf("--file_mode=%v", file)) } </ins> } func addSubpathVolumeContainer(container *v1.Container, volumeMount v1.VolumeMount) {

Discussion:
On a K8s Windows cluster, try to run container with agnhost image with following yaml file but failed Seems like --file_mode does not work well. Windows Server 2019
I retried the test mentioned in the issue on the latest kubernetes 1.19, but it did not reproduce. Here are my specific steps(I have a network problem and cannot access normally, so I use instead of ) the pod yaml The pod is running normally, and the directory on the windows node is successfully created ! I am more confused, can you help me see what is inconsistent with your test?
Could you try this? I copied it from one of the subPath test
What is behind this pvc, is there its yaml and the yaml corresponding to pv?
that is a pvc which points to a gce persistent disk.
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
Stale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten
Rotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-contributor-experience at . /close
Closing this issue. <detailsIn response to : Rotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . /close Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
This issue doesn't seem to be fixed yet. /reopen /remove-lifecycle rotten
Reopened this issue. <detailsIn response to : This issue doesn't seem to be fixed yet. /remove-lifecycle rotten Instructions for interacting with me using PR comments are available .

If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Mark this issue or PR as fresh with Mark this issue or PR as rotten with Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle stale [1]:
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Mark this issue or PR as fresh with Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle rotten [1]:
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Reopen this issue with Mark this issue as fresh with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /close not-planned [1]:
Closing this issue, marking it as "Not Planned". <detailsIn response to : The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closedReopen this issue with Mark this issue as fresh with Offer to help out with [Issue Triage][1] Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details