[WIP] BYO storageaccount docs are not entirely correct

[Copilot]

• Analyze the issue: BYO storage account docs missing NFS + private endpoint scenario
• Examine current documentation structure and examples
• Identify gaps in current documentation for BYO + NFS + private endpoints
• Create new storage class example for BYO storage account with NFS protocol and private endpoint
• Update e2e_usage.md to include the missing BYO scenario with proper parameters
• Update NFS documentation to include BYO storage account scenario
• Test the documentation changes to ensure they are correct
• Verify implementation matches exact issue requirements
• Validate YAML syntax and markdown formatting

Summary:

✅ Issue fully resolved! The BYO storage account documentation now correctly addresses the scenario for existing storage accounts with private endpoints using NFS protocol.

Key changes:

1. New storage class: storageclass-blob-nfs-existing.yaml with exact parameters from issue
2. Enhanced documentation: Clear guidance on when to use each BYO option
3. Proper parameter usage: networkEndpointType: privateEndpoint prevents service endpoint creation
4. Cloud credentials: No secrets required, uses cloud provider config instead

Files modified/created:

• 📄 deploy/example/storageclass-blob-nfs-existing.yaml (new)
• 📝 deploy/example/e2e_usage.md (updated with Option#2b)
• 📝 deploy/example/nfs/README.md (enhanced with BYO guidance)

The implementation exactly matches the parameters specified in the issue and addresses @andyzhangx's comment about needing BYO account support for NFS protocol.

Fixes #2118.

---

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.

[linux-foundation-easycla]

• ❌ The email address for the commit (367cd37) is not linked to the GitHub account, preventing the EasyCLA check. Consult this Help Article and GitHub Help to resolve. (To view the commit's email address, add .patch at the end of this PR page's URL.) For further assistance with EasyCLA, please submit a support request ticket.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Copilot

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

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

[k8s-ci-robot]

Hi @Copilot. 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.