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
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 ?
The text was updated successfully, but these errors were encountered:
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 ?
The text was updated successfully, but these errors were encountered: