You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to use QNAP-CSI-PlugIn to dynamically create iscsi backed PVC's on my qnap. During the last part of the configuration the node pod tries to use dd if=/dev/sdc bs=4096 count=512 status=none to determine the block device filesystem type but it's not permitted.
@rothgar I do have iscsi extension on all nodes and I can see the iscsi volume get created in my qnap so all that is working. I think it's an issue with the security policy on the pod that the QNAP operator creates. I am able to use the talos debug daemonset to add a pod in the same namespace as the qnap operator and when I ssh into it I can run the same dd commands on the iscsi device that the qnap operator created.
I'm trying to use QNAP-CSI-PlugIn to dynamically create iscsi backed PVC's on my qnap. During the last part of the configuration the node pod tries to use
dd if=/dev/sdc bs=4096 count=512 status=none
to determine the block device filesystem type but it's not permitted./dev
is mounted in the container andtalosctl disks
on the node shows that the iscsi block device resides at/dev/sdc
I have
pod-security.kubernetes.io/enforce: privileged
label set on the qnap-csi operator namespace.Is there anything else that's needed to allow the dd command to work?
The text was updated successfully, but these errors were encountered: