Feature: PVC Clone support (CLONE_VOLUME capability)

[ElanHasson]

Is this a BUG REPORT or FEATURE REQUEST?:

/kind feature

What happened:
I tried to clone a PVC and got this error.
failed to provision volume with StorageClass "vsphere-csi-sc": CSI driver does not support clone operations: controller CLONE_VOLUME capability is not reported

What you expected to happen:
A clone to have been created.

How to reproduce it (as minimally and precisely as possible):

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
    name: clone-of-pvc-1
    namespace: myns
spec:
  accessModes:
  - ReadWriteOnce
  storageClassName: cloning
  resources:
    requests:
      storage: 5Gi
  dataSource:
    kind: PersistentVolumeClaim
    name: pvc-1

Anything else we need to know?:

Environment:

• csi-vsphere version: 3..0.1
• vsphere-cloud-controller-manager version:
• Kubernetes version: 1.26.1
• vSphere version: 7
• OS (e.g. from /etc/os-release): Ubuntu 22.04
• Kernel (e.g. uname -a):
• Install tools:
• Others:

[divyenpatel]

@ElanHasson you can create a snapshot of the volume and later create new volume out of that snapshot.

Does this suffices your requirement?

[ElanHasson]

@divyenpatel thanks for the reply.

I was trying to clone to a different storage class (different vSan policy). I realized I can just create new nodes in my cluster (in this case, elastic) with the new storage class and let elastic replicate it's data, then scale down the old nodes.

At least now there is a breadcrumb for folks searching for clone support.

[k8s-triage-robot]

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

[divyenpatel]

/remove-lifecycle stale

[k8s-triage-robot]

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