-
Notifications
You must be signed in to change notification settings - Fork 519
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Trying to modprobe allowed true modules does not work #2317
Comments
This looks like fallout from #2296 - what's happening is that As a workaround you can use the host's
I've opened bottlerocket-os/bottlerocket-admin-container#66 to track the fix in the admin container. |
Hi Ben, Just to confirm, the fix you are investigating will work from any container (suitably privileged) and not just need to use the admin container? i.e. to install components like CSI plugins, the node plugin daemon set may need to load whitelisted modules. https://kubernetes-csi.github.io/docs/deploying.html Thanks Chris |
That fix is specific to the admin container. Whether other containers need a fix will depend on whether they are running a base distro where There are a few workarounds that wouldn't require updating the container's base image - using an init container in the deployment to load modules, or a bootstrap container to load them when Bottlerocket boots, or using the host's My current thinking is that the right path is to partially revert #2296 and use This can be checked by running
|
Using a RHEL8 UBI as base image. |
Hi Chris, The recently released Bottlerocket v1.9.1 switched to the xz format for kernel module compression which, at least for now, is more widely supported than zstd. Please give it a go and let me know if you hit any problems! Thanks |
Image I'm using:
$ cat /etc/bottlerocket-release
NAME=Bottlerocket
ID=bottlerocket
VERSION="1.9.0 (aws-k8s-1.22)"
PRETTY_NAME="Bottlerocket OS 1.9.0 (aws-k8s-1.22)"
VARIANT_ID=aws-k8s-1.22
VERSION_ID=1.9.0
BUILD_ID=159e4ced
HOME_URL="https://github.com/bottlerocket-os/bottlerocket"
SUPPORT_URL="https://github.com/bottlerocket-os/bottlerocket/discussions"
BUG_REPORT_URL="https://github.com/bottlerocket-os/bottlerocket/issues"
What I expected to happen:
I expect the additional modules to be loaded using standard linux workflow, e.g. modprobe.
I am trying to load some additional modules as a follow up to #1953. I have created an eksctl file which is as follows:
This was following the documentation here:
https://github.com/bottlerocket-os/bottlerocket#kernel-settings
I expected to be able to ssh into the machine and now modprobe to load modules.
What actually happened:
How to reproduce the problem:
See above, use the eksctl command and ssh into the machine.
The text was updated successfully, but these errors were encountered: