Channels
extensions
rancher-extensions
supermicro-sixsq
ozt
os
one-point-x
rio
onlinemeetup
v16-v21-migration
events
onlinetraining
training-1220
training-0110
training-0124
k3s-contributor
submariner
storage
k3os
windows
ci-cd
theranchcast
rfed_ara
nederlands
ukranian
danish
training-0131
masterclass
training-0207
training-0214
terraform-controller
epinio
phillydotnet
swarm
rancher-wrangler
deutsch
russian
chinese
mesos
français
japanese
arm
longhorn-dev
terraform-provider-rke
service-mesh
azure
gcp
academy
random
elemental
espanol
lima
harvester-dev
portugues
kubernetes
kim
hypper
kubewarden
opni
logging
neuvector-security
rancher-setup
developer
office-hours
mexico
cabpr
rke
vsphere
longhorn-storage
k3s
k3d
terraform-provider-rancher2
fleet
amazon
harvester
rke2
s3gw
hobbyfarm
rancher-desktop
general
Title
l
loud-daybreak-83328
09/20/2022, 12:07 PMStarting a new thread with this. I'm having trouble getting CSI snapshots to work with Longhorn (Rancher 2.6.8, Longhorn 1.3.1, RKE1 or RKE2 both have the issue), K8S 1.22. I followed the directions to the letter here: https://longhorn.io/docs/1.3.1/snapshots-and-backups/csi-snapshot-support/enable-csi-snapshot-support/. I verified that my backup area works, and that snapshots function through the GUI. When I try to create the snapshot through the CSI, it doesn't seem to actually do anything. Kubernetes accepts the yaml, and creates a VolumeSnapshot object, but Longhorn doesn't do anything. Any idea where I can look for messages to indicate what's going on? Thanks.
Ok, maybe I have it working by having the snapshot controller exist in the same namespace as the volumes (which makes sense), but would I need to deploy this in EVERY namespace that needed snapshots created?
I just tried a new namespace and am now getting an error: Failed to create snapshot content with error snapshot controller failed to update test1 on API server: cannot get claim from snapshot
I think I'm in business now. Part of my issue was that I forgot a couple of namespace changes in the external-snapshotter configuration and it was making it not work across the entire cluster.
👍 1