环境
CentOS7.9-2009
双节点 192.168.100.131 node1
192.168.100.142 node2
1.初始环境
配置静态ip,完成hosts映射
hostnamectl set-hostname node1
[root@node1 ~]# cat /etc/hosts
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
192.168.100.131 node1
192.168.100.142 node2
2. sealos安装包下载与安装
Releases · labring/sealos (github.com) ##sealos安装包下载地址
wget https://github.com/labring/sealos/releases/download/v4.3.0/sealos_4.3.0_linux_amd64.rpm
[root@node1 ~]# yum install -y sealos_4.3.0_linux_amd64.rpm
官网部署文档 >>什么是 Sealos? | Sealos: 专为云原生开发打造的以 K8s 为内核的云操作系统
[root@node1 ~]# sealos run labring/kubernetes:v1.25.0 labring/helm:v3.8.2 labring/calico:v3.24.1 \
> --masters 192.168.100.131 \
> --nodes 192.168.100.142 -p 000000
出现以下图表示部署完成
3.资源检查
[root@node1 ~]# kubectl get nodes
NAME STATUS ROLES AGE VERSION
node1 Ready control-plane 9m31s v1.25.0
node2 Ready <none> 8m38s v1.25.0
[root@node1 ~]# kubectl get ns
NAME STATUS AGE
calico-apiserver Active 3m43s
calico-system Active 7m59s
default Active 9m20s
kube-node-lease Active 9m33s
kube-public Active 9m34s
kube-system Active 9m37s
tigera-operator Active 8m27s
[root@node1 ~]# kubectl get pods -n calico-system
NAME READY STATUS RESTARTS AGE
calico-kube-controllers-85666c5b94-pggd9 1/1 Running 0 8m20s
calico-node-l4qs9 1/1 Running 0 8m23s
calico-node-n7t4d 1/1 Running 0 8m23s
calico-typha-6cb5c84b6-xt2fm 1/1 Running 0 8m23s
csi-node-driver-k4zb8 2/2 Running 0 5m48s
csi-node-driver-zxcqr 2/2 Running 0 5m48s
[root@node1 ~]# kubectl get pods -n kube-system
NAME READY STATUS RESTARTS AGE
coredns-565d847f94-thnwf 1/1 Running 0 9m50s
coredns-565d847f94-vtwgp 1/1 Running 0 9m50s
etcd-node1 1/1 Running 0 10m
kube-apiserver-node1 1/1 Running 0 10m
kube-controller-manager-node1 1/1 Running 3 (5m48s ago) 10m
kube-proxy-2t5nt 1/1 Running 0 9m35s
kube-proxy-z54qb 1/1 Running 0 9m50s
kube-scheduler-node1 1/1 Running 2 (5m44s ago) 10m
kube-sealos-lvscare-node2 1/1 Running 0 9m28s
[root@node1 ~]# kubectl get cs
Warning: v1 ComponentStatus is deprecated in v1.19+
NAME STATUS MESSAGE ERROR
controller-manager Healthy ok
scheduler Healthy ok
etcd-0 Healthy {"health":"true","reason":""}
完成