3.0安装失败~~求助

Lleejor · 2020年9月6日

rayzhou2017
[master-21 10.10.10.21] MSG:
[reset] Reading configuration from the cluster…
[reset] FYI: You can look at this config file with ‘kubectl -n kube-system get cm kubeadm-config -oyaml’
W0906 12:58:47.629895 40112 reset.go:99] [reset] Unable to fetch the kubeadm-config ConfigMap from cluster: failed to get config map: Get https://lb.kubesphere.local:6443/api/v1/namespaces/kube-system/configmaps/kubeadm-config?timeout=10s: dial tcp 10.10.10.20:6443: connect: connection refused
[preflight] Running pre-flight checks
W0906 12:58:47.630260 40112 removeetcdmember.go:79] [reset] No kubeadm config, using etcd pod spec to get data directory
[reset] No etcd config found. Assuming external etcd
[reset] Please, manually reset etcd to prevent further issues
[reset] Stopping the kubelet service
[reset] Unmounting mounted directories in “/var/lib/kubelet”
[reset] Deleting contents of config directories: [/etc/kubernetes/manifests /etc/kubernetes/pki]
[reset] Deleting files: [/etc/kubernetes/admin.conf /etc/kubernetes/kubelet.conf /etc/kubernetes/bootstrap-kubelet.conf /etc/kubernetes/controller-manager.conf /etc/kubernetes/scheduler.conf]
[reset] Deleting contents of stateful directories: [/var/lib/kubelet /var/lib/dockershim /var/run/kubernetes /var/lib/cni]

The reset process does not clean CNI configuration. To do so, you must remove /etc/cni/net.d

The reset process does not reset or clean up iptables rules or IPVS tables.
If you wish to reset iptables, you must do so manually by using the “iptables” command.

If your cluster was setup to utilize IPVS, run ipvsadm –clear (or similar)
to reset your system’s IPVS tables.

The reset process does not clean your kubeconfig files and you must remove them manually.
Please, check the contents of the $HOME/.kube/config file.

rayzhou2017 · 2020年9月6日

贴一下config yaml文件

Lleejor · 2020年9月6日

rayzhou2017 我换成v1.17.9 安装仍然有问题。
配置文件
`

apiVersion: kubekey.kubesphere.io/v1alpha1
kind: Cluster
metadata:
  name: config-sample
spec:
  hosts:
  - {name: master-21, address: 10.10.10.21, internalAddress: 10.10.10.21, password: an@123@#!}
  - {name: master-22, address: 10.10.10.22, internalAddress: 10.10.10.22, password: an@123@#!}
  - {name: master-23, address: 10.10.10.23, internalAddress: 10.10.10.23, password: an@123@#!}
  - {name: node-24, address: 10.10.10.24, internalAddress: 10.10.10.24, password: an@123@#!}
  - {name: node-25, address: 10.10.10.25, internalAddress: 10.10.10.25, password: an@123@#!}
  - {name: node-26, address: 10.10.10.26, internalAddress: 10.10.10.26, password: an@123@#!}
  - {name: node-27, address: 10.10.10.27, internalAddress: 10.10.10.27, password: an@123@#!}
  - {name: node-28, address: 10.10.10.28, internalAddress: 10.10.10.28, password: an@123@#!}
  roleGroups:
    etcd:
    - master-21
    - master-22
    - master-23
    master:
    - master-21
    - master-22
    - master-23
    worker:
    - node-24
    - node-25
    - node-26
    - node-27
    - node-28
  controlPlaneEndpoint:
    domain: lb.kubesphere.local
    # vip
    address: "10.10.10.20"
    port: "6443"
  kubernetes:
    version: v1.17.9
    imageRepo: kubesphere
    clusterName: cluster.local
    masqueradeAll: false  # masqueradeAll tells kube-proxy to SNAT everything if using the pure iptables proxy mode. [Default: false]
    maxPods: 110  # maxPods is the number of pods that can run on this Kubelet. [Default: 110]
    nodeCidrMaskSize: 24  # internal network node size allocation. This is the size allocated to each node on your network. [Default: 24]
    proxyMode: ipvs  # mode specifies which proxy mode to use. [Default: ipvs]
  network:
    plugin: calico
    calico:
      ipipMode: Always  # IPIP Mode to use for the IPv4 POOL created at start up. If set to a value other than Never, vxlanMode should be set to "Never". [Always | CrossSubnet | Never] [Default: Always]
      vxlanMode: Never  # VXLAN Mode to use for the IPv4 POOL created at start up. If set to a value other than Never, ipipMode should be set to "Never". [Always | CrossSubnet | Never] [Default: Never]
      vethMTU: 1440  # The maximum transmission unit (MTU) setting determines the largest packet size that can be transmitted through your network. [Default: 1440]
    kubePodsCIDR: 10.233.64.0/18
    kubeServiceCIDR: 10.233.0.0/18
  registry:
    registryMirrors: []
    insecureRegistries: []
  addons: [] # add your persistent storage and LoadBalancer plugin configuration here if you have, see https://kubesphere.io/docs/installing-on-linux/introduction/storage-configuration

Lleejor · 2020年9月7日

rayzhou2017 安装了无数次都不行。脑壳疼。

Zzackzhang · 2020年9月7日

请问有什么报错吗？

Lleejor · 2020年9月7日

zackzhang 就是上面的错误，感觉是lb通信问题。但是我PING了是通的。
[master-21 10.10.10.21] MSG:
[reset] Reading configuration from the cluster…
[reset] FYI: You can look at this config file with ‘kubectl -n kube-system get cm kubeadm-config -oyaml’
W0906 12:58:47.629895 40112 reset.go:99] [reset] Unable to fetch the kubeadm-config ConfigMap from cluster: failed to get config map: Get https://lb.kubesphere.local:6443/api/v1/namespaces/kube-system/configmaps/kubeadm-config?timeout=10s: dial tcp 10.10.10.20:6443: connect: connection refused
[preflight] Running pre-flight checks
W0906 12:58:47.630260 40112 removeetcdmember.go:79] [reset] No kubeadm config, using etcd pod spec to get data directory
[reset] No etcd config found. Assuming external etcd
[reset] Please, manually reset etcd to prevent further issues
[reset] Stopping the kubelet service
[reset] Unmounting mounted directories in “/var/lib/kubelet”
[reset] Deleting contents of config directories: [/etc/kubernetes/manifests /etc/kubernetes/pki]
[reset] Deleting files: [/etc/kubernetes/admin.conf /etc/kubernetes/kubelet.conf /etc/kubernetes/bootstrap-kubelet.conf /etc/kubernetes/controller-manager.conf /etc/kubernetes/scheduler.conf]
[reset] Deleting contents of stateful directories: [/var/lib/kubelet /var/lib/dockershim /var/run/kubernetes /var/lib/cni]

The reset process does not clean CNI configuration. To do so, you must remove /etc/cni/net.d

The reset process does not reset or clean up iptables rules or IPVS tables.
If you wish to reset iptables, you must do so manually by using the “iptables” command.

If your cluster was setup to utilize IPVS, run ipvsadm –clear (or similar)
to reset your system’s IPVS tables.

The reset process does not clean your kubeconfig files and you must remove them manually.
Please, check the contents of the $HOME/.kube/config file.

Cauchy · 2020年9月9日

leejor

Storing the certificates in Secret “kubeadm-certs” in the “kube-system” Namespace
error execution phase upload-certs: error uploading certs: error creating token: timed out waiting for the condition

连接到kube-apiserver超时，能ping通vip并不代表vip的端口能通，要保证vip设置的kub-apiserver端口能通。

Lleejor · 2020年9月9日

Cauchy 我所有的节点防火墙都是关闭的，好困惑

Cauchy · 2020年9月9日

Cauchy

lb是自己搭的？还是用的云lb？lb上是不是挂了防火墙或者安全组

Lleejor · 2020年9月9日

Cauchy 按照教程自己搭建的，lb上的防火墙也关闭了。

Cauchy · 2020年9月10日

leejor
那有可能是lb搞得有问题，curl -k https://{masterip}:6443 curl -k https://{vip}:{lbport} 对比下返回结果，不一样的话，就是lb搞得有问题了。

siu91 · 2020年9月22日

Mark一下，我今天也遇到相同的问题@leejor 最后解决了吗

siu91 · 2020年9月22日

Cauchy 我的确实是lb的问题，lb配置用之前的测试主机，防火墙是关了，但是发现唯独这台有配置其它业务的iptables

ylksty · 2021年3月8日

我也遇到了，
yum install -y socat conntrack 解决

Aairkong · 2021年3月18日

我这边也遇到该错误，不过我不是连接超时，不清楚怎么解决

johnhuster · 2021年11月2日

我这边也出现了类似的问题，上面说的也没解决我的问题，我的解决方法就是失败了就执行kk delete cluster，然后再部署，试了几次就可以了，所以kk输出的错误日志有时不能方便定位问题

yule-sun · 2021年12月20日

同样的错误呀，好像不是很活跃呀，没有人回答；解决了的也没有人反馈呀。

多节点离线安装，master三台，worker1台

Cnetos7.8 kubekk v1.2.0 kubernetes v1.20.4 kubesphere v3.1.0

关于这个负载均衡这块要怎么设置呢，是使用其中一台master的主机IP地址作为vip么？没有找到相关的介绍呀。

yule-sun · 2021年12月20日

同样的错误呀，好像不是很活跃呀，没有人回答；解决了的也没有人反馈呀。

多节点离线安装，master三台，worker1台

Cnetos7.8 kubekk v1.2.0 kubernetes v1.20.4 kubesphere v3.1.0

关于这个负载均衡这块要怎么设置呢，是使用其中一台master的主机IP地址作为vip么？没有找到相关的介绍呀。

Rryuhai083 · 2021年12月30日

yule-sun
3.21 版本后可以使用内置的lb，之前的版本要设置lb， lb需要设置一个独立的vip

3.0安装失败~~求助

Lleejor

rayzhou2017K零SK壹S

Lleejor

Lleejor

ZzackzhangK零SK壹S

Lleejor

CauchyK零SK壹S

Lleejor

CauchyK零SK壹S

Lleejor

CauchyK零SK壹S

siu91

siu91

ylksty

Aairkong

johnhuster

yule-sun

yule-sun

Rryuhai083