Replies: 2 comments 1 reply
-
@dgrechka as a stop gap you can try deploying a privileged deamon set, with HostMNT, HostNET and HostIPC as well as correctly setup bind mounts (make crypytsetup available as part of path), that way when the csi plugin nsenters into the host namespace. It will execute your cryptsetup binary as long as it is part of the path. REF: https://github.com/longhorn/longhorn-manager/blob/fade760c17abe2aec1a23bf8a584f8c612e20675/csi/crypto/luks.go#L53 This deamonset can also be used to load/make available the |
Beta Was this translation helpful? Give feedback.
-
The "it works on my machine" problem should never exist. Does the Longhorn team even understand the point of containerization? Clearly they've lost sight of the most important fundamental concept of why we want containerized solutions. |
Beta Was this translation helpful? Give feedback.
-
Hi all,
Why does longhorn requires to install
cryptsetup
on the k8s nodes to enable encryption? Why can't we instead include cryptsetup into the engine or manager image (not sure in which it is required)?For some setups, like k3os, it is hard to install dependencies like these on the nodes.
Beta Was this translation helpful? Give feedback.
All reactions