centos7使用kubeadm搭建kubernetes集羣
1、本地實驗環境準備
- 服務器虛擬機準備
| IP | CPU | 內存 | hostname |
|---|---|---|---|
| 192.168.222.129 | >=2c | >=2G | master |
| 192.168.222.130 | >=2c | >=2G | node1 |
| 192.168.222.131 | >=2c | >=2G | node2 |
本實驗我這裏用的虛擬機是vmware workstation建立的，個人機器配置較低，因此master給了4G 4C，node每一個給了4G 4C，你們根據本身的資源狀況，按照上面給的建議最低值建立便可。
注意：hostname不能有大寫字母，好比Master這樣的。html
1. 軟件版本
系統：CentOS7.5.1804 Kubernetes：1.15.3 docker-ce版本：19.03.1
2. 環境初始化操做
2.1 配置hostname
## 192.168.222.129 hostnamectl set-hostname master ## 192.168.222.130 hostnamectl set-hostname node1 ## 192.168.222.131 hostnamectl set-hostname node2
2.2 配置三臺虛擬機的/etc/hosts
echo "192.168.222.129 master" >> /etc/hosts echo "192.168.222.130 node1" >> /etc/hosts echo "192.168.222.131 node2" >> /etc/hosts
2.3 安裝必要軟件以及升級全部軟件,關閉防火牆、selinux、swap
yum -y install vim-enhanced wget curl net-tools conntrack-tools bind-utils socat ipvsadm ipset yum -y update ## 停防火牆 systemctl stop firewalld systemctl disable firewalld ## 關閉Selinux sed -i 's#SELINUX=enforcing#SELINUX=disabled#g' /etc/sysconfig/selinux sed -i 's#SELINUX=enforcing#SELINUX=disabled#g' /etc/selinux/config ## 關閉沒必要要服務 systemctl disable auditd systemctl disable postfix systemctl disable irqbalance systemctl disable remote-fs systemctl disable tuned systemctl disable rhel-configure systemctl disable firewalld ## 安裝kernel-lt(kernel 4.4.178) rpm --import https://www.elrepo.org/RPM-GPG-KEY-elrepo.org yum -y install https://www.elrepo.org/elrepo-release-7.0-3.el7.elrepo.noarch.rpm yum --enablerepo=elrepo-kernel install kernel-lt -y grub2-set-default 0 grub2-mkconfig -o /etc/grub2.cfg ## 優化內核 cat >>/etc/sysctl.conf <<EOF net.ipv4.ip_forward = 1 vm.swappiness = 0 net.bridge.bridge-nf-call-ip6tables = 1 net.bridge.bridge-nf-call-iptables = 1 net.ipv4.tcp_max_syn_backlog = 65536 net.core.netdev_max_backlog = 32768 net.core.somaxconn = 32768 net.core.wmem_default = 8388608 net.core.rmem_default = 8388608 net.core.rmem_max = 16777216 net.core.wmem_max = 16777216 net.ipv4.tcp_timestamps = 0 net.ipv4.tcp_synack_retries = 2 net.ipv4.tcp_syn_retries = 2 net.ipv4.tcp_tw_recycle = 1 net.ipv4.tcp_tw_reuse = 1 net.ipv4.tcp_mem = 94500000 915000000 927000000 net.ipv4.tcp_max_orphans = 3276800 net.ipv4.ip_local_port_range = 1024 65535 EOF sysctl -p ## 修改文件打開數 cat >>/etc/security/limits.conf <<EOF * soft memlock unlimited * hard memlock unlimited * soft nofile 65535 * hard nofile 65535 * soft nproc 65535 * hard nproc 65535 EOF ## 系統關閉使用交換內存 echo "swapoff -a">>/etc/rc.local chmod +x /etc/rc.local swapoff -a ## 註釋掉/etc/fstab的swap行 # /dev/mapper/centos-swap swap swap defaults 0 0 ## 建立k8s.conf vim /etc/sysctl.d/k8s.conf ## 寫入以下配置 net.bridge.bridge-nf-call-ip6tables = 1 net.bridge.bridge-nf-call-iptables = 1 ## 加載br_netfilter modprobe br_netfilter sysctl -p /etc/sysctl.d/k8s.conf
3. 配置CentOS YUM源
## 配置國內tencent yum源地址、epel源地址、Kubernetes源地址 mkdir -p /etc/yum.repo.d/repo.bak mv /etc/yum.repo.d/*.repo /etc/yum.repo.d/repo.bak wget -O /etc/yum.repos.d/CentOS-Base.repo http://mirrors.cloud.tencent.com/repo/centos7_base.repo wget -O /etc/yum.repos.d/epel.repo http://mirrors.cloud.tencent.com/repo/epel-7.repo
配置國內Kubernetes源地址
vim /etc/yum.repos.d/kubernetes.reponode
[kubernetes] name=Kubernetes Repo baseurl=https://mirrors.aliyun.com/kubernetes/yum/repos/kubernetes-el7-x86_64/ gpgcheck=0 gpgkey=https://mirrors.aliyun.com/kubernetes/yum/doc/yum-key.gpg enabled=1
yum clean all && yum makecache
4. 安裝一些依賴軟件包
yum install -y conntrack ipvsadm ipset jq sysstat curl iptables libseccomp bash-completion yum-utils device-mapper-persistent-data lvm2 net-tools conntrack-tools vim libtool-ltdl
5. 時間同步配置
yum install chrony –y systemctl enable chronyd.service && systemctl start chronyd.service && systemctl status chronyd.service chronyc sources
運行date命令看下系統時間，過一下子時間就會同步。若是同步失敗檢查是否是由於公司內部網致使沒法同步時間linux
6. 以上操做後，所有重啓一下。
7. 安裝docker
## 配置docker yum 源 cd /etc/yum.repos.d && wget https://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo ## 查看docker-ce的可用資源 yum list docker-ce.x86_64 --showduplicates | sort -r
會顯示以下的docker-ce信息git
Repository cr is listed more than once in the configuration Repository fasttrack is listed more than once in the configuration 已加載插件：fastestmirror, langpacks 已安裝的軟件包 可安裝的軟件包 Loading mirror speeds from cached hostfile * elrepo: mirrors.tuna.tsinghua.edu.cn docker-ce.x86_64 3:19.03.1-3.el7 docker-ce-stable docker-ce.x86_64 3:19.03.1-3.el7 @docker-ce-stable docker-ce.x86_64 3:19.03.0-3.el7 docker-ce-stable docker-ce.x86_64 3:18.09.8-3.el7 docker-ce-stable docker-ce.x86_64 3:18.09.7-3.el7 docker-ce-stable docker-ce.x86_64 3:18.09.6-3.el7 docker-ce-stable docker-ce.x86_64 3:18.09.5-3.el7 docker-ce-stable docker-ce.x86_64 3:18.09.4-3.el7 docker-ce-stable docker-ce.x86_64 3:18.09.3-3.el7 docker-ce-stable docker-ce.x86_64 3:18.09.2-3.el7 docker-ce-stable docker-ce.x86_64 3:18.09.1-3.el7 docker-ce-stable docker-ce.x86_64 3:18.09.0-3.el7 docker-ce-stable docker-ce.x86_64 18.06.3.ce-3.el7 docker-ce-stable docker-ce.x86_64 18.06.2.ce-3.el7 docker-ce-stable docker-ce.x86_64 18.06.1.ce-3.el7 docker-ce-stable docker-ce.x86_64 18.06.0.ce-3.el7 docker-ce-stable docker-ce.x86_64 18.03.1.ce-1.el7.centos docker-ce-stable docker-ce.x86_64 18.03.0.ce-1.el7.centos docker-ce-stable docker-ce.x86_64 17.12.1.ce-1.el7.centos docker-ce-stable docker-ce.x86_64 17.12.0.ce-1.el7.centos docker-ce-stable docker-ce.x86_64 17.09.1.ce-1.el7.centos docker-ce-stable docker-ce.x86_64 17.09.0.ce-1.el7.centos docker-ce-stable docker-ce.x86_64 17.06.2.ce-1.el7.centos docker-ce-stable docker-ce.x86_64 17.06.1.ce-1.el7.centos docker-ce-stable docker-ce.x86_64 17.06.0.ce-1.el7.centos docker-ce-stable docker-ce.x86_64 17.03.3.ce-1.el7 docker-ce-stable docker-ce.x86_64 17.03.2.ce-1.el7.centos docker-ce-stable docker-ce.x86_64 17.03.1.ce-1.el7.centos docker-ce-stable docker-ce.x86_64 17.03.0.ce-1.el7.centos docker-ce-stable
選擇你想要得版本，我使用了最新版本
yum -y install docker-ce
配置鏡像加速器和docker數據存放路徑
vim /etc/docker/daemon.json
寫入以下配置github
{
"registry-mirrors": ["https://q2hy3fzi.mirror.aliyuncs.com"],
"graph": "/tol/docker-data" ,
"exec-opts":["native.cgroupdriver=systemd"]
}
設置自啓動
systemctl enable docker && systemctl start docker
8. 安裝 kubeadm、kubelet、kubectl K8S_VERSION=v1.15.3
cat <<EOF > /etc/yum.repos.d/kubernetes.repo
[kubernetes]
name=Kubernetes
baseurl=http://mirrors.aliyun.com/kubernetes/yum/repos/kubernetes-el7-x86_64
enabled=1
gpgcheck=0
repo_gpgcheck=0
gpgkey=http://mirrors.aliyun.com/kubernetes/yum/doc/yum-key.gpg
http://mirrors.aliyun.com/kubernetes/yum/doc/rpm-package-key.gpg
EOF
yum install -y kubeadm kubelet kubectl
kubelet --version //v1.15.3
kubelet啓動設置
vim /etc/sysconfig/kubelet
寫入以下配置docker
KUBELET_EXTRA_ARGS="--fail-swap-on=false"
再重啓shell
systemctl daemon-reload
9. master節點設置(192.168.222.129)
下載相關鏡像
#!/bin/bash # master 節點 shell K8S_VERSION=v1.15.3 ETCD_VERSION=3.3.10 DNS_VERSION=1.3.1 PAUSE_VERSION=3.1 FLANNEL_VERSION=v0.11.0-amd64 DASHBOARD_VERSION=v1.10.1 // 下載鏡像 docker pull registry.cn-hangzhou.aliyuncs.com/google_containers/kube-apiserver:$K8S_VERSION docker pull registry.cn-hangzhou.aliyuncs.com/google_containers/kube-controller-manager:$K8S_VERSION docker pull registry.cn-hangzhou.aliyuncs.com/google_containers/kube-scheduler:$K8S_VERSION docker pull registry.cn-hangzhou.aliyuncs.com/google_containers/kube-proxy:$K8S_VERSION docker pull registry.cn-hangzhou.aliyuncs.com/google_containers/pause:$PAUSE_VERSION docker pull registry.cn-hangzhou.aliyuncs.com/google_containers/etcd:$ETCD_VERSION docker pull registry.cn-hangzhou.aliyuncs.com/google_containers/coredns:$DNS_VERSION docker pull jmgao1983/flannel:$FLANNEL_VERSION docker pull siriuszg/kubernetes-dashboard-amd64:$DASHBOARD_VERSION # 修改tag docker tag registry.cn-hangzhou.aliyuncs.com/google_containers/kube-apiserver:$K8S_VERSION k8s.gcr.io/kube-apiserver:$K8S_VERSION docker tag registry.cn-hangzhou.aliyuncs.com/google_containers/kube-controller-manager:$K8S_VERSION k8s.gcr.io/kube-controller-manager:$K8S_VERSION docker tag registry.cn-hangzhou.aliyuncs.com/google_containers/kube-scheduler:$K8S_VERSION k8s.gcr.io/kube-scheduler:$K8S_VERSION docker tag registry.cn-hangzhou.aliyuncs.com/google_containers/kube-proxy:$K8S_VERSION k8s.gcr.io/kube-proxy:$K8S_VERSION docker tag registry.cn-hangzhou.aliyuncs.com/google_containers/pause:$PAUSE_VERSION k8s.gcr.io/pause:$PAUSE_VERSION docker tag registry.cn-hangzhou.aliyuncs.com/google_containers/etcd:$ETCD_VERSION k8s.gcr.io/etcd:$ETCD_VERSION docker tag registry.cn-hangzhou.aliyuncs.com/google_containers/coredns:$DNS_VERSION k8s.gcr.io/coredns:$DNS_VERSION docker tag jmgao1983/flannel:$FLANNEL_VERSION quay.io/coreos/flannel:$FLANNEL_VERSION docker tag siriuszg/kubernetes-dashboard-amd64:$DASHBOARD_VERSION k8s.gcr.io/kubernetes-dashboard-amd64:$DASHBOARD_VERSION #刪除冗餘的images docker rmi registry.cn-hangzhou.aliyuncs.com/google_containers/kube-apiserver:$K8S_VERSION docker rmi registry.cn-hangzhou.aliyuncs.com/google_containers/kube-controller-manager:$K8S_VERSION docker rmi registry.cn-hangzhou.aliyuncs.com/google_containers/kube-scheduler:$K8S_VERSION docker rmi registry.cn-hangzhou.aliyuncs.com/google_containers/kube-proxy:$K8S_VERSION docker rmi registry.cn-hangzhou.aliyuncs.com/google_containers/pause:$PAUSE_VERSION docker rmi registry.cn-hangzhou.aliyuncs.com/google_containers/etcd:$ETCD_VERSION docker rmi registry.cn-hangzhou.aliyuncs.com/google_containers/coredns:$DNS_VERSION docker rmi jmgao1983/flannel:$FLANNEL_VERSION docker rmi siriuszg/kubernetes-dashboard-amd64:$DASHBOARD_VERSION
集羣安裝初始化(192.168.222.129)
## 初始化命令 kubeadm init --kubernetes-version=v1.15.3 --pod-network-cidr=10.244.0.0/16 --ignore-preflight-errors=Swap
這時候出現以下信息代表安裝成功json
Your Kubernetes master 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/
You can now join any number of machines by running the following on each node
as root:
kubeadm join 192.168.222.129:6443 --token 981it6.k4kqs2i73e1bfd1p \
--discovery-token-ca-cert-hash sha256:5cc5c1c2ace7b720a178840c951b2a05c679d26b8d6a1cfc81aa7e006e6a6ef9
按照上面的提示執行推薦操做vim
mkdir -p $HOME/.kube sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config sudo chown $(id -u):$(id -g) $HOME/.kube/config
查看集羣健康情況
kubectl get cs
集羣安裝過程當中遇到問題，重置操做（報錯時使用,不報錯不用）
kubeadm reset
安裝網絡插件
kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml
查看集羣中的組件運行狀態
kubectl get pods --all-namespaces
10. node節點設置(192.168.222.130和192.168.222.131子節點配置)
下載鏡像
#!/bin/bash # node 節點 shell K8S_VERSION=v1.15.3 ETCD_VERSION=3.3.10 DNS_VERSION=1.3.1 PAUSE_VERSION=3.1 FLANNEL_VERSION=v0.11.0-amd64 DASHBOARD_VERSION=v1.10.1 ## node 安裝插件 docker pull registry.cn-hangzhou.aliyuncs.com/google_containers/kube-proxy:$K8S_VERSION docker pull registry.cn-hangzhou.aliyuncs.com/google_containers/pause:$PAUSE_VERSION docker pull jmgao1983/flannel:v0.11.0-amd64 docker pull siriuszg/kubernetes-dashboard-amd64:$DASHBOARD_VERSION docker tag registry.cn-hangzhou.aliyuncs.com/google_containers/kube-proxy:$K8S_VERSION k8s.gcr.io/kube-proxy:$K8S_VERSION docker tag registry.cn-hangzhou.aliyuncs.com/google_containers/pause:$PAUSE_VERSION k8s.gcr.io/pause:$PAUSE_VERSION docker tag jmgao1983/flannel:$FLANNEL_VERSION quay.io/coreos/flannel:$FLANNEL_VERSION docker tag siriuszg/kubernetes-dashboard-amd64:$DASHBOARD_VERSION k8s.gcr.io/kubernetes-dashboard-amd64:$DASHBOARD_VERSION docker rmi jmgao1983/flannel:$FLANNEL_VERSION docker rmi registry.cn-hangzhou.aliyuncs.com/google_containers/pause:$PAUSE_VERSION docker rmi registry.cn-hangzhou.aliyuncs.com/google_containers/kube-proxy:$K8S_VERSION docker rmi siriuszg/kubernetes-dashboard-amd64:$DASHBOARD_VERSION
加入節點
這裏的信息在主節點初始化完成後會出現，按照本身初始化完後的信息操做，這裏僅供參考centos
kubeadm join 192.168.222.129:6443 --token 9ump71.6fnndushlwn87fnf \
--discovery-token-ca-cert-hash sha256:addb0cd073a460331fe4cadd1f02c69e9b1bdad4e62188fae788ff65e0a8fb11 --ignore-preflight-errors=Swap
出現下面的信息代表子節點加入主節點成功,可使用該命令kubectl get nodes查看
This node has joined the cluster: * Certificate signing request was sent to master and a response was received. * The Kubelet was informed of the new secure connection details. Run 'kubectl get nodes' on the master to see this node join the cluster.
若是執行上述命令報The connection to the server localhost:8080 was refused - did you specify the right host or port?
操做以下
1. 將主節點中的【/etc/kubernetes/admin.conf】文件拷貝到從節點相同目錄下 2. echo "export KUBECONFIG=/etc/kubernetes/admin.conf" >> ~/.bash_profile 3. source ~/.bash_profile
11. 安裝 dashboard組件(我是在主節點上操做的)
配置dashboard
kubectl create -f https://raw.githubusercontent.com/kubernetes/dashboard/v2.0.0-beta1/aio/deploy/recommended.yaml
集羣配置，生成瀏覽器證書(這些證書在後面瀏覽器打開dashboard時須要導入)
# 生成client-certificate-data
grep 'client-certificate-data' ~/.kube/config | head -n 1 | awk '{print $2}' | base64 -d >> kubecfg.crt
# 生成client-key-data
grep 'client-key-data' ~/.kube/config | head -n 1 | awk '{print $2}' | base64 -d >> kubecfg.key
# 生成p12
openssl pkcs12 -export -clcerts -inkey kubecfg.key -in kubecfg.crt -out kubecfg.p12 -name "kubernetes-client"
# 導入證書後瀏覽器重啓
建立admin-user帳號，並放在kube-system名稱空間下
vim admin-user.yaml
寫入以下配置
apiVersion: v1 kind: ServiceAccount metadata: name: admin-user namespace: kube-system
使用該命令加載配置
kubectl create -f admin-user.yaml
綁定角色
vim admin-user-role-binding.yaml
寫入以下配置
apiVersion: rbac.authorization.k8s.io/v1beta1 kind: ClusterRoleBinding metadata: name: admin-user roleRef: apiGroup: rbac.authorization.k8s.io kind: ClusterRole name: cluster-admin subjects: - kind: ServiceAccount name: admin-user namespace: kube-system
使用該命令加載配置
kubectl create -f admin-user-role-binding.yaml
登陸dashboard
在瀏覽器中訪問以下url
https://127.0.0.1:6443/api/v1/namespaces/kubernetes-dashboard/services/https:kubernetes-dashboard:/proxy/
在打開的頁面中選擇token方式,獲取token的方式以下
kubectl -n kube-system describe secret $(kubectl -n kube-system get secret | grep admin-user | awk '{print $1}')
12. 集成Heapster
Heapster是容器集羣監控和性能分析工具
執行命令
kubectl create -f http://mirror.faasx.com/kubernetes/heapster/deploy/kube-config/influxdb/influxdb.yaml kubectl create -f http://mirror.faasx.com/kubernetes/heapster/deploy/kube-config/influxdb/grafana.yaml kubectl create -f http://mirror.faasx.com/kubernetes/heapster/deploy/kube-config/influxdb/heapster.yaml kubectl create -f http://mirror.faasx.com/kubernetes/heapster/deploy/kube-config/rbac/heapster-rbac.yaml
當pod的狀態全都變成了running，則可以使用。
參考
Kubeadm安裝Kubernetes 1.15.1
kubeadm 虛擬機實踐
相關文章
- 1. kubeadm 搭建 Kubernetes 集羣
- 2. kubeadm搭建kubernetes-1.13.2集羣
- 3. centos7使用kubeadm安裝kubernetes集羣
- 4. 利用kubeadm搭建kubernetes集羣
- 5. Google雲上用kubeadm搭建kubernetes集羣
- 6. 使用 kubeadm 構建 kubernetes 集羣.md
- 7. 使用 kubeadm 創建一個 kubernetes 集羣
- 8. 使用kubeadm建立Kubernetes集羣
- 9. 搭建自己的集羣，使用 kubeadm 搭建自己的 kubernetes 集羣
- 10. 本地kubeadm搭建kubernetes集羣
- 更多相關文章...
- • Swarm 集羣管理 - Docker教程
- • Swift 環境搭建 - Swift 教程
- • Composer 安裝與使用
- • 適用於PHP初學者的學習線路和建議
相關標籤/搜索
每日一句
-
每一个你不满意的现在，都有一个你没有努力的曾经。
最新文章
- 1. Appium入門
- 2. Spring WebFlux 源碼分析(2)-Netty 服務器啓動服務流程 --TBD
- 3. wxpython入門第六步（高級組件）
- 4. CentOS7.5安裝SVN和可視化管理工具iF.SVNAdmin
- 5. jedis 3.0.1中JedisPoolConfig對象缺少setMaxIdle、setMaxWaitMillis等方法，問題記錄
- 6. 一步一圖一代碼，一定要讓你真正徹底明白紅黑樹
- 7. 2018-04-12—（重點）源碼角度分析Handler運行原理
- 8. Spring AOP源碼詳細解析
- 9. Spring Cloud（1）
- 10. python簡單爬去油價信息發送到公衆號
歡迎關注本站公眾號,獲取更多信息
相關文章
- 1. kubeadm 搭建 Kubernetes 集羣
- 2. kubeadm搭建kubernetes-1.13.2集羣
- 3. centos7使用kubeadm安裝kubernetes集羣
- 4. 利用kubeadm搭建kubernetes集羣
- 5. Google雲上用kubeadm搭建kubernetes集羣
- 6. 使用 kubeadm 構建 kubernetes 集羣.md
- 7. 使用 kubeadm 創建一個 kubernetes 集羣
- 8. 使用kubeadm建立Kubernetes集羣
- 9. 搭建自己的集羣，使用 kubeadm 搭建自己的 kubernetes 集羣
- 10. 本地kubeadm搭建kubernetes集羣