<p>I'm working on a project and encountered some issues. I'm still a beginner with Kubernetes and need some help regarding that.</p>
<p>The code from helm config is as follows:</p>
<pre><code>storage:
    storageClass: aws-efs
    provisioner: someCustomName
    pvc:
      logs:
      .........
</code></pre>
<p>I'm unable to figure out the <strong>provisioner part</strong> there's some custom name written instead of the usual storageclass provisioner such as <code>kubernetes.io/azure-file</code>. So, is it a custom provisioner? or it's some different concept? Please, guide me!</p>
<p>I've searched a lot but unable to get anything on this.</p>

<p>If the <a href="https://kubernetes.io/docs/concepts/storage/storage-classes/#provisioner" rel="nofollow noreferrer">provisioner</a> is prefixed with <code>kubernetes.io/</code> like <a href="https://kubernetes.io/docs/concepts/storage/storage-classes/#azure-file" rel="nofollow noreferrer">azure-file</a> it means that it is an <em>internal provisioner</em> plugin. But it is valid to use an <em>external provisioner</em> as well.</p>
<blockquote>
<p>You are not restricted to specifying the &quot;internal&quot; provisioners listed here (whose names are prefixed with &quot;kubernetes.io&quot; and shipped alongside Kubernetes). You can also run and specify external provisioners, which are independent programs that follow a <a href="https://github.com/kubernetes/community/blob/master/contributors/design-proposals/storage/volume-provisioning.md" rel="nofollow noreferrer">specification</a> defined by Kubernetes. Authors of external provisioners have full discretion over where their code lives, how the provisioner is shipped, how it needs to be run, what volume plugin it uses (including Flex), etc. The repository kubernetes-sigs/sig-storage-lib-external-provisioner houses a library for writing external provisioners that implements the bulk of the specification.</p>
</blockquote>
<p>Also see more about the <a href="https://github.com/kubernetes-sigs/aws-efs-csi-driver" rel="nofollow noreferrer">AWS EFS CSI driver</a></p>
