kubernetes-setup

复现过程

wget -c https://sealyun.oss-cn-beijing.aliyuncs.com/05a3db657821277f5f3b92d834bbaf98-v1.22.0/kube1.22.0.tar.gz

sealos init —passwd 'password' \
	—master 192.168.1.122  \
	—pkg-url /root/kube1.22.0.tar.gz  \
	—version v1.20.2

报错：

command result is: this version of kubeadm only supports deploying clusters with the control plane version >= 1.21.0. Current

I'm trying to apply node labels using the following configuration:

  - name: test
    instanceType: m5.large
    minSize: 1
    maxSize: 2
    desiredCapacity: 2
    labels:
      role: test
      node-role.kubernetes.io/test: ok

According to #580 and #582 using node-role subdomain should the way to apply labels, however I still get a domain error:

AWS::EKS::No

Describe the solution you'd like
When adding a configmap via the config-map field in a plugin, if we see they are adding a yaml file, why not parse it and try and see if its valid yaml? Especially with the whitespace of nesting it this can cause issues and I've hit the problem more than once.

I assume we could do a basic json/yaml validation, more if others request it.

**Anything el

Same as #3319 for all Kubernetes components here the list (maybe not exhaustive):

• kube-scheduler
• kube-controller-manager
• kubelet
• kube-proxy

Works in Safari, Chrome for Mac, Chrome for PC, Edge, but not IE version 11.192.16299.0 on Windows 10

The command line should be able to display the pupernetes version.