Open tiagolobocastro opened 3 months ago
Thanks for all your hard work on this! I just ran into this one. The link suggests disabling init_containers. While this is being worked on, how can I disable init_containers?
Hey, I think you need to disable like so for example, if you use mayastor chart directly:
helm upgrade mayastor mayastor/mayastor -n mayastor --reuse-values --set "csi.node.initContainers.enabled=false"
@CloudFocused I work with @tiagolobocastro on the futures for Mayastor. If you're open to talking about your experiences, and what you're doing, let me know (you can reply here or DM me). Ed
You are right @tiagolobocastro - That did it. Thanks!
Scoping this for v4.2
Describe the bug Some components, by default, use init containers to check for nvme kernel modules. The problem is these modules might actually get compiled builtin, and these checks are failing in this case.
To Reproduce Install on nodes with builtin nvme-tcp kernel modules.
Expected behavior InitContainer should not fail.
OS info (please complete the following information):