Feature request : Bring an existing Volume into Trident Management

[kaparora]

The ability to bring existing ONTAP/SolidFire volumes into Trident management.

Usecase 1 : Migrate existing workloads to Kubernetes e.g. a Database
Usecase 2: Bring a volume into trident management, clone it and run tests or a data job.

[oliviermasson]

Hello,

It's an expectation for three major account in France (G100 account)
These accounts wants to deploy container with same security/functionnality as Legacy application.
So they need to be able to "import" already created volume for backup/dr purpose by example

[si-heger]

The ability to "import" volumes into kubernetes via trident is also an important use case for inter-kubernetes-cluster ability to move volumes.

Many customers operate multiple kubernetes clusters e.g . one for dev, one for test, one for prod etc. Sometimes it would be useful to be able to "move" a volume from one cluster to the next. For that some kind of "import" functionality would be the first step

[kaparora]

Is this in the feature pipeline? Just checking as a customer asked about it today.
Kapil

[ghost]

Our customers also want such a feature.

[lari-ch]

Same request from our customers. We would like this feature. Thx

[korenaren]

@kapilarora Yes, in the pipeline. No commitment, but we are actively discussing this one.

[Matthias-Beck]

We are also interested to have this option

[forgosh]

I also have a large customer asking for this. The use case is slightly different however. They want to be able to clone from a PV, not a PVC, so that the clones can cross namespaces. They are saying that it is a competitive weakness today for us.

[kangarlou]

@forgosh Cloning a volume to a different namespace is currently being discussed by the community: https://github.com/erinboyd/community/blob/patch-3/contributors/design-proposals/storage/cloning.md. The manual cloning by the admin and the manual construction of the corresponding PVC and PV is the recommended approach for now. Once Trident supports volume import (this issue), Trident can manage the manually provisioned clones.

[git001]

Any Update on this topic.
We need to migrate one trident/etcd compo from one cluster to another and it would be very helpfully to be able to do something like this.

• export etcd data from cluster A
• import etcd data to cluster B
• copy data from pv storage A to pv storage B

[jason-technology]

This is very important for the Data Fabric. Not only do we need the ability to import PVs, we need the ability to import them from SnapMirror destinations.

[si-heger]

Any update on this? This is probably the most important missing features that directly aligns with the Data Fabric and ability to move workloads from one cluster to another (or one cloud to another)

[clintonk]

Hi, @si-heger. We're working on this at high priority.

[psingh59]

We are also in desperate need of this. When will it be likely to release??

[korenaren]

Volume Import is targeted for the 19.04 release (April 2019) and will include support in the following drivers: ontap-nas, ontap-nas-flexgroup, solidfire-san, and aws-cvs.

[sarangrakhecha]

Addressed in 56bd0dd