kubeedge: edge: Init websocket connection failed x509: cannot validate certificate for 10.0.10.35 because it doesn't contain any IP SANs

What happened:

What you expected to happen: edge is running healthy How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

KubeEdge version(e.g. cloudcore/edgecore --version):
1.3.0 CloudSide Environment:
Hardware configuration (e.g. lscpu): Architecture: aarch64 Byte Order: Little Endian CPU(s): 16 On-line CPU(s) list: 0-15 Socket(s): 4 NUMA 节点： 1 Model name: phytium FT1500a BogoMIPS: 3594.24 NUMA node0 CPU(s): 0-15 Flags: fp asimd evtstrm aes pmull sha1 sha2 crc32
OS (e.g. cat /etc/os-release): NAME=“Ubuntu” VERSION=“16.04.6 LTS (Xenial Xerus)” ID=ubuntu ID_LIKE=debian PRETTY_NAME=“Ubuntu 16.04.6 LTS” VERSION_ID=“16.04” HOME_URL=“http://www.ubuntu.com/” SUPPORT_URL=“http://help.ubuntu.com/” BUG_REPORT_URL=“http://bugs.launchpad.net/ubuntu/” VERSION_CODENAME=xenial UBUNTU_CODENAME=xenial
Kernel (e.g. uname -a): Linux pk6 4.4.58-20180615.kylin.server.YUN±generic #kylin SMP Tue Jul 10 14:55:31 CST 2018 aarch64 aarch64 aarch64 GNU/Linux
Go version (e.g. go version): go version go1.13.11 linux/arm64
Others:

EdgeSide Environment:

edgecore version (e.g. edgecore --version): 1.3.0
Hardware configuration (e.g. lscpu): Architecture: aarch64 Byte Order: Little Endian CPU(s): 16 On-line CPU(s) list: 0-15 Socket(s): 4 NUMA 节点： 1 Model name: phytium FT1500a BogoMIPS: 3594.24 NUMA node0 CPU(s): 0-15 Flags: fp asimd evtstrm aes pmull sha1 sha2 crc32
OS (e.g. cat /etc/os-release): NAME=“Ubuntu” VERSION=“16.04.6 LTS (Xenial Xerus)” ID=ubuntu ID_LIKE=debian PRETTY_NAME=“Ubuntu 16.04.6 LTS” VERSION_ID=“16.04” HOME_URL=“http://www.ubuntu.com/” SUPPORT_URL=“http://help.ubuntu.com/” BUG_REPORT_URL=“http://bugs.launchpad.net/ubuntu/” VERSION_CODENAME=xenial UBUNTU_CODENAME=xenial
Kernel (e.g. uname -a): Linux pk6 4.4.58-20180615.kylin.server.YUN±generic #kylin SMP Tue Jul 10 14:55:31 CST 2018 aarch64 aarch64 aarch64 GNU/Linux
Go version (e.g. go version): go version go1.13.11 linux/arm64
Others:

About this issue

Original URL
State: closed
Created 4 years ago
Comments: 26 (9 by maintainers)

Most upvoted comments

same issue version 1.5 please give a solution

yeganeahmadnejad on Jan 10, 2021

@yzhao66 is it ok now? @markwangC I have try latest code and bring up a new cluster, no error happens. can you show this

kubectl get nodes
cloudcore --version
edgecore --version

kubectl delete secret casecret -nkubeedge
kubectl delete secret cloudcoresecret -nkubeedge
# both cloud and edge side
mv /etc/kubeedge/ca  /etc/kubeedge/ca.bak 
mv  /etc/kubeedge/certs /etc/kubeedge/certs.bak

luogangyi on May 27, 2020

You need to add the advertise-address to cloudcore, which will be add to SANs in cloud certs. Ref: https://github.com/kubeedge/kubeedge/blob/master/docs/setup/kubeedge_configure.md#modification-in-cloudcoreyaml https://github.com/kubeedge/kubeedge/blob/master/docs/setup/kubeedge_install_keadm.md#setup-cloud-side-kubeedge-master-node

fisherxu on May 27, 2020