https://rancher.com/ logo
#longhorn-storage
Title
# longhorn-storage
a

adamant-kite-43734

02/02/2023, 9:49 AM
This message was deleted.
l

late-needle-80860

02/02/2023, 9:55 AM
My reason for
symlinking
the
kubelet
dir from
var/lib/kubelet
to
myDir
is that if I didn’t I would get
CSINode … <http://driver.longhorn.io|driver.longhorn.io>
not found. As that driver would end up in
/var/lib/kubelet
instead of the new kubelet root-dir I set via
--kubelet-arg root-dir=…
And yes I’ve also configured the
kubeletRootDir
variable to the Longhorn Helm Chart on the CSI component.
I can also see that in
/var/lib/kubelet/plugins/kubernetes.io/csi/driver.longhorn.io/SOME_VOLUME/
the
globalmount
dir have
1001
in the
gid
section when e.g. viewing permission with
ls -la
… and that’s NOT the case on the node whereon I’ve
symlinked
the kubelet and containerd directories
@creamy-pencil-82913 would you be so kind, if you have any input on this one … me again, from the good ol’ #2068 on the
K3s
repo … trying in the
Longhorn
channel here .. as Longhorn is the final thing not fully working after doing what I describe above. Any help is highly appreciated.
The node-driver-registrar do not throw any errors … however, it seems to be registering the driver to
/var/lib/kubelet
and not reflect the value to
kubeletRootDir
Hmm diving deeper I see that the Longhorn project uses https://github.com/kubernetes-csi/node-driver-registrar … and there’s a
--kubelet-reigstration-path
parameter … However, if one changes the
--kubelet-arg root-dir
parameter this is not reflected on the node-driver-registrar parameters ..
So setting csi.kubeletRootDir in the values.yaml file of the Longhorn Helm chart sets the KUBELET_ROOT_DIR env. var in the
longhorn-driver-deployer
Deployment
… and that is reflected in the
longhorn-csi-plugin
DaemonSet
workload … However, if one have a cluster with a cluster already running Longhorn and one want to change the
kubelet
and
conatinerd
data paths … then apparently it’s not enough to set the
csi.kubeletRootDir
and then delete the
longhorn-csi-plugin
DaemonSet
as it doesn’t come back… I ended up having to uninstall Longhorn >> install it again >> the created
longhorn-csi-plugin
DaemonSet
then reflected the
csi.kubeletRootDir
setting. --- For people wanting to change
kubelet
and
containerd
paths and are running
Longhorn
is there a better way than uninstalling Longhorn as that have potentially a prolonged downtime effect. ---
So setting csi.kubeletRootDir in the values.yaml file of the Longhorn Helm chart sets the KUBELET_ROOT_DIR env. var in the
longhorn-driver-deployer
Deployment
… and that is reflected in the
longhorn-csi-plugin
DaemonSet
workload … However, if one have a cluster with a cluster already running Longhorn and one want to change the
kubelet
and
conatinerd
data paths … then apparently it’s not enough to set the
csi.kubeletRootDir
and then delete the
longhorn-csi-plugin
DaemonSet
as it doesn’t come back… I ended up having to uninstall Longhorn >> install it again >> the created
longhorn-csi-plugin
DaemonSet
then reflected the
csi.kubeletRootDir
setting. --- For people wanting to change
kubelet
and
containerd
paths and are running
Longhorn
is there a better way than uninstalling Longhorn as that have potentially a prolonged downtime effect???? --- Thank you very much.
Ey yo 😄 - anyone
Anyone with an idea on this? Thanks What’s the process for updating and applying the
csi.kubeletRootDir
value when Longhorn is deployed via the Helm chart?
Anyone with an idea on this? Thanks What’s the process for updating and applying the
csi.kubeletRootDir
value when Longhorn is deployed via the Helm chart?
n

narrow-egg-98197

02/16/2023, 11:06 AM
I guess it should also include re-create longhorn manager, since the interface of CSI node server and controller server were implement by longhorn-manager. https://github.com/longhorn/longhorn-manager/tree/master/csi
l

late-needle-80860

02/17/2023, 7:41 AM
Alright cool. I’ll try the recreate the longhorn manager approach
😀 1
64 Views