Centos7安装部署k8s(kubernetes)最新v1.27.1版本超详细安装教程

您所在的位置:网站首页 zookeeper部署k8s Centos7安装部署k8s(kubernetes)最新v1.27.1版本超详细安装教程

Centos7安装部署k8s(kubernetes)最新v1.27.1版本超详细安装教程

#Centos7安装部署k8s(kubernetes)最新v1.27.1版本超详细安装教程| 来源: 网络整理| 查看: 265

master 初始化(仅在master节点主机上执行)

kubeadm init --image-repository=registry.aliyuncs.com/google_containers --apiserver-advertise-address=192.168.42.150 --kubernetes-version=v1.27.1 # --image-repository 镜像加速地址,一般不动 # --apiserver-advertise-address master 节点IP地址,自己改 # --kubernetes-version kubernetes 版本,自己选择的什么版本就改成什么版本 # 初始化失败可以使用 kubeadm reset 重置 # 失败原因多半是因为网络问题,可以换个网络试试

初始化成功后执行(仅在master节点主机上执行)

mkdir -p $HOME/.kube sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config sudo chown $(id -u):$(id -g) $HOME/.kube/config

将 node 加入集群(仅在node节点主句执行)不要直接复制,每个人不一样

# 执行成功后,会出现类似下列内容: # kubeadm join 192.168.80.60:6443 --token f9lvrz.59mykzssqw6vjh32 \ # --discovery-token-ca-cert-hash sha256:4e23156e2f71c5df52dfd2b9b198cce5db27c47707564684ea74986836900107 # 将控制台打印的这句复制到 node 节点主机上执行就行 # 如果忘记或者过期可以使用以下命令重新生成 # kubeadm token create --print-join-command

查看集群状态(master 节点执行)

kubectl get nodes

输出:

NAME STATUS ROLES AGE VERSION master NotReady control-plane 7h21m v1.27.1 node1 NotReady 7h20m v1.27.1 node2 NotReady 7h20m v1.27.1

可以看到所有节点都是 NotReady ,这是因为还没有配置网络

配置网络(仅在master节点执行)

k8s与Calico版本对应

Kubernetes 版本Calico 版本Calico 文档1.18、1.19、1.203.18https://projectcalico.docs.tigera.io/archive/v3.18/getting-started/kubernetes/requirementshttps://projectcalico.docs.tigera.io/archive/v3.18/manifests/calico.yaml1.19、1.20、1.213.19https://projectcalico.docs.tigera.io/archive/v3.19/getting-started/kubernetes/requirementshttps://projectcalico.docs.tigera.io/archive/v3.19/manifests/calico.yaml1.19、1.20、1.213.20https://projectcalico.docs.tigera.io/archive/v3.20/getting-started/kubernetes/requirementshttps://projectcalico.docs.tigera.io/archive/v3.20/manifests/calico.yaml1.20、1.21、1.223.21https://projectcalico.docs.tigera.io/archive/v3.21/getting-started/kubernetes/requirementshttps://projectcalico.docs.tigera.io/archive/v3.21/manifests/calico.yaml1.21、1.22、1.233.22https://projectcalico.docs.tigera.io/archive/v3.22/getting-started/kubernetes/requirementshttps://projectcalico.docs.tigera.io/archive/v3.22/manifests/calico.yaml1.21、1.22、1.233.23https://projectcalico.docs.tigera.io/archive/v3.23/getting-started/kubernetes/requirementshttps://projectcalico.docs.tigera.io/archive/v3.23/manifests/calico.yaml1.22、1.23、1.243.24https://projectcalico.docs.tigera.io/archive/v3.24/getting-started/kubernetes/requirementshttps://projectcalico.docs.tigera.io/archive/v3.24/manifests/calico.yaml1.23、1.24、1.25、1.26、1.273.25https://projectcalico.docs.tigera.io/archive/v3.25/getting-started/kubernetes/requirementshttps://projectcalico.docs.tigera.io/archive/v3.25/manifests/calico.yaml

或者自己去官网查看版本对应关系

https://docs.tigera.io/calico/latest/getting-started/kubernetes/requirements

下载(网址换成自己版本对应的即可)

wget --no-check-certificate https://projectcalico.docs.tigera.io/archive/v3.25/manifests/calico.yaml

下载不了的可以把后面网址复制到浏览器下载下来后在传到虚拟机

修改 calico.yaml 文件

vim calico.yaml # 在 - name: CLUSTER_TYPE 下方添加如下内容 - name: CLUSTER_TYPE value: "k8s,bgp" # 下方为新增内容 - name: IP_AUTODETECTION_METHOD value: "interface=master节点主机的网卡名称"

配置网络

kubectl apply -f calico.yaml

再次查看节点信息

查看 node 状态

kubectl get nodes

输出:

NAME STATUS ROLES AGE VERSION master NotReady control-plane 21m v1.27.1 node1 NotReady 20m v1.27.1 node2 NotReady 20m v1.27.1

查看 pod 状态

kubectl get pods --all-namespaces -o wide

输出:

[root@master ~]# kubectl get pods --all-namespaces -o wide NAMESPACE NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES kube-system calico-kube-controllers-f79f7749d-rkqgw 0/1 Pending 0 11s kube-system calico-node-7698p 0/1 Init:0/3 0 11s 192.168.80.60 k8s kube-system calico-node-tvhnb 0/1 Init:0/3 0 11s 192.168.0.18 centos-7-9-16 kube-system coredns-c676cc86f-4lncg 0/1 Pending 0 8m14s kube-system coredns-c676cc86f-7n9wv 0/1 Pending 0 8m14s kube-system etcd-k8s 1/1 Running 0 8m21s 192.168.80.60 k8s kube-system kube-apiserver-k8s 1/1 Running 0 8m18s 192.168.80.60 k8s kube-system kube-controller-manager-k8s 1/1 Running 0 8m18s 192.168.80.60 k8s kube-system kube-proxy-87lx5 1/1 Running 0 6m16s 192.168.0.18 centos-7-9-16 kube-system kube-proxy-rctn6 1/1 Running 0 8m14s 192.168.80.60 k8s kube-system kube-scheduler-k8s 1/1 Running 0 8m18s 192.168.80.60 k8s [root@k8s ~]#

可以看到正在初始化,现在稍等一段时间(多久看网络情况)

初始化失败大部分情况也是因为网络原因,建议换个网络试试

初始化成功

查看 node 状态

kubectl get nodes

输出:

NAME STATUS ROLES AGE VERSION master Ready control-plane 7h21m v1.27.1 node1 Ready 7h20m v1.27.1 node2 Ready 7h20m v1.27.1

全部 Ready

查看 pod 状态

kubectl get pods --all-namespaces -o wide

输出:

NAMESPACE NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES kube-system calico-kube-controllers-6c99c8747f-92ctj 1/1 Running 1 (64m ago) 31m 172.16.219.69 master kube-system calico-node-72n28 1/1 Running 2 (64m ago) 31m 192.168.42.150 master kube-system calico-node-jb2n8 1/1 Running 1 (64m ago) 31m 192.168.42.152 node2 kube-system calico-node-m6ndl 1/1 Running 1 (64m ago) 31m 192.168.42.151 node1 kube-system coredns-7bdc4cb885-6l9dk 1/1 Running 1 (64m ago) 33m 172.16.219.70 master kube-system coredns-7bdc4cb885-j7qlm 1/1 Running 1 (64m ago) 33m 172.16.219.68 master kube-system etcd-master 1/1 Running 1 (64m ago) 33m 192.168.42.150 master kube-system kube-apiserver-master 1/1 Running 1 (64m ago) 33m 192.168.42.150 master kube-system kube-controller-manager-master 1/1 Running 1 (64m ago) 33m 192.168.42.150 master kube-system kube-proxy-558cb 1/1 Running 1 (64m ago) 33m 192.168.42.150 master kube-system kube-proxy-fpk62 1/1 Running 1 (64m ago) 32m 192.168.42.152 node2 kube-system kube-proxy-sm4ph 1/1 Running 1 (64m ago) 32m 192.168.42.151 node1 kube-system kube-scheduler-master 1/1 Running 1 (64m ago) 33m 192.168.42.150 master

全部 Ready

k8s 命令补全

! grep -q kubectl "$HOME/.bashrc" && echo "source /usr/share/bash-completion/bash_completion" >>"$HOME/.bashrc" ! grep -q kubectl "$HOME/.bashrc" && echo "source


【本文地址】


今日新闻


推荐新闻


CopyRight 2018-2019 办公设备维修网 版权所有 豫ICP备15022753号-3