Open stoneshi-yunify opened 2 years ago
$ kubectl --kubeconfig=vv.config version
WARNING: This version information is deprecated and will be replaced with the output from kubectl version --short. Use --output=yaml|json to get the full version.
Client Version: version.Info{Major:"1", Minor:"24", GitVersion:"v1.24.3", GitCommit:"aef86a93758dc3cb2c658dd9657ab4ad4afc21cb", GitTreeState:"clean", BuildDate:"2022-07-13T14:21:56Z", GoVersion:"go1.18.4", Compiler:"gc", Platform:"darwin/amd64"}
Kustomize Version: v4.5.4
Server Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.3+k3s1", GitCommit:"5fb370e53e0014dc96183b8ecb2c25a61e891e76", GitTreeState:"clean", BuildDate:"2022-01-27T02:12:21Z", GoVersion:"go1.17.5", Compiler:"gc", Platform:"linux/amd64"}
ks: v3.3.0
I have a k3s (kubesphere lightweight cluster) and I was trying to install kubesphere v3.3.0 on it.
the k3s is not very stable, it restarts sometimes, and the ks-installer seems hold a stale connection with apiserver. the ks-installer logs a lot of
connection refused
errors even the k3s apiserver can be connected to.I deleted the ks-installer pod and new ks-installer goes well, which proves the k3s apiserver has been recovered and old ks-installer pod was holding a bad connection.
ks-installer logs
10.101.244.194:443
is k3s apiserver.log in ks-installer pod and curl the apiserver, succeeded:
restarted ks-installer pod then everything goes well.
Is there a way to solve the problem without restarting the ks-installer ?