We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
v3.0.13
RedHat 8.6
apiVersion: kubekey.kubesphere.io/v1alpha2 kind: Cluster metadata: name: assistant spec: hosts: - {name: kme-23-18, address: 172.16.23.18, internalAddress: 172.16.23.18, user: root, password: "sugon_web.com@."} - {name: kme-23-20, address: 172.16.23.20, internalAddress: 172.16.23.20, user: root, password: "sugon_web.com@."} - {name: kme-24-15, address: 172.16.24.15, internalAddress: 172.16.24.15, user: root, password: "sugon_web.com@."} roleGroups: etcd: - kme-23-18 - kme-23-20 - kme-24-15 control-plane: - kme-23-18 - kme-23-20 - kme-24-15 worker: - kme-23-18 - kme-23-20 - kme-24-15 controlPlaneEndpoint: ## Internal loadbalancer for apiservers internalLoadbalancer: haproxy domain: lb.kubesphere.local address: "" port: 6443 kubernetes: version: v1.23.10 clusterName: cluster.local autoRenewCerts: true containerManager: docker etcd: type: kubekey network: plugin: calico kubePodsCIDR: 10.233.64.0/18 kubeServiceCIDR: 10.233.0.0/18 ## multus support. https://github.com/k8snetworkplumbingwg/multus-cni multusCNI: enabled: false registry: privateRegistry: "172.16.23.18:5000" namespaceOverride: "" registryMirrors: [] insecureRegistries: [] addons: []
只部署k8s三节点,其中一个节点的calico node pod启动失败: 发现异常的节点上calico生成的配置IP加了个中括号:
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
What is version of KubeKey has the issue?
v3.0.13
What is your os environment?
RedHat 8.6
KubeKey config file
A clear and concise description of what happend.
只部署k8s三节点,其中一个节点的calico node pod启动失败:
发现异常的节点上calico生成的配置IP加了个中括号:
Relevant log output
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: