OCI CSI (like almost every other CSI) relies a lot on host tools to mount the external volumes (e.g. nfs, iscsi, mount, ...). Talos on the other hand only contains the absolute bare essentials required for operation. These can be extended somewhat, but not in a way to make it compatible with every CSI out-of-the box.
TL;DR: Block Volumes can be provisioned and injected into PV(C)s just fine, but mounting the resulting devices / iscsi targets fails. A first day of hacking lead to 2 reproducible issues:
MountVolume.MountDevice failed for volume: rpc error: code = Internal desc = iscsi: error adding node record to db: exit status 127chroot: failed to run command 'mount': No such file or directory
Given similar developments for the Synology and democratic CSIs, it may be a worthwhile (learning) effort to extend the OCI CSI as well.
OCI CSI (like almost every other CSI) relies a lot on host tools to mount the external volumes (e.g. nfs, iscsi, mount, ...). Talos on the other hand only contains the absolute bare essentials required for operation. These can be extended somewhat, but not in a way to make it compatible with every CSI out-of-the box.
TL;DR: Block Volumes can be provisioned and injected into PV(C)s just fine, but mounting the resulting devices / iscsi targets fails. A first day of hacking lead to 2 reproducible issues:
MountVolume.MountDevice failed for volume: rpc error: code = Internal desc = iscsi: error adding node record to db: exit status 127chroot: failed to run command 'mount': No such file or directoryGiven similar developments for the Synology and democratic CSIs, it may be a worthwhile (learning) effort to extend the OCI CSI as well.