doc: Update examples for mount permissions setting

[m-anyac]

What type of PR is this?
/kind documentation

What this PR does / why we need it:
Add comment for mount permission
Fix installation guide

Which issue(s) this PR fixes:

Fixes #

Requirements:

• uses conventional commit messages
• includes documentation
• adds unit tests
• tested upgrade from previous version

Special notes for your reviewer:

Release note:

chore: add comment for mount permission and fix installation guide

[k8s-ci-robot]

Welcome @m-anyac!

It looks like this is your first PR to kubernetes-sigs/azurefile-csi-driver 🎉. 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-sigs/azurefile-csi-driver 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. 😃

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: m-anyac (7d952b6, 7a1c5c5)

[k8s-ci-robot]

Hi @m-anyac. Thanks for your PR.

I'm waiting for a kubernetes-sigs 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-sigs/prow repository.

[nearora-msft]

/ok-to-test

[m-anyac]

Hi Andy @andyzhangx, could I get review from you?

I think I have no permission to add a reviewer to this PR.

[andyzhangx]

@m-anyac
if you want to make more secure, then why not use 0755 ? and I don't think you need to change all examples, you only need to add a comment after 0777, e.g. 0777 # modify this permission if you want to enhance the security

[nearora-msft]

@m-anyac if you want to make more secure, then why not use 0755 ? and I don't think you need to change all examples, you only need to add a comment after 0777, e.g. 0777 # modify this permission if you want to enhance the security

@andyzhangx Isn't a customer is more likely to use the example directly, instead of modifying the example based on comments? If we want this setting to be default in the future, it makes sense to modify the examples first?

[andyzhangx]

@m-anyac if you want to make more secure, then why not use 0755 ? and I don't think you need to change all examples, you only need to add a comment after 0777, e.g. 0777 # modify this permission if you want to enhance the security

@andyzhangx Isn't a customer is more likely to use the example directly, instead of modifying the example based on comments? If we want this setting to be default in the future, it makes sense to modify the examples first?

@nearora-msft different customers want different settings, in the before, we have set as 0755 by default in the code, and then challenged by quite a lot customers since default setting won't work for them, and finally we reverted to 0777. I think we should set 0777 for general usage, and if specific customers wants to be more secure, then they could use 0775 or 0755, there is no setting applied for all customers, that's not possible.

[andyzhangx]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andyzhangx, m-anyac

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

[m-anyac]

/easycla

[m-anyac]

/retest

[k8s-ci-robot]

New changes are detected. LGTM label has been removed.

[andyzhangx]

Ubuntu apt update is down, so this failure is expected now:

7.898 Processing triggers for libc-bin (2.36-9+deb12u8) ...
7.913 Processing triggers for ca-certificates (20230311) ...
7.919 Updating certificates in /etc/ssl/certs...
8.736 0 added, 0 removed; done.
8.736 Running hooks in /etc/ca-certificates/update.d...
8.738 done.
9.091 
9.091 gzip: stdin: not in gzip format
9.092 tar: Child returned status 1
9.092 tar: Error is not recoverable: exiting now

[andyzhangx]

/retest

[k8s-ci-robot]

@m-anyac: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-azurefile-csi-driver-e2e-capz	7a1c5c5	link	true	/test pull-azurefile-csi-driver-e2e-capz
pull-azurefile-csi-driver-e2e-migration-windows	7a1c5c5	link	true	/test pull-azurefile-csi-driver-e2e-migration-windows
pull-azurefile-csi-driver-e2e-capz-windows-2022-hostprocess	7a1c5c5	link	true	/test pull-azurefile-csi-driver-e2e-capz-windows-2022-hostprocess
pull-azurefile-csi-driver-external-e2e-smb	7a1c5c5	link	true	/test pull-azurefile-csi-driver-external-e2e-smb
pull-azurefile-csi-driver-e2e-migration	7a1c5c5	link	true	/test pull-azurefile-csi-driver-e2e-migration
pull-azurefile-csi-driver-e2e-capz-windows-2019-hostprocess	7a1c5c5	link	true	/test pull-azurefile-csi-driver-e2e-capz-windows-2019-hostprocess

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