Centos7三台机器安装 k8s

最新推荐文章于 2024-02-18 18:30:54 发布

swingLau007

最新推荐文章于 2024-02-18 18:30:54 发布

阅读量1k

点赞数

分类专栏： linux软件文章标签： k8s

本文链接：https://blog.csdn.net/swingLau007/article/details/111582625

版权

linux软件专栏收录该内容

17 篇文章 0 订阅

订阅专栏

1.机器配置

硬件	说明
CPU	2核+
内存	2G +
硬盘	10G+
系统	CentOS Linux release 7.9.2009 (Core)

安装k8s，cpu不能少于2核，内存不能少于2G, 否则安装时说提示出错，无法安装。

2.软件安装 (每台都执行一次)

2.1 修改Hosts

vi /etc/hosts

192.168.56.101 master01
192.168.56.102 node1
192.168.56.103 node2

修改Hostname

hostname
# localhost.localdomain  // 显示当前的hostname
hostnamectl set-hostname master01   //其它两台是 node1\node2
hostname
# master01 // 显示修改后的hostname  其它两台是 node1\node2

修改后的hostname 在kubectl get node 里面显示
安装成功的效果图

kubectl get node
NAME       STATUS   ROLES                  AGE    VERSION
master01   Ready    control-plane,master   112m   v1.20.1
node1      Ready    <none>                 79m    v1.20.1
node2      Ready    <none>                 56m    v1.20.1

2.2 关闭swap，注释swap分区

[root@master01 ~]# swapoff -a
[root@master01 ~]# cat /etc/fstab

#
# /etc/fstab
# Created by anaconda on Tue Mar 31 22:44:34 2020
#
# Accessible filesystems, by reference, are maintained under '/dev/disk/'.
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info.
#
# After editing this file, run 'systemctl daemon-reload' to update systemd
# units generated from this file.
#
/dev/mapper/cl-root     /                       xfs     defaults        0 0
UUID=5fecb240-379b-4331-ba04-f41338e81a6e /boot                   ext4    defaults        1 2
/dev/mapper/cl-home     /home                   xfs     defaults        0 0
#/dev/mapper/cl-swap     swap                    swap    defaults        0 0

2.3 配置内核参数，将桥接的IPv4流量传递到iptables的链

[root@master01 ~]# cat > /etc/sysctl.d/k8s.conf <<EOF
net.bridge.bridge-nf-call-ip6tables = 1
net.bridge.bridge-nf-call-iptables = 1
EOF
[root@master01 ~]# sysctl --system

2.4 基础包安装

添加阿里源

[root@localhost ~]# rm -rfv /etc/yum.repos.d/*
[root@localhost ~]# curl -o /etc/yum.repos.d/CentOS-Base.repo http://mirrors.aliyun.com/repo/Centos-7.repo

安装常用包

[root@master01 ~]# yum install vim bash-completion net-tools gcc -y

使用aliyun源安装docker-ce

[root@master01 ~]# yum install -y yum-utils device-mapper-persistent-data lvm2
[root@master01 ~]# yum-config-manager --add-repo https://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo
[root@master01 ~]# yum -y install docker-ce

添加aliyundocker仓库加速器

[root@master01 ~]# mkdir -p /etc/docker
[root@master01 ~]# tee /etc/docker/daemon.json <<-'EOF'
{
  "registry-mirrors": ["https://fl791z1h.mirror.aliyuncs.com"]
}
EOF
[root@master01 ~]# systemctl daemon-reload
[root@master01 ~]# systemctl restart docker

2.5 安装k8s

安装kubectl、kubelet、kubeadm (添加阿里kubernetes源)

[root@master01 ~]# cat <<EOF > /etc/yum.repos.d/kubernetes.repo
[kubernetes]
name=Kubernetes
baseurl=https://mirrors.aliyun.com/kubernetes/yum/repos/kubernetes-el7-x86_64/
enabled=1
gpgcheck=1
repo_gpgcheck=1
gpgkey=https://mirrors.aliyun.com/kubernetes/yum/doc/yum-key.gpg https://mirrors.aliyun.com/kubernetes/yum/doc/rpm-package-key.gpg
EOF

安装

[root@master01 ~]# yum install kubectl kubelet kubeadm
[root@master01 ~]# systemctl enable kubelet

3 master机器安装

POD的网段为: 10.122.0.0/16， api server地址就是master本机IP。
这一步很关键，由于kubeadm 默认从官网k8s.grc.io下载所需镜像，国内无法访问，因此需要通过–image-repository指定阿里云镜像仓库地址。

kubeadm init --kubernetes-version=1.20.0  \
--apiserver-advertise-address=192.168.56.101   \
--image-repository registry.aliyuncs.com/google_containers  \
--service-cidr=10.10.0.0/16 --pod-network-cidr=10.122.0.0/16

集群初始化成功后返回如下信息：

Your Kubernetes control-plane has initialized successfully!

To start using your cluster, you need to run the following as a regular user:

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

You should now deploy a pod network to the cluster.
Run "kubectl apply -f [podnetwork].yaml" with one of the options listed at:
  https://kubernetes.io/docs/concepts/cluster-administration/addons/

Then you can join any number of worker nodes by running the following on each as root:

kubeadm join 192.168.56.101:6443 --token wl0fs4.mjpadkvixjzae8j4 \
    --discovery-token-ca-cert-hash sha256:9c13914b176c5622098f47c8392a58657f7cd0a6a15b5814f30c9baaf7536b79

执行

[root@master01 ~]#  mkdir -p $HOME/.kube
[root@master01 ~]# sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
[root@master01 ~]#   sudo chown $(id -u):$(id -g) $HOME/.kube/config
root@master01 ~]# source <(kubectl completion bash)

查看节点，pod
master01 NotReady 需要拉取镜像要等几分钟才会转成Ready

[root@master01 ~]# kubectl get node
NAME                STATUS     ROLES    AGE     VERSION
master01	   NotReady   master   2m29s   v1.18.0
[root@master01 ~]# kubectl get pod --all-namespaces
NAMESPACE     NAME                                        READY   STATUS    RESTARTS   AGE
kube-system   coredns-7ff77c879f-fsj9l                    0/1     Pending   0          2m12s
kube-system   coredns-7ff77c879f-q5ll2                    0/1     Pending   0          2m12s
kube-system   etcd-master01.paas.com                      1/1     Running   0          2m22s
kube-system   kube-apiserver-master01.paas.com            1/1     Running   0          2m22s
kube-system   kube-controller-manager-master01.paas.com   1/1     Running   0          2m22s
kube-system   kube-proxy-th472                            1/1     Running   0          2m12s
kube-system   kube-scheduler-master01.paas.com            1/1     Running   0          2m22s
[root@master01 ~]#

安装calico网络

[root@master01 ~]# kubectl apply -f https://docs.projectcalico.org/manifests/calico.yaml
configmap/calico-config created
customresourcedefinition.apiextensions.k8s.io/bgpconfigurations.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/bgppeers.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/blockaffinities.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/clusterinformations.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/felixconfigurations.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/globalnetworkpolicies.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/globalnetworksets.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/hostendpoints.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/ipamblocks.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/ipamconfigs.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/ipamhandles.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/ippools.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/networkpolicies.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/networksets.crd.projectcalico.org created
clusterrole.rbac.authorization.k8s.io/calico-kube-controllers created
clusterrolebinding.rbac.authorization.k8s.io/calico-kube-controllers created
clusterrole.rbac.authorization.k8s.io/calico-node created
clusterrolebinding.rbac.authorization.k8s.io/calico-node created
daemonset.apps/calico-node created
serviceaccount/calico-node created
deployment.apps/calico-kube-controllers created
serviceaccount/calico-kube-controllers created

问题：

kubectl get cs

[root@master01 ~]# kubectl get cs
scheduler            Unhealthy   Get "http://127.0.0.1:10251/healthz": dial tcp 127.0.0.1:10251: connect: connection refused
controller-manager   Unhealthy   Get "http://127.0.0.1:10252/healthz": dial tcp 127.0.0.1:10252: connect: connection refused

解决：
将两文件里面的“–port=0“ 这行删除” “”
/etc/kubernetes/manifests/kube-controller-manager.yaml
/etc/kubernetes/manifests/kube-scheduler.yaml
重启kubelet服务 systemctl restart kubelet

4 节点机器安装

加入k8s集群

kubeadm join 192.168.56.101:6443 --token wl0fs4.mjpadkvixjzae8j4 \
>     --discovery-token-ca-cert-hash sha256:9c13914b176c5622098f47c8392a58657f7cd0a6a15b5814f30c9baaf7536b79

设置kubectl 客户端可用

复制admin.conf到节点在master主机执行

[root@master01 ~]# scp /etc/kubernetes/admin.conf  node1:/etc/kubernetes/admin.conf
[root@master01 ~]# scp /etc/kubernetes/admin.conf  node2:/etc/kubernetes/admin.conf

节点机器执行

[root@node1 ~]# echo "export KUBECONFIG=/etc/kubernetes/admin.conf" >> ~/.bash_profile
[root@node1 ~]# source ~/.bash_profile

[root@node1 ~]# kubectl get node
NAME       STATUS   ROLES                  AGE    VERSION
master01   Ready    control-plane,master   121m   v1.20.1
node1      Ready    <none>                 88m    v1.20.1
node2      Ready    <none>                 102s   v1.20.1

5 安装kubernetes-dashboard

官方部署dashboard的服务没使用nodeport，将yaml文件下载到本地，在service里添加nodeport

[root@master01 ~]# wget  https://raw.githubusercontent.com/kubernetes/dashboard/v2.0.0-rc7/aio/deploy/recommended.yaml
[root@master01 ~]# vim recommended.yaml
kind: Service
apiVersion: v1
metadata:
  labels:
    k8s-app: kubernetes-dashboard
  name: kubernetes-dashboard
  namespace: kubernetes-dashboard
spec:
  type: NodePort
  ports:
    - port: 443
      targetPort: 8443
      nodePort: 30000
  selector:
    k8s-app: kubernetes-dashboard

[root@master01 ~]# kubectl create -f recommended.yaml
namespace/kubernetes-dashboard created
serviceaccount/kubernetes-dashboard created
service/kubernetes-dashboard created
secret/kubernetes-dashboard-certs created
secret/kubernetes-dashboard-csrf created
secret/kubernetes-dashboard-key-holder created
configmap/kubernetes-dashboard-settings created
role.rbac.authorization.k8s.io/kubernetes-dashboard created
clusterrole.rbac.authorization.k8s.io/kubernetes-dashboard created
rolebinding.rbac.authorization.k8s.io/kubernetes-dashboard created
clusterrolebinding.rbac.authorization.k8s.io/kubernetes-dashboard created
deployment.apps/kubernetes-dashboard created
service/dashboard-metrics-scraper created
deployment.apps/dashboard-metrics-scraper created

获取token

kubectl -n kube-system describe $(kubectl -n kube-system get secret -n kube-system -o name | grep namespace) | grep token

6. 常见问题

问题： k8s network: stat /var/lib/calico/nodename: no such file or directory
（见calico-kube-controllers 0/1 CrashLoopBackOff 状态）
命令：kubectl describe pod calico-kube-controllers-744cfdf676-6jbgn -n kube-system

解决：
安装k8s 的时候残留的文件导致的问题
wget https://docs.projectcalico.org/manifests/calico.yaml

rm -rf /var/lib/calico
rm -rf /etc/cni/net.d/calico*

#重新创建calico
kubectl delete -f calico.yaml
kubectl create -f calico.yaml

问题： calico/node is not ready: BIRD is not ready: BGP not established with 10.117.150.23
（见calico-node 0/1 CrashLoopBackOff 状态）

解决：
// calico.yaml 文件添加以下二行
- name: IP_AUTODETECTION_METHOD
value: “interface=ens.*” # ens 根据实际网卡开头配置

  			- name: CLUSTER_TYPE
              value: "k8s,bgp"
            - name: IP_AUTODETECTION_METHOD
              value: "interface=ens.*"
              #或者 value: "interface=ens160"
            # Auto-detect the BGP IP address.
            - name: IP
              value: "autodetect"
            # Enable IPIP
            - name: CALICO_IPV4POOL_IPIP
              value: "Always"

参考页面
https://www.kubernetes.org.cn/7189.html

swingLau007

关注

0
点赞
踩
3

收藏

觉得还不错? 一键收藏
1
评论
Centos7三台机器安装 k8s

1.机器配置硬件说明CPU2核+内存2G +硬盘10G+系统CentOS Linux release 7.9.2009 (Core)安装k8s，cpu不能少于2核，内存不能少于2G, 否则安装时说提示出错，无法安装。2.软件安装 (每台都执行一次)2.1 修改Hostsvi /etc/hosts192.168.56.101 master01192.168.56.102 node1192.168.56.103 node2修改Hostnam
复制链接

扫一扫