Signing NVIDIA kernel module when installing with GPU-Operator

[Frewx]

Hi,
I am trying to install GPU operator to my kubernetes cluster which has 3 worker nodes all of them are pyhsical RTX 3090 GPU nodes. When using GPU-Operator helm deployment I am getting below errors.

The target kernel has CONFIG_MODULE_SIG set, which means that it supports cryptographic signatures on kernel modules. On some systems, the kernel may refuse to load modules without a valid signature from a trusted key. This system also has UEFI Secure Boot enabled; many distributions enforce module signature verification on UEFI systems when Secure Boot is enabled. Would you like to sign the NVIDIA kernel module? Valid responses are: (1) "Sign the kernel module" (2) "Install without signing" [ default ] Please select your response by number or name: The target kernel has CONFIG_MODULE_SIG set, which means that it supports cryptographic signatures on kernel modules. On some systems, the kernel may refuse to load modules without a valid signature from a trusted key. This system also has UEFI Secure Boot enabled; many distributions enforce module signature verification on UEFI systems when Secure Boot is enabled. Would you like to sign the NVIDIA kernel module? (Answer: Install without signing) Kernel module load error: Operation not permitted

How can I select a response when deploying with helm ? Is there a value for this in the values.yml that I can use ?

[github-actions]

This issue is stale because it has been open 90 days with no activity. This issue will be closed in 30 days unless new comments are made or the stale label is removed. To skip these checks, apply the "lifecycle/frozen" label.

[ageisen2000]

Did you ever figure this out? My journalctl logs show node1 kernel: Loading of unsigned module is rejected

[Frewx]

I fixed this by simply installing the kernel driver to the GPU worker nodes. Didn't sign the drivers and disabled secure boot (not recommending it). If you have access to the worker nodes you can sign and install kernel drivers, reboot once, accept the signature and move on.