-
Notifications
You must be signed in to change notification settings - Fork 80
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
Installation failed in an environment with cilium cni as the main plugin #4428
Comments
@yunzck8s thanks for the report, I will look into this. Can you also provide the cilium configmap?
|
@cyclinder this is configmap of the cilium
|
this is a bug, I made a fix for this. before that you can change your cilium ipam from |
Okay, Thanks for you! |
@cyclinder I use the manifests to create the NGINX service but it has some issue
|
I set the routing mode to native for Cilium. Do you know if this configuration will have any impact? |
the native mode is one of the cilium, theoretically there is no impact on cluster communication, but you need to seriously consider the impact of restarting cilium components as a result of switching modes. |
I reset the Kubernetes cluster and created a new cluster with minikube. They also have a problem.
|
Spiderpool Version
v0.9.7
Main CNI
cilium
bug description
During installation, spiderpool-controller keeps reporting errors
What did you expect to happen?
No response
How to reproduce it (as minimally and precisely as possible)
Additional Context
os: rocky 9.5
kubernetes: 1.32
cilium: 1.16
spiderpool-controller-6ff5cbc655-27fwt
spiderpool-init-glqz9
The text was updated successfully, but these errors were encountered: