<p>there are two kinds of provisioner in kubernetes storageclass
one is：</p>

<blockquote>
  <p>kind: StorageClass<br>
  apiVersion: storage.k8s.io/v1<br>
  metadata:<br>
    name: hdd1<br>
  provisioner: kubernetes.io/cinder<br>
  parameters:<br>
    type: HDD1 # change for your cloud volume type<br>
    availability: nova </p>
</blockquote>

<p>and one is :</p>

<blockquote>
  <p>kind: StorageClass<br>
  apiVersion: storage.k8s.io/v1beta1<br>
  metadata:<br>
    name: cinder-standard-iops<br>
  provisioner: openstack.org/standalone-cinder<br>
  parameters:<br>
    type: standard-iops</p>
</blockquote>

<p>I'm wondering what's the difference between them,Thanks!</p>

<p><code>provisioner: kubernetes.io/cinder</code> default driver is described in <a href="https://kubernetes.io/docs/concepts/storage/storage-classes/#openstack-cinder" rel="nofollow noreferrer">official documentation.</a></p>

<p><code>provisioner: openstack.org/standalone-cinder</code> : a beta feature which was created for use with external Cinder storage.</p>

<p><a href="https://github.com/kubernetes-incubator/external-storage/issues/317" rel="nofollow noreferrer">Here</a> you can find the main discussion about adding additional provisioner toCinder-standalone.</p>

<blockquote>
  <p>The builtin kubernetes cinder support expects that nodes are deployed on nova instances. In order to use cinder as a standalone storage service I'd like to add an external provisioner. This provisioner creates volumes in cinder and retrieves connection information. It then translates this connection information into a native k8s PV (ie. iscsi or rbd are already implemented).</p>
</blockquote>
