Understanding automatic CSI migration

305 Views Asked by At

As in-tree plug-ins are going to be deprecated, third party storage provider is installed as default in the Kubernetes cluster. So my doubt is if I don’t enable automatic CSI migration, what will happen if I create new workloads with pvc using CSI driver? And what will happen to my existing workload which is using in-tree plugins. Quite confused on what is the exact use of automatic CSI migration

1

There are 1 best solutions below

2
On

If you don't enable automatic CSI migration, existing workloads that utilize PVCs backed by in-tree drivers will continue to use the in-tree driver.When enabled, any new workloads that use a CSI driver will automatically be migrated to the new CSI driver.The purpose of automatic CSI migration in Kubernetes is to replace existing in-tree storage plugins with a corresponding CSI driver.

If automatic CSI migration is not enabled and new workloads are created with PVCs using a CSI driver, the workloads will still be able to use the in-tree storage plugin. However, they will not be able to take advantage of any features provided by the CSI driver. It recommends that you enable automatic CSI migration to ensure that your workloads are running on the most up-to-date and optimized storage plugins.

CSI migration is to migrate existing workloads from in-tree storage plugins to CSI-based storage plugins.The new CSI-based plugins will be able to take advantage of the improved features and improved performance that comes with the new plugins.

For reference follow the official doc.