要求 IP 服务
master(2C/4G,cpu核心数要求大于2) 192.168.85.10 docker、kubeadm、kubelet、kubectl、flannel
node01(2C/2G) 192.168.85.20 docker、kubeadm、kubelet、kubectl、flannel
node02(2C/2G) 192.168.85.30 docker、kubeadm、kubelet、kubectl、flannel
Harbor节点(hub.kgc.com) 192.168.85.40 docker、docker-compose、harbor-offline-v1.2.2
  1. 在一切节点上装置Docker和kubeadm
  2. 布置Kubernetes Master
  3. 布置容器网络插件
  4. 布置 Kubernetes Node,将节点参加Kubernetes集群中
  5. 布置 Dashboard Web 页面,可视化查看Kubernetes资源
  6. 布置 Harbor 私有库房,寄存镜像资源

环境预备

一切节点,封闭防火墙规矩,封闭selinux,封闭swap交流
systemctl stop firewalld
systemctl disable firewalld
setenforce 0
sed -i 's/enforcing/disabled/' /etc/selinux/config
iptables -F && iptables -t nat -F && iptables -t mangle -F && iptables -X
swapoff -a						#交流分区必需求封闭
sed -ri 's/.*swap.*/#&/' /etc/fstab		#永久封闭swap分区,&符号在sed命令中代表上次匹配的成果
#加载 ip_vs 模块
for i in $(ls /usr/lib/modules/$(uname -r)/kernel/net/netfilter/ipvs|grep -o "^[^.]*");do echo $i; /sbin/modinfo -F filename $i >/dev/null 2>&1 && /sbin/modprobe $i;done

修正主机名

hostnamectl set-hostname master01
hostnamectl set-hostname node01
hostnamectl set-hostname node02

一切节点修正hosts文件

vim /etc/hosts
192.168.85.10 master01
192.168.85.20 node01
192.168.85.30 node02

调整内核参数

cat > /etc/sysctl.d/kubernetes.conf << EOF
#敞开网桥形式,可将网桥的流量传递给iptables链
net.bridge.bridge-nf-call-ip6tables=1
net.bridge.bridge-nf-call-iptables=1
#封闭ipv6协议
net.ipv6.conf.all.disable_ipv6=1
net.ipv4.ip_forward=1
EOF

收效参数

sysctl --system

一切节点装置docker

yum install -y yum-utils device-mapper-persistent-data lvm2
yum-config-manager --add-repo https://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo 
yum install -y docker-ce docker-ce-cli containerd.io
mkdir /etc/docker
cat > /etc/docker/daemon.json <<EOF
{
  "registry-mirrors": ["https://6ijb8ubo.mirror.aliyuncs.com"],
  "exec-opts": ["native.cgroupdriver=systemd"],
  "log-driver": "json-file",
  "log-opts": {
    "max-size": "100m"
  }
}
EOF
#运用Systemd办理的Cgroup来进行资源操控与办理,由于相对Cgroupfs而言,Systemd限制CPU、内存等资源更加简略和成熟安稳。
#日志运用json-file格式类型存储,巨细为100M,保存在/var/log/containers目录下,便利ELK等日志体系搜集和办理日志。
systemctl daemon-reload
systemctl restart docker.service
systemctl enable docker.service 
docker info | grep "Cgroup Driver"
Cgroup Driver: systemd

云原生kubernetes--单master安装

一切节点装置kubeadm,kubelet和kubectl

界说kubernetes源

cat > /etc/yum.repos.d/kubernetes.repo << EOF
[kubernetes]
name=Kubernetes
baseurl=https://mirrors.aliyun.com/kubernetes/yum/repos/kubernetes-el7-x86_64
enabled=1
gpgcheck=0
repo_gpgcheck=0
gpgkey=https://mirrors.aliyun.com/kubernetes/yum/doc/yum-key.gpg https://mirrors.aliyun.com/kubernetes/yum/doc/rpm-package-key.gpg
EOF
yum install -y kubelet-1.20.15 kubeadm-1.20.15 kubectl-1.20.15

开机自启kubelet

systemctl enable kubelet.service
#K8S经过kubeadm装置出来今后都是以Pod办法存在,即底层是以容器办法运行,所以kubelet必须设置开机自启

布置K8S集群

查看初始化需求的镜像
kubeadm config images list --kubernetes-version 1.20.15

云原生kubernetes--单master安装

在 master 节点上传 v1.20.15.zip 压缩包至 /opt 目录

unzip v1.20.15.zip -d /opt/k8s
cd /opt/k8s/
for i in $(ls *.tar); do docker load -i $i; done

仿制镜像和脚本到 node 节点,并在 node 节点上执行脚本加载镜像文件

scp -r /opt/k8s root@node01:/opt
scp -r /opt/k8s root@node02:/opt

初始化kubeadm

办法一:
kubeadm config print init-defaults > /opt/kubeadm-config.yaml
cd /opt/
vim kubeadm-config.yaml
......
11 localAPIEndpoint:
12   advertiseAddress: 192.168.85.10		#指定master节点的IP地址
13   bindPort: 6443
......
34 kubernetesVersion: v1.20.15				#指定kubernetes版别号
35 networking:
36   dnsDomain: cluster.local
37   podSubnet: "10.244.0.0/16"				#指定pod网段,10.244.0.0/16用于匹配flannel默许网段
38   serviceSubnet: 10.96.0.0/16			#指定service网段
39 scheduler: {}
#结尾再增加以下内容
--- 
apiVersion: kubeproxy.config.k8s.io/v1alpha1
kind: KubeProxyConfiguration
mode: ipvs									#把默许的kube-proxy调度办法改为ipvs形式
kubeadm init --config=kubeadm-config.yaml --upload-certs | tee kubeadm-init.log
#--upload-certs 参数能够在后续执行参加节点时主动分发证书文件
#tee kubeadm-init.log 用以输出日志
//查看 kubeadm-init 日志
less kubeadm-init.log
//kubernetes配置文件目录
ls /etc/kubernetes/
//寄存ca等证书和暗码的目录
ls /etc/kubernetes/pki	
办法二:
kubeadm init \
--apiserver-advertise-address=192.168.85.10 \
--image-repository registry.aliyuncs.com/google_containers \
--kubernetes-version=v1.20.15 \
--service-cidr=10.96.0.0/16 \
--pod-network-cidr=10.244.0.0/16 \
--token-ttl=0
--------------------------------------------------------------------------------------------
初始化集群需运用kubeadm init命令,能够指定具体参数初始化,也能够指定配置文件初始化。
可选参数:
--apiserver-advertise-address:apiserver布告给其他组件的IP地址,一般应该为Master节点的用于集群内部通信的IP地址,0.0.0.0表明节点上一切可用地址
--apiserver-bind-port:apiserver的监听端口,默许是6443
--cert-dir:通讯的ssl证书文件,默许/etc/kubernetes/pki
--control-plane-endpoint:操控台平面的同享终端,能够是负载均衡的ip地址或许dns域名,高可用集群时需求增加
--image-repository:拉取镜像的镜像库房,默许是k8s.gcr.io
--kubernetes-version:指定kubernetes版别
--pod-network-cidr:pod资源的网段,需与pod网络插件的值设置一致。Flannel网络插件的默许为10.244.0.0/16,Calico插件的默许值为192.168.0.0/16;
--service-cidr:service资源的网段
--service-dns-domain:service全域名的后缀,默许是cluster.local
--token-ttl:默许token的有效期为24小时,假如不想过期,能够加上 --token-ttl=0 这个参数
---------------------------------------------------------------------------------------------
办法二初始化后需求修正 kube-proxy 的 configmap,敞开 ipvs
kubectl edit cm kube-proxy -n=kube-system
修正mode: ipvs

提示:

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.85.10:6443 --token rc0kfs.a1sfe3gl4dvopck5 \
    --discovery-token-ca-cert-hash sha256:864fe553c812df2af262b406b707db68b0fd450dc08b34efb73dd5a4771d37a2
设定kubectl
kubectl需经由API server认证及授权后方能执行相应的办理操作,kubeadm 布置的集群为其生成了一个具有办理员权限的认证配置文件 /etc/kubernetes/admin.conf,它可由 kubectl 经过默许的 “$HOME/.kube/config” 的途径进行加载。
mkdir -p $HOME/.kube
cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
chown $(id -u):$(id -g) $HOME/.kube/config
假如 kubectl get cs 发现集群不健康,更改以下两个文件
vim /etc/kubernetes/manifests/kube-scheduler.yaml 
vim /etc/kubernetes/manifests/kube-controller-manager.yaml
# 修正如下内容
把--bind-address=127.0.0.1变成--bind-address=192.168.85.10		#修正成k8s的操控节点master01的ip
把httpGet:字段下的hosts由127.0.0.1变成192.168.80.10(有两处)
#- --port=0					# 查找port=0,把这一行注释掉
systemctl restart kubelet

一切节点布置网络插件flannel

办法一:
//一切节点上传 flannel 镜像 flannel.tar 和网络插件 cni-plugins-linux-amd64-v0.8.6.tgz 到 /opt 目录,master节点上传 kube-flannel.yml 文件
cd /opt
docker load < flannel.tar
mv /opt/cni /opt/cni_bak
mkdir -p /opt/cni/bin
tar zxvf cni-plugins-linux-amd64-v0.8.6.tgz -C /opt/cni/bin
//在 master 节点创立 flannel 资源
kubectl apply -f kube-flannel.yml 
办法二:
kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml
//在 node 节点上执行 kubeadm join 命令参加群集
kubeadm join 192.168.85.10:6443 --token rc0kfs.a1sfe3gl4dvopck5 \
    --discovery-token-ca-cert-hash sha256:864fe553c812df2af262b406b707db68b0fd450dc08b34efb73dd5a4771d37a2
在master节点查看节点状况
kubectl get nodes

云原生kubernetes--单master安装

kubectl get pods -n kube-system

云原生kubernetes--单master安装

测试 pod 资源创立

kubectl create deployment nginx --image=nginx
kubectl get pods -o wide

露出端口提供服务

kubectl expose deployment nginx --port=80 --type=NodePort

云原生kubernetes--单master安装

测试拜访

curl http://node01:31346

云原生kubernetes--单master安装

扩展3个副本

kubectl scale deployment nginx --replicas=3
kubectl get pods -o wide

云原生kubernetes--单master安装

布置 Dashboard

 master01 节点上操作
#上传 recommended.yaml 文件到 /opt/k8s 目录中
cd /opt/k8s
vim recommended.yaml
#默许Dashboard只能集群内部拜访,修正Service为NodePort类型,露出到外部:
kind: Service
apiVersion: v1
metadata:
  labels:
    k8s-app: kubernetes-dashboard
  name: kubernetes-dashboard
  namespace: kubernetes-dashboard
spec:
  ports:
    - port: 443
      targetPort: 8443
      nodePort: 30001     #增加
  type: NodePort          #增加
  selector:
    k8s-app: kubernetes-dashboard
kubectl apply -f recommended.yaml
#创立service account并绑定默许cluster-admin办理员集群人物
kubectl create serviceaccount dashboard-admin -n kube-system
kubectl create clusterrolebinding dashboard-admin --clusterrole=cluster-admin --serviceaccount=kube-system:dashboard-admin
kubectl describe secrets -n kube-system $(kubectl -n kube-system get secret | awk '/dashboard-admin/{print $1}')
#运用输出的token登录Dashboard
https://192.168.85.20:30001

云原生kubernetes--单master安装

装置Harbor私有库房

修正主机名

hostnamectl set-hostname hub.aa.com

一切节点加上主机名映射

echo '192.168.85.40 hub.aa.com' >> /etc/hosts

装置 docker

yum install -y yum-utils device-mapper-persistent-data lvm2
yum-config-manager --add-repo https://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo 
yum install -y docker-ce docker-ce-cli containerd.io
mkdir /etc/docker
cat > /etc/docker/daemon.json <<EOF
{
  "registry-mirrors": ["https://6ijb8ubo.mirror.aliyuncs.com"],
  "exec-opts": ["native.cgroupdriver=systemd"],
  "log-driver": "json-file",
  "log-opts": {
    "max-size": "100m"
  },
  "insecure-registries": ["https://hub.aa.com"]
}
EOF

重启docker

systemctl start docker
systemctl enable docker

一切 node 节点都修正 docker 配置文件,加上私有库房配置

cat > /etc/docker/daemon.json <<EOF
{
  "registry-mirrors": ["https://6ijb8ubo.mirror.aliyuncs.com"],
  "exec-opts": ["native.cgroupdriver=systemd"],
  "log-driver": "json-file",
  "log-opts": {
    "max-size": "100m"
  },
  "insecure-registries": ["https://hub.kgc.com"]
}
EOF
systemctl daemon-reload
systemctl restart docker

装置 Harbor

上传 harbor-offline-installer-v1.2.2.tgz 和 docker-compose 文件到 /opt 目录
cd /opt
cp docker-compose /usr/local/bin/
chmod +x /usr/local/bin/docker-compose
tar zxvf harbor-offline-installer-v1.2.2.tgz
cd harbor/
vim harbor.cfg
5  hostname = hub.aa.com
9  ui_url_protocol = https
24 ssl_cert = /data/cert/server.crt
25 ssl_cert_key = /data/cert/server.key
59 harbor_admin_password = Harbor12345

生成证书

mkdir -p /data/cert
cd /data/cert
#生成私钥
openssl genrsa -des3 -out server.key 2048
输入两遍暗码:123456
#生成证书签名请求文件
openssl req -new -key server.key -out server.csr
输入私钥暗码:123456
输入国家名:CN
输入省名:BJ
输入市名:BJ
输入组织名:KGC
输入组织名:KGC
输入域名:hub.kgc.com
输入办理员邮箱:admin@aa.com
其它悉数直接回车
#备份私钥
cp server.key server.key.org
#铲除私钥暗码
openssl rsa -in server.key.org -out server.key
输入私钥暗码:123456
#签名证书
openssl x509 -req -days 1000 -in server.csr -signkey server.key -out server.crt
chmod +x /data/cert/*
cd /opt/harbor/
./install.sh
在本地运用火狐浏览器拜访:https://hub.aa.com
增加破例 -> 确认安全破例
用户名:admin
暗码:Harbor12345
//在一个node节点上登录harbor
docker login -u admin -p Harbor12345 https://hub.aa.com
上传镜像
docker tag nginx:latest hub.kgc.com/library/nginx:v1
docker push hub.aa.com/library/nginx:v1
//在master节点上删除之前创立的nginx资源
kubectl delete deployment nginx
kubectl run nginx-deployment --image=hub.kgc.com/library/nginx:v1 --port=80 --replicas=3
kubectl expose deployment nginx-deployment --port=30000 --target-port=80
kubectl get svc,pods

云原生kubernetes--单master安装

yum install ipvsadm -y
ipvsadm -Ln
curl 10.96.222.161:30000
kubectl edit svc nginx-deployment
25   type: NodePort						#把调度策略改成NodePort

云原生kubernetes--单master安装

浏览器拜访:
192.168.85.10:32340
192.168.85.20:32340
192.168.85.30:32340
#将cluster-admin人物权限颁发用户system:anonymous
kubectl create clusterrolebinding cluster-system-anonymous --clusterrole=cluster-admin --user=system:anonymous

内核参数优化计划

cat > /etc/sysctl.d/kubernetes.conf <<EOF
net.bridge.bridge-nf-call-iptables=1
net.bridge.bridge-nf-call-ip6tables=1
net.ipv4.ip_forward=1
net.ipv4.tcp_tw_recycle=0
vm.swappiness=0									#禁止运用 swap 空间,只有当体系内存不足(OOM)时才允许运用它
vm.overcommit_memory=1							#不查看物理内存是否够用
vm.panic_on_oom=0								#敞开 OOM
fs.inotify.max_user_instances=8192
fs.inotify.max_user_watches=1048576
fs.file-max=52706963							#指定最大文件句柄数
fs.nr_open=52706963								#仅4.4以上版别支撑
net.ipv6.conf.all.disable_ipv6=1
net.netfilter.nf_conntrack_max=2310720
EOF

初始化失利,进行的操作

kubeadm reset -f
ipvsadm --clear 
rm -rf ~/.kube
再次进行初始化