-
Notifications
You must be signed in to change notification settings - Fork 512
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
cilium-node-init CrashLoopBackOff when running on Bottlerocket OS #1405
Comments
Thank you for bringing the issue to our attention. The problem you’re experiencing is a result of the cilium-node-init container attempting to use the host’s Bash. As Bottlerocket does not have a shell available, accessing Bash in this manner is not possible. However, we don’t believe that cilium-init-nodes are required to run Cilium on Bottlerocket successfully. Can you try that out and see if that works for you? You should be able to install Cilium via Helm and omit the cilium-init-nodes as shown below:
|
Thanks I've tried that and that does work. However, it only works when I need chaining mode enabled With it enabled Cilium doesn't start
and |
@mmochan Did you find a workaround for this? We're seeing the exact same issue unfortunately. |
@springroll12 Unfortunately not yet. |
After some trial and error, I was able to get Cilium v1.9.x to work after upgrading the AWS-CNI to v1.7.9 (v1.7.5 seems to be the current default). On the amazon-vpc-cni-k8s repo you can read more about the issue and the fix. I did run into some different issues with v1.10.x, so the following only applies to v1.9.x. These were the steps I used to successfully install cilium:
Please give these steps a shot and let us know how it goes! |
I have exactly the same problem, I've installed cilium successfully on Amazon Linux but I got the same error using bottleneck. I tried the steps described by @jpculp but that didn't work on my side. |
Hi @Smana. I'm sorry to hear you're running into issues. We also saw them on our end with 1.10.x and are continuing to investigate. The fix above only applies to cilium 1.9.x. |
Let me know if you want me to tests on my side whenever a fix is ready to be tested. |
Hi @Smana, sorry for the delay. Cilium 1.10.3 seems to initialize successfully with the steps detailed above, but with a slight modification to step 4. Please give the follow install configuration a shot and let us know how it goes!
If you aren't interested in AWS CNI chaining, these steps are also valid:
|
Hey @Smana, hopefully the updated instructions above are working for your use case. If you run into anything else, don't hesitate to open another issue and let us know. |
Platform I'm building on:
What I expected to happen:
I expected the cilium-node-init pod to start successfully
What actually happened:
cilium-node-init fails with
How to reproduce the problem:
The daemonset for the cilium-node-init pods runs a startup script and is expecting bash to be available which I don't believe it is?
The working node is an Amazon Linux 2 AMI
The text was updated successfully, but these errors were encountered: