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
SpiderPool Controller Crash On k8s 1.29 (k0s installer) #3204
Comments
Could you also show the logs of the spiderpool-init? I think it is a bug, I will fix it later. |
Looks like the spiderpool-init also depends on the controller been up:
|
Hi using the latest release, the above error is not occurring but stateful pods are not coming up, following is the error from kubectl describe pod:
The spider controller and agent pods are not giving any errors in the logs Below is the manifest I used:
|
Hi @infinitydon, Thanks for the report. Could you show some debug information using the following commands?
And what is the version of spiderpool you used?
could you show the logs of spiderpool-controller? Maybe the replicas of spiderpool-controller is greater than 1 in your cluster and you need to look at the logs of the other replicas. |
@cyclinder - I am currently using k0s and not kubeadm cluster, so kubectl get po -A -l component=kube-controller-manager and Is spider-pool made to work only in a kubeadm based cluster?
Spiderpool-controller, this is just one replica:
spiderpool-controller Logs attached below spiderpool-logs-march-7-2024.txt Spiderpool version is v0.9.2
|
Currently, we synchronize the cluster CIDR from kubeadm-config configMap and KCM pod, I don't know much about k0s, can you tell me where I can get the cluster CIDR in a k0s based cluster? And you can solve this by creating a configMap manually, please refer to https://spidernet-io.github.io/spiderpool/v0.9/usage/install/overlay/get-started-calico/#prerequisites. |
Works now after creating the configmap. For k0s, I am using the default settings, so the parameters can be retrieved from the k0s command k0s config create | grep -i cidr:
Since spiderpool should be able to work on any k8s distro, I will suggest a different name for the configmap since not all the clusters will be based on kubeadm, maybe give it a generic name, what do you think? |
Maybe we need a new ENV for spiderpool-controller, something like ClusterType. Its value can be Can you read the ClusterConfig by using |
kubectl get clusterconfig -o yaml does not work in the k0s:
I agree with the suggestion of using ENV values so each user will be responsible for providing the values since there could be multiple ways of getting the values depending on the k8s distro. |
Sadly, I went through on k0s quickly. Did not find a way to get cluster cidr by command or reading any resources, maybe we need to ask for help from the k0s community. |
Spiderpool Version
chart spiderpool-0.9.1
Bug Type
Installation Issue
Main CNI
kube-router
What happened?
Tried to install spiderpool using the following commands:
spirderpool controller pod keeps crashing with the following error logs:
What did you expect to happen?
All spiderpool pods should be up and running without crashes
How to reproduce it (as minimally and precisely as possible)
Additional Context
No response
The text was updated successfully, but these errors were encountered: