-
Notifications
You must be signed in to change notification settings - Fork 14
Installation steps using helm #14
Comments
Thanks for the report! Could you try to upload the Cilium sysdump again? It seems you submitted the issue before uploading was finished. |
Trial 2: EKS tried installing using helm
Got below error.
|
I received the same errors in both installation methods on a 1.21 EKS cluster. |
Same issue here on a bare-metal cluster. @pchaigno did you get a sysdump? If not I can share one privately with you. |
@ghouscht I didn't receive a sysdump yet. If you could share one, that would help as it would allow us to confirm this is a complexity issue caused by the lack of kernel support for KPR. I'm pchaigno on Slack as well. |
same for me on Azure:
results in
A previous installation with Cilium 1.11.1 went fine on the same cluster (AKS 1.21.7). |
cc @jrajahalme |
I assume this is because of reusing AKS clusters that have been in clustermesh mode previously. |
I had similar issue. I got following errors:
This happened when I downgraded cilium from a newer version to old v1.11.1. And only happened when I enable xdp via I have two nodes. I reload one node and it recovered from the error. I tried to get sysdump ( I guess now it calls debuginfo?) . But I can only get it from the recovered cilium pod. For the crashing one, I cannot get it since it keeps crashing. I uploaded the file here anyway. |
Is there an existing issue for this?
What happened?
but getting errors like
cilium uninstall
and simplecilium install --kube-proxy-replacement=probe
, but that also gave same error.and this went fine.
Cilium Version
1.11.0
Kernel Version
NA
Kubernetes Version
1.21.5
Sysdump
Uploading cilium-sysdump-20220110-102642.zip…
Relevant log output
No response
Anything else?
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: