-
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
[BUG] serviceCIDR get failed #4307
Comments
Thanks for the report @0x0034, We'll look into it further. |
Hi @0x0034, I can't reproduce your issue by using your kubeadm-config, what's your k8s version? and can you run the command
|
the kubernetes version is
apiVersion: apps.sealos.io/v1beta1
kind: Cluster
metadata:
creationTimestamp: null
name: qa-lab
spec:
hosts:
- ips:
- 10.215.45.124:22
- 10.215.45.91:22
- 10.215.45.144:22
roles:
- master
- amd64
- ips:
- 10.215.20.33:22
roles:
- node
- amd64
image:
- registry.cn-shanghai.aliyuncs.com/labring/kubernetes-docker:v1.21.14
- registry.cn-shanghai.aliyuncs.com/labring/helm:v3.15.4
ssh:
passwd: xxx
pk: /root/.ssh/id_rsa
port: 22
user: root
status: {}
---
apiVersion: kubeadm.k8s.io/v1beta2
kind: ClusterConfiguration
networking:
dnsDomain: cluster.local
serviceSubnet: 245.100.128.0/18
podSubnet: 10.215.22.0/24
scheduler: {} sealos apply -f Clusterfile you can build cluster by above command , i hope can help you recurrence the bug |
Spiderpool Version
0.9.7
kubernetes Version
1.21.14
Main CNI
macvlan
bug description
What did you expect to happen?
No response
How to reproduce it (as minimally and precisely as possible)
No response
Additional Context
问题补充:
当删除
kubeadm-config
后 controller 可以正常的从kube-controller-manager
中获取 serviceCIDR . controller 日志如下The text was updated successfully, but these errors were encountered: