Feature: Volume Clone

[Madhan-SWE]

Is your feature request related to a problem?/Why is this needed Volume clone feature is currently not implemented in ibm-powervs-block-csi-driver.

/feature

Describe the solution you'd like in detail Explore the following APIs in the Power Cloud API Docs: 1.https://cloud.ibm.com/apidocs/power-cloud#pcloud-volumes-clone-post 2.https://cloud.ibm.com/apidocs/power-cloud#pcloud-v2-volumes-clone-post 3.https://cloud.ibm.com/apidocs/power-cloud#pcloud-v2-volumes-clonetasks-get 4.https://cloud.ibm.com/apidocs/power-cloud#pcloud-v2-volumesclone-post 5.https://cloud.ibm.com/apidocs/power-cloud#pcloud-v2-volumesclone-getall 6.https://cloud.ibm.com/apidocs/power-cloud#pcloud-v2-volumesclone-get 7.https://cloud.ibm.com/apidocs/power-cloud#pcloud-v2-volumesclone-delete

Add support for volume clone feature in the ibm-powervs-block-csi-driver.

Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.

Additional context Add any other context or screenshots about the feature request here.

https://github.com/kubernetes-sigs/ibm-powervs-block-csi-driver/issues/241#tasklist-block-5b6dc7f0-a980-42e2-90e6-c596ecc2c50c

[Madhan-SWE]

/assign

[Madhan-SWE]

PR is on hold as the volume clone feature is not yet completed in the powervs front.

[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

[Madhan-SWE]

/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

[yussufsh]

/lifecycle frozen

[yussufsh]

/assign

[yussufsh]

/unassign @Madhan-SWE

[kishen-v]

/remove-lifecycle frozen https://github.com/kubernetes-sigs/cluster-api-provider-ibmcloud/pull/1965#issuecomment-2357494144 Support for Volume clone is now available.

/assign

[GunaKKIBM]

@kishen-v I will take this up.