whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

CSI migration of Portworx is in alpha

Browse Source
This commit is contained in:
Oksana Naumov
2021-11-11 12:01:08 -08:00
parent 44576253cf
commit 02f63b9661
2 changed files with 14 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/concepts/storage/volumes.md
+10
View File
@@ -1050,6 +1050,16 @@ but new volumes created by the vSphere CSI driver will not be honoring these par
To turn off the `vsphereVolume` plugin from being loaded by the controller manager and the kubelet, you need to set `InTreePluginvSphereUnregister` feature flag to `true`. You must install a `csi.vsphere.vmware.com` {{< glossary_tooltip text="CSI" term_id="csi" >}} driver on all worker nodes.
#### Portworx CSI migration
{{< feature-state for_k8s_version="v1.23" state="alpha" >}}
The `CSIMigration` feature for Portworx has been added but disabled by default in Kubernetes 1.23 since it's in alpha state.
It redirects all plugin operations from the existing in-tree plugin to the
`pxd.portworx.com` Container Storage Interface (CSI) Driver.
[Portworx CSI Driver](https://docs.portworx.com/portworx-install-with-kubernetes/storage-operations/csi/)
must be installed on the cluster.
To enable the feature, set `CSIMigrationPortworx=true` in kube-controller-manager and kubelet.
## Using subPath {#using-subpath}
Sometimes, it is useful to share one volume for multiple uses in a single pod.