fix: use mkdir -p for creating subdir in mounted base-dir

[alankan-finocomp]

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:
It creates also parent directories of sub-directories under the mounted base-dir. Just like mkdir -p does.

Which issue(s) this PR fixes:

Fixes #411

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

none

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: alankan-finocomp (fb2d112)

[k8s-ci-robot]

Welcome @alankan-finocomp!

It looks like this is your first PR to kubernetes-csi/csi-driver-nfs 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-csi/csi-driver-nfs has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @alankan-finocomp. Thanks for your PR.

I'm waiting for a kubernetes-csi 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/test-infra repository.

[andyzhangx]

/ok-to-test

[andyzhangx]

/kind bug

[coveralls]

Pull Request Test Coverage Report for Build 4161914852

• 1 of 1 (100.0%) changed or added relevant line in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 77.33%

---

Totals
Change from base Build 4161821773:	0.0%
Covered Lines:	614
Relevant Lines:	794

---

💛 - Coveralls

[alankan-finocomp]

Sorry I am new to this prow tool and a bit lost about which line of the e2e-tests failed at :( Could you help me understand it?

[andyzhangx]

the test error would be fixed by #409

[andyzhangx]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: alankan-finocomp, andyzhangx

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

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

[alankan-finocomp]

@andyzhangx Thank you very much for reviewing and merging this PR promptly 🙇

May I ask if there is any upcoming release including this change please?