VolumeSnapshot support
See original GitHub issueHi,
first of all thanks for the great project. I’m running a 3 nodes k8s cluster on rpi4 and it’s a fantastic to have such powerful k8s just running on a desk at home.
I’m using quite a few PVC on this clusters and it would be amazing if I could use VolumeSnapshot
too.
I’m running Microk8s 1.19 and I think Snapshot should be supported from 1.17.
This is what I see when I try to install:
ubuntu@rpi-one:~/cardano-node-builder$ cat snap-test.yaml
---
apiVersion: snapshot.storage.k8s.io/v1beta1
kind: VolumeSnapshot
metadata:
name: new-snapshot-test
namespace: cardano-relay
spec:
source:
persistentVolumeClaimName: cardano-node-tau
ubuntu@rpi-one:~/cardano-node-builder$ k apply -f snap-test.yaml
error: unable to recognize "snap-test.yaml": no matches for kind "VolumeSnapshot" in version "snapshot.storage.k8s.io/v1beta1"
Am I doing anything wrong?
Issue Analytics
- State:
- Created 3 years ago
- Comments:11
Top Results From Across the Web
Volume Snapshots - Kubernetes
In Kubernetes, a VolumeSnapshot represents a snapshot of a volume on a storage ... VolumeSnapshot support is only available for CSI drivers.
Read more >Volume Snapshot & Restore - Kubernetes-CSI
This site documents how to develop and deploy a Container Storage Interface (CSI) driver on Kubernetes.
Read more >vsphere-csi-driver/volume_snapshot.md at master - GitHub
It is only supported in Vanilla Kubernetes cluster now, while not yet supported in either vSphere with Kubernetes cluster aka Supervisor Cluster or...
Read more >Using volume snapshots | Google Kubernetes Engine (GKE)
Using volume snapshots · On this page · Requirements · Before you begin · Creating and using a volume snapshot. Create a PersistentVolumeClaim...
Read more >Container Storage Interface Snapshot Support in Velero
When restoring CSI volumesnapshots across clusters, the name of the CSI driver in the destination cluster is the same as that on the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi, for those following this but don’t want to apply something beta/modified, I actually found the openebs to be very useful. I’m not related to the project but the setup is extremely simple and you get some better grip on the used storage https://github.com/openebs/zfs-localpv
The documentation mentions to modify the paths when you are using microk8s. You can modify the paths quite easily with a sed (hence why I’m posting, for my own ref).
You will have to also apply the storage snapshot yaml found here if you want to have snapshot support https://github.com/openebs/zfs-localpv/blob/master/docs/snapshot.md
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.