You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[root@node01 kubekey]# ./kk version
kk version: &version.Info{Major:"", Minor:"", GitVersion:"", GitCommit:"", GitTreeState:"", BuildDate:"", GoVersion:"go1.19.4", Compiler:"gc", Platform:"linux/amd64"}
[root@node01 kubekey]# cat /etc/redhat-release
Rocky Linux release 8.7 (Green Obsidian)
[root@node01 kubekey]# kubectl get node
NAME STATUS ROLES AGE VERSION
node02 Ready control-plane,worker 3d v1.27.2
node03 Ready control-plane,worker 2d21h v1.27.2
A three-node K8S environment was deployed using kk on node01, node02, and node03, with node01 being the deployment node where kk is located. Due to the need to replace servers, the original servers are being removed one by one. The new servers are deployed with the same operating system, hostname, and IP, and then re-joined to the K8S cluster as a replacement. The operations are as follows:
kubectl drain node03 --ignore-daemonsets --delete-emptydir-data kk delete node node03 -f /opt/deploy/kubekey.yaml kk add nodes -f "/opt/deploy/kubekey.yaml" --container-manager containerd
The operations for node02 and node03 were successful, but an error message was prompted when replacing node01. What are the differences between the node01 deployment node and other nodes? How should the deployment node where kk is located be replaced?
Here is the error log.
15:29:52 CST stdout: [node03]
W0830 15:29:52.380998 133527 initconfiguration.go:332] [config] WARNING: Ignored YAML document with GroupVersionKind kubeadm.k8s.io/v1beta3, Kind=JoinConfiguration
no InitConfiguration or ClusterConfiguration kind was found in the YAML file
To see the stack trace of this error execute with --v=5 or higher
15:29:52 CST message: [node03]
Failed to upload kubeadm certs: Failed to exec command: sudo -E /bin/bash -c "/usr/local/bin/kubeadm init phase upload-certs --upload-certs --config /etc/kubernetes/kubeadm-config.yaml"
W0830 15:29:52.380998 133527 initconfiguration.go:332] [config] WARNING: Ignored YAML document with GroupVersionKind kubeadm.k8s.io/v1beta3, Kind=JoinConfiguration
no InitConfiguration or ClusterConfiguration kind was found in the YAML file
To see the stack trace of this error execute with --v=5 or higher: Process exited with status 1
15:29:52 CST retry: [node03]
15:29:57 CST stdout: [node03]
v1.27.2
15:29:58 CST stdout: [node03]
node02 v1.27.2 [map[address:172.20.163.121 type:InternalIP] map[address:node02 type:Hostname]]
node03 v1.27.2 [map[address:172.20.163.179 type:InternalIP] map[address:node03 type:Hostname]]
15:29:58 CST stdout: [node03]
W0830 15:29:58.272506 134188 initconfiguration.go:332] [config] WARNING: Ignored YAML document with GroupVersionKind kubeadm.k8s.io/v1beta3, Kind=JoinConfiguration
no InitConfiguration or ClusterConfiguration kind was found in the YAML file
To see the stack trace of this error execute with --v=5 or higher
15:29:58 CST message: [node03]
Failed to upload kubeadm certs: Failed to exec command: sudo -E /bin/bash -c "/usr/local/bin/kubeadm init phase upload-certs --upload-certs --config /etc/kubernetes/kubeadm-config.yaml"
W0830 15:29:58.272506 134188 initconfiguration.go:332] [config] WARNING: Ignored YAML document with GroupVersionKind kubeadm.k8s.io/v1beta3, Kind=JoinConfiguration
no InitConfiguration or ClusterConfiguration kind was found in the YAML file
To see the stack trace of this error execute with --v=5 or higher: Process exited with status 1
15:29:59 CST stdout: [node02]
v1.27.2
15:30:00 CST stdout: [node02]
node02 v1.27.2 [map[address:172.20.163.121 type:InternalIP] map[address:node02 type:Hostname]]
node03 v1.27.2 [map[address:172.20.163.179 type:InternalIP] map[address:node03 type:Hostname]]
15:30:01 CST stdout: [node02]
W0830 15:30:00.674176 501935 initconfiguration.go:332] [config] WARNING: Ignored YAML document with GroupVersionKind kubeadm.k8s.io/v1beta3, Kind=JoinConfiguration
no InitConfiguration or ClusterConfiguration kind was found in the YAML file
To see the stack trace of this error execute with --v=5 or higher
15:30:01 CST message: [node02]
Failed to upload kubeadm certs: Failed to exec command: sudo -E /bin/bash -c "/usr/local/bin/kubeadm init phase upload-certs --upload-certs --config /etc/kubernetes/kubeadm-config.yaml"
W0830 15:30:00.674176 501935 initconfiguration.go:332] [config] WARNING: Ignored YAML document with GroupVersionKind kubeadm.k8s.io/v1beta3, Kind=JoinConfiguration
no InitConfiguration or ClusterConfiguration kind was found in the YAML file
To see the stack trace of this error execute with --v=5 or higher: Process exited with status 1
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Version
A three-node K8S environment was deployed using kk on node01, node02, and node03, with node01 being the deployment node where kk is located. Due to the need to replace servers, the original servers are being removed one by one. The new servers are deployed with the same operating system, hostname, and IP, and then re-joined to the K8S cluster as a replacement. The operations are as follows:
kubectl drain node03 --ignore-daemonsets --delete-emptydir-data
kk delete node node03 -f /opt/deploy/kubekey.yaml
kk add nodes -f "/opt/deploy/kubekey.yaml" --container-manager containerd
The operations for node02 and node03 were successful, but an error message was prompted when replacing node01. What are the differences between the node01 deployment node and other nodes? How should the deployment node where kk is located be replaced?
Here is the error log.
Beta Was this translation helpful? Give feedback.
All reactions