Default to use mountOptions.vers=4.2

[consideRatio]

I asked @yuvipanda whom I learn a lot of NFS matters from about this:

nfs-ganesha-server-and-external-provisioner/deploy/helm/values.yaml

Lines 74 to 75 in 027c2eb

	mountOptions:
	- vers=3

Yeah, I think the default should be 4.2 since nfs-ganesha supports it, unless they have a strong reason to not do that.

---

Should we transition to suggest 4.2 by default instead?

[kvaps]

This change from NFSv4 to NFSv3 was introduced by me in helm/charts#19260

The main reason was in fact that NFSv3 is stateless protocol and works better in such dynamic environment as Kubernetes.
My tests shows that NFSv3 has faster recovery after failure and shows better performance than NFSv4.

Many vendors are using NFSv3 by default, for example Proxmox and VMWare are doing that by providing NFSv4 support just as an additional option.

More details about the differences you can read in this article:

• A brief look at the difference between NFSv3 and NFSv4

So I would put the question differently:
What are the benefits we'll get of using 4.2 over 3 by default?

[consideRatio]

Ah I wasn't aware of this complexity, and I'm also not very knowledgeable about the tradeoffs in general.

@yuvipanda could you answer what you think regarding benefits of using v4.2 over v3 by default?

[k8s-triage-robot]

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, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

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, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

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, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue.

In response to this:

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, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

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.