Feature: Volume Snapshot

[Madhan-SWE]

Is your feature request related to a problem?/Why is this needed
Volume Snapshot 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-pvminstances-snapshots-post
2.https://cloud.ibm.com/apidocs/power-cloud#pcloud-cloudinstances-snapshots-getall
Implement volume snapshot feature if that is supported by the environment.

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.

[mkumatag]

1.https://cloud.ibm.com/apidocs/power-cloud#pcloud-pvminstances-snapshots-post
2.https://cloud.ibm.com/apidocs/power-cloud#pcloud-cloudinstances-snapshots-getall
Implement volume snapshot feature if that is supported by the environment.

These are the vm snapshot calls, I really doubt you can snapshot the volumes with these apis.

[k8s-triage-robot]

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[Madhan-SWE]

Volume Snapshot feature is not yet supported by PowerVS currently.

[Madhan-SWE]

/remove-lifecycle stale
lets hold until the feature is supported by PowerVS.

[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

[k8s-triage-robot]

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

[Madhan-SWE]

/remove-lifecycle stale
lets hold until the feature is supported by PowerVS.

[Madhan-SWE]

/remove-lifecycle rotten