Improve reconnecting behaviour

[h0jeZvgoxFepBQ2C]

See https://github.com/kubernetes-sigs/nfs-ganesha-server-and-external-provisioner/issues/34#issuecomment-1145340129 for further insights

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: h0jeZvgoxFepBQ2C To complete the pull request process, please assign jsafrane after the PR has been reviewed. You can assign the PR to them by writing /assign @jsafrane in a comment when ready.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[kvaps]

Hi @h0jeZvgoxFepBQ2C thanks for your contribution, could you also update the chart version please? https://github.com/kubernetes-sigs/nfs-ganesha-server-and-external-provisioner/blob/abfbe652e38e5a0562c70ce1af517a31a07d7c9a/charts/nfs-server-provisioner/Chart.yaml#L5

[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

[kvaps]

/remove-lifecycle stale