Replies: 1 comment 6 replies
-
Hi @Acacio98, Thank you for reaching out! Your issue seems to be related to the kubernetes server version installed by kubeadm during init. The installed server version is the latest k8s patched version available at the time kubeadm init is run, which explains some possible mismatches between the k8s client & server versions when you run the command
Simply find & install the version that previously worked on your setup. A few additional notes:
Hope this helps! |
Beta Was this translation helpful? Give feedback.
-
Hello, when installing the platform, it gives an error when initializing "kubeadm", as it has again released a new version of Docker and gives the following error:
~$ sudo kubeadm init
I0606 17:53:31.293296 4739 version.go:252] remote version is much newer: v1.24.1; falling back to: stable-1.19
W0606 17:53:31.779612 4739 configset.go:348] WARNING: kubeadm cannot validate component configs for API groups [kubelet.config.k8s.io kubeproxy.config.k8s.io]
[init] Using Kubernetes version: v1.19.16
[preflight] Running pre-flight checks
[WARNING SystemVerification]: this Docker version is not on the list of validated versions: 20.10.16. Latest validated version: 19.03
error execution phase preflight: [preflight] Some fatal errors occurred:
[ERROR NumCPU]: the number of available CPUs 1 is less than the required 2
[preflight] If you know what you are doing, you can make a check non-fatal with
--ignore-preflight-errors=...
To see the stack trace of this error execute with --v=5 or higher
Beta Was this translation helpful? Give feedback.
All reactions