Allow for shares to be provisioned manually - Allow for reusable shares

[mhaddon]

This is a WIP, I am mostly interested to see if anyone is interested in this, because if there is a desire I will tidy up the code.
Consider this a draft and a PoC.

Basically you can define nfs exports from the helm chart, like this:

        nfsExports:
          - path: /kaniko-build-nfs
            squash: no_root_squash

This allows you to define the pv/pvc like this:

apiVersion: v1
kind: PersistentVolume
metadata:
  name: kaniko-build-nfs
spec:
  storageClassName: ci-nfs
  capacity:
    storage: 60Gi
  accessModes:
    - ReadWriteMany
  claimRef:
    apiVersion: v1
    kind: PersistentVolumeClaim
    namespace: ci
    name: kaniko-build-nfs
  mountOptions:
    - rw
    - hard
    - vers=3
    - noatime
    - nodiratime
    - sync
    - intr
    - rsize=32768
    - wsize=32768
    - retrans=2
    - timeo=30
  nfs:
    path: /export/kaniko-build-nfs
    server: ci-nfs-nfs-server-provisioner.ci.svc.cluster.local
  persistentVolumeReclaimPolicy: Delete
  volumeMode: Filesystem
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: kaniko-build-nfs
  namespace: ci
spec:
  storageClassName: ci-nfs
  accessModes:
    - ReadWriteMany
  resources:
    requests:
      storage: 60Gi
  volumeMode: Filesystem
  volumeName: kaniko-build-nfs

Which means you can provision your NFS shares with gitops or whatever, and also keep a predictable export path for rebuilds and what have you.

[linux-foundation-easycla]

• ❌ - login: @mhaddon / name: Michael Haddon . The commit (d4d5062, b0ff11a, c78241f, ea6ec20) is not authorized under a signed CLA. Please click here to be authorized. 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: mhaddon
Once this PR has been reviewed and has the lgtm label, please assign wongma7 for approval. For more information see the Kubernetes Code Review Process.

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

[k8s-ci-robot]

Welcome @mhaddon!

It looks like this is your first PR to kubernetes-sigs/nfs-ganesha-server-and-external-provisioner 🎉. 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/nfs-ganesha-server-and-external-provisioner 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-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages 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 PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this 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 PRs.

This bot triages 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 PR is closed

You can:

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

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

/lifecycle rotten