<match value="conectix" type="string" offset="0"/>
    </magic>
  </mime-type>

  <mime-type type="application/x-vmdk">
    <acronym>VMDK</acronym>
    <_comment>Virtual Disk Format</_comment>
    <tika:link>http://en.wikipedia.org/wiki/VMDK</tika:link>
    <glob pattern="*.vmdk"/>
  </mime-type>

  <mime-type type="application/x-wais-source">
    <glob pattern="*.src"/>
  </mime-type>

* Fix for detach volume when node is not present/ powered off ([#40118](https://github.com/kubernetes/kubernetes/pull/40118), [@BaluDontu](https://github.com/BaluDontu))
* Adding vmdk file extension for vmDiskPath in vsphere DeleteVolume ([#40538](https://github.com/kubernetes/kubernetes/pull/40538), [@divyenpatel](https://github.com/divyenpatel))

  // +optional
  optional EphemeralVolumeSource ephemeral = 29;
}

// Represents a vSphere volume resource.
message VsphereVirtualDiskVolumeSource {
  // volumePath is the path that identifies vSphere volume vmdk
  optional string volumePath = 1;

  // fsType is filesystem type to mount.
  // Must be a filesystem type supported by the host operating system.

- Treat VSphere "File (vmdk path here) was not found" errors as success during volume deletion ([#92372](https://github.com/kubernetes/kubernetes/pull/92372), [@breunigs](https://github.com/breunigs)) [SIG Cloud Provider and Storage]

    * I0109 11:17:59.430113       1 vsphere.go:1334] The canonical volume path for the newly created vSphere volume is "[vsanDatastore] 98db185c-6683-d8c7-bc55-0200435ec5da/kubernetes-dynamic-pvc-34650c12-1400-11e9-aef4-005056804cc9.vmdk"
    * Ran regression tests (no zone) and they passed.