vsphere-csi-driver
vsphere-csi-driver copied to clipboard
kubernetes-sigs
How to remove snapshot manually when can't see it on console or cli
Hi All. I have question about remove snapshot when can't see it on console or cli. I use OpenShift as container platform (vsphere-csi-driver for storage class) and NetbackupKOPS for software backup PVC. NetbackupKOPS job only remove infomation snapshot on OpenShift but it not remove snapshot on vSphere. Now, I don't know how to remove it. Someone can help me resolve it? (Manually remove snapshot container volume)
Hi, I have the same question. My max snapshots was set to 3 so I was able to increase it to 4, but I want to prevent it from happening again.
We will be adding APIs to get snapshots of a volume and to delete snapshots of a volume (or an individual snapshot) in tool called CNS Manager (it is a diagnostic and self-service tool that helps detect and auto-remediate some of the known issues in storage control plane in vCenter). These APIs will be available in the upcoming CNS Manager release v0.3.0.
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/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas 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
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/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas 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
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Reopen this issue with
/reopen - Mark this issue as fresh with
/remove-lifecycle rotten - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
@k8s-triage-robot: Closing this issue, marking it as "Not Planned".
In response to this:
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied- After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied- After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closedYou can:
- Reopen this issue with
/reopen- Mark this issue as fresh with
/remove-lifecycle rotten- Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
You can use cns-manager tool to list snapshots of a volume and to remove the snapshots. These changes are GAed now https://github.com/vmware-samples/cloud-native-storage-self-service-manager/releases/tag/v0.3.0.