Clone Operations for fsx csi ddriver

kubernetes-sigs / aws-fsx-openzfs-csi-driver

Amazon FSx for OpenZFS Cloud Container Storage Interface(CSI) Driver

Apache License 2.0

22 stars 8 forks source link

Clone Operations for fsx csi ddriver #60

Open repudi8or opened 8 months ago

repudi8or commented 8 months ago

i am trying to create a stateful set, that, on scale up, copies the storage from the first replica using volumeClaimTemplate like this :

   volumeClaimTemplates:
    - metadata:
        name: zfstestpvc
      spec:
        accessModes: [ "ReadWriteOnce" ]
        storageClassName: "fsx-sc"
        resources:
          requests:
            storage: 1Gi
        dataSource:
          name: zfstestpvc-0
          kind: PersistentVolumeClaim
          apiGroup: ""

I get the response :

failed to provision volume with StorageClass "fsx-sc": CSI driver does not support clone operations: controller CLONE_VOLUME capability is not reported i'm going to have to work around the need with snapshot/restore

/feature

Please add a feature to CSI driver to support clone operations

k8s-triage-robot commented 5 months ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle stale
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented 4 months ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle rotten
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

hughdanliu commented 3 months ago

/remove-lifecycle rotten

k8s-triage-robot commented 1 week ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle stale
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale