-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error on cluster without external snapshotter #929
Comments
@NiklasRosenstein VolSync does depend on VolumeSnapshots for the majority of replications, so sets up watches on those resources (and therefore assumes you have the VolumeSnapshot CRD installed). Are you planning on using VolSync in direct mode for your replications? |
@tesshuflower Indeed, I was planning to use it in direct mode! |
@NiklasRosenstein in the meantime you can install the snapshot controller and CRDs with this helm chart. The controller barely uses any resources in my cluster. |
Yes, sorry I should have mentioned - if you go with that workaround, and are not actually using snapshots, you shouldn't need the snapshot controller itself, only the CRDs. |
Describe the bug
I installed volsync on a Kubernetes cluster without external-snapshotter. According to the documentation
But the volsync Pod fails with the following error (using chart version 0.7.1):
Steps to reproduce
Install volsync on a cluster without the
VolumeSnapshot
CRD (k3s in my case).Additional context
I want to run volsync on a k3s cluster that without
VolumeSnapshot
support.The text was updated successfully, but these errors were encountered: