Hi all,
May be a bit offtopic. Is anyone here running k8s cluster on incus system contaienrs able to get longhorn working properly? (k8s nodes are system containers)
Made below post on LongHorn community/github discussion - (didn’t get any reposnse…hence trying here.)
My k8s nodes are incus system containers. (3 master, 6 workers). Incus contaienrs doesn’t support block device type volume. I have longhorn 1.7.1 version installed on this k8s cluster.
Whenever I create volume using yaml by kubectl, it creates volume with Frontend:Block Device. This is reason why my pods never comes up. They remain in pending/contaiener creating state as this volume can’t be attached to k8s worker node. And volume keep attaching/detaching stage
While doing basic testing from GUI, I observed that whenever I set frontend type to iSCSI while creating volume I could attach it to k8s node file. I then created pvc/pv from this volume in longhorn GUI. Then edited the yaml for POD to include new pvc/pv. From longhorn GUI I could see this volume attached to PODNAME on WORKERNODE. So from longhorn POV, this volume is healthy.
Blockquote
But the pod still remain in containercreating state with kubectl describe POD showing
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning FailedAttachVolume 10s (x243 over 8h) attachdetach-controller AttachVolume.Attach failed for volume "webvol-pv" : rpc error: code = InvalidArgument desc = volume webvol invalid frontend type iscsi
Why is invalid frontend error coming here? Any idea?