使用Kubeadm在CentOS7.2上部署Kubernetes集群的方法
更新時(shí)間：2018年03月09日 09:13:56 作者：Jackson_csdn
本篇文章主要介紹了使用Kubeadm在CentOS7.2上部署Kubernetes集群的方法，小編覺得挺不錯(cuò)的，現(xiàn)在分享給大家，也給大家做個(gè)參考。一起跟隨小編過來看看吧
本文參考kubernetes官網(wǎng)文章Installing Kubernetes on Linux with kubeadm在CentOS7.2使用Kubeadm部署Kuebernetes集群，解決了一些在按照該文檔部署時(shí)遇到的問題。
操作系統(tǒng)版本
# cat /etc/redhat-release CentOS Linux release 7.2.1511 (Core)
內(nèi)核版本
# uname -r 3.10.0-327.el7.x86_64
集群節(jié)點(diǎn)
192.168.120.122 kube-master 192.168.120.123 kube-agent1 192.168.120.124 kube-agent2 192.168.120.125 kube-agent3
即該集群包含一個(gè)控制節(jié)點(diǎn)和三個(gè)工作節(jié)點(diǎn)。
部署前的準(zhǔn)備
配置可以訪問google相關(guān)網(wǎng)站
這種部署方式使用的軟件包由google相關(guān)源提供，因此集群節(jié)點(diǎn)必須能夠訪問外網(wǎng)，至于如何配置請(qǐng)自行解決。
關(guān)閉防火墻
# systemctl stop firewalld.service && systemctl disable firewalld.service
禁用SELinux
# setenforce 0 # sed -i.bak 's/SELINUX=enforcing/SELINUX=permissive/' /etc/selinux/config
配置yum源
# cat <<EOF > /etc/yum.repos.d/kubernetes.repo
[kubernetes]
name=Kubernetes
baseurl=https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64
enabled=1
gpgcheck=1
repo_gpgcheck=1
gpgkey=https://packages.cloud.google.com/yum/doc/yum-key.gpg
https://packages.cloud.google.com/yum/doc/rpm-package-key.gpg
EOF
安裝kubelet和kubeadm
在所有節(jié)點(diǎn)上安裝以下軟件包：
# yum install -y docker kubelet kubeadm kubectl kubernetes-cni # systemctl enable docker && systemctl start docker # systemctl enable kubelet && systemctl start kubelet
然后設(shè)置內(nèi)核參數(shù)：
# sysctl net.bridge.bridge-nf-call-iptables=1 # sysctl net.bridge.bridge-nf-call-ip6tables=1
初始化控制節(jié)點(diǎn)
# kubeadm init --pod-network-cidr=10.244.0.0/16
因?yàn)樵谠摷褐袑⑹褂胒lannel搭建pod網(wǎng)絡(luò)，因此必須添加–pod-network-cidr參數(shù)。
注意：初始化較慢，因?yàn)樵撨^程會(huì)pull一些docker image。
該命令的輸出如下：
Initializing your master... [kubeadm] WARNING: kubeadm is in beta, please do not use it for production clusters. [init] Using Kubernetes version: v1.6.4 [init] Using Authorization mode: RBAC [preflight] Running pre-flight checks [certificates] Generated CA certificate and key. [certificates] Generated API server certificate and key. [certificates] API Server serving cert is signed for DNS names [kube-master kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 192.168.120.122] [certificates] Generated API server kubelet client certificate and key. [certificates] Generated service account token signing key and public key. [certificates] Generated front-proxy CA certificate and key. [certificates] Generated front-proxy client certificate and key. [certificates] Valid certificates and keys now exist in "/etc/kubernetes/pki" [kubeconfig] Wrote KubeConfig file to disk: "/etc/kubernetes/admin.conf" [kubeconfig] Wrote KubeConfig file to disk: "/etc/kubernetes/kubelet.conf" [kubeconfig] Wrote KubeConfig file to disk: "/etc/kubernetes/controller-manager.conf" [kubeconfig] Wrote KubeConfig file to disk: "/etc/kubernetes/scheduler.conf" [apiclient] Created API client, waiting for the control plane to become ready [apiclient] All control plane components are healthy after 1377.560339 seconds [apiclient] Waiting for at least one node to register [apiclient] First node has registered after 6.039626 seconds [token] Using token: 60bc68.e94800f3c5c4c2d5 [apiconfig] Created RBAC rules [addons] Created essential addon: kube-proxy [addons] Created essential addon: kube-dns Your Kubernetes master has initialized successfully! To start using your cluster, you need to run (as a regular user): sudo cp /etc/kubernetes/admin.conf $HOME/ sudo chown $(id -u):$(id -g) $HOME/admin.conf export KUBECONFIG=$HOME/admin.conf You should now deploy a pod network to the cluster. Run "kubectl apply -f [podnetwork].yaml" with one of the options listed at: http://kubernetes.io/docs/admin/addons/ You can now join any number of machines by running the following on each node as root: kubeadm join --token <token> 192.168.120.122:6443
觀察控制節(jié)點(diǎn)的docker image：
# docker images REPOSITORY TAG IMAGE ID CREATED SIZE gcr.io/google_containers/kube-apiserver-amd64 v1.6.4 4e3810a19a64 2 days ago 150.6 MB gcr.io/google_containers/kube-controller-manager-amd64 v1.6.4 0ea16a85ac34 2 days ago 132.8 MB gcr.io/google_containers/kube-proxy-amd64 v1.6.4 e073a55c288b 2 days ago 109.2 MB gcr.io/google_containers/kube-scheduler-amd64 v1.6.4 1fab9be555e1 2 days ago 76.75 MB gcr.io/google_containers/etcd-amd64 3.0.17 243830dae7dd 12 weeks ago 168.9 MB gcr.io/google_containers/pause-amd64 3.0 99e59f495ffa 12 months ago 746.9 kB
按照初始化命令的提示執(zhí)行以下操作：
# cp /etc/kubernetes/admin.conf $HOME/ # chown $(id -u):$(id -g) $HOME/admin.conf # export KUBECONFIG=$HOME/admin.conf
隔離控制節(jié)點(diǎn)
# kubectl taint nodes --all node-role.kubernetes.io/master- node "kube-master" tainted
安裝pod網(wǎng)絡(luò)
# kubectl apply -f flannel/Documentation/kube-flannel-rbac.yml clusterrole "flannel" created clusterrolebinding "flannel" created # kubectl apply -f flannel/Documentation/kube-flannel.yml serviceaccount "flannel" created configmap "kube-flannel-cfg" created daemonset "kube-flannel-ds" created
可以通過git clone flannel倉(cāng)庫(kù)：
# git clone https://github.com/coreos/flannel.git
添加工作節(jié)點(diǎn)
# kubeadm join --token <token> 192.168.120.122:6443
該操作輸出如下：
[kubeadm] WARNING: kubeadm is in beta, please do not use it for production clusters. [preflight] Running pre-flight checks [discovery] Trying to connect to API Server "192.168.120.122:6443" [discovery] Created cluster-info discovery client, requesting info from "https://192.168.120.122:6443" [discovery] Cluster info signature and contents are valid, will use API Server "https://192.168.120.122:6443" [discovery] Successfully established connection with API Server "192.168.120.122:6443" [bootstrap] Detected server version: v1.6.4 [bootstrap] The server supports the Certificates API (certificates.k8s.io/v1beta1) [csr] Created API client to obtain unique certificate for this node, generating keys and certificate signing request [csr] Received signed certificate from the API server, generating KubeConfig... [kubeconfig] Wrote KubeConfig file to disk: "/etc/kubernetes/kubelet.conf" Node join complete: * Certificate signing request sent to master and response received. * Kubelet informed of new secure connection details. Run 'kubectl get nodes' on the master to see this machine join.
在控制節(jié)點(diǎn)觀察集群狀態(tài)
# kubectl get nodes NAME STATUS AGE VERSION kube-agent1 Ready 16m v1.6.3 kube-agent2 Ready 16m v1.6.3 kube-agent3 Ready 16m v1.6.3 kube-master Ready 37m v1.6.3 # kubectl get pods --all-namespaces -o wide NAMESPACE NAME READY STATUS RESTARTS AGE IP NODE kube-system etcd-kube-master 1/1 Running 0 32m 192.168.120.122 kube-master kube-system kube-apiserver-kube-master 1/1 Running 7 32m 192.168.120.122 kube-master kube-system kube-controller-manager-kube-master 1/1 Running 0 32m 192.168.120.122 kube-master kube-system kube-dns-3913472980-3x9wh 3/3 Running 0 37m 10.244.0.2 kube-master kube-system kube-flannel-ds-1m4wz 2/2 Running 0 18m 192.168.120.122 kube-master kube-system kube-flannel-ds-3jwf5 2/2 Running 0 17m 192.168.120.123 kube-agent1 kube-system kube-flannel-ds-41qbs 2/2 Running 4 17m 192.168.120.125 kube-agent3 kube-system kube-flannel-ds-ssjct 2/2 Running 4 17m 192.168.120.124 kube-agent2 kube-system kube-proxy-0mmfc 1/1 Running 0 17m 192.168.120.124 kube-agent2 kube-system kube-proxy-23vwr 1/1 Running 0 17m 192.168.120.125 kube-agent3 kube-system kube-proxy-5q8vq 1/1 Running 0 17m 192.168.120.123 kube-agent1 kube-system kube-proxy-8srwn 1/1 Running 0 37m 192.168.120.122 kube-master kube-system kube-scheduler-kube-master 1/1 Running 0 32m 192.168.120.122 kube-master
至此，完成Kubernetes集群的部署。
以上就是本文的全部?jī)?nèi)容，希望對(duì)大家的學(xué)習(xí)有所幫助，也希望大家多多支持腳本之家。
相關(guān)文章
在htaccess寫法詳解一文中已經(jīng)寫過了htaccess文件一基本寫法和語(yǔ)句原則，同時(shí)本文也不再闡述htaccess文件的作用之強(qiáng)大，今天只來討論一下很多人都容易誤解的一個(gè)地方，那就是.htaccess文件的作用范圍2012-02-02
Linux系統(tǒng)下Nginx支持ipv6配置的方法
這篇文章主要介紹了Linux系統(tǒng)下Nginx支持ipv6的方法，小編覺得挺不錯(cuò)的，現(xiàn)在分享給大家，也給大家做個(gè)參考。一起跟隨小編過來看看吧2018-12-12
linux多線程設(shè)計(jì)是指基于Linux操作系統(tǒng)下的多線程設(shè)計(jì)，包括多任務(wù)程序的設(shè)計(jì)，并發(fā)程序設(shè)計(jì),網(wǎng)絡(luò)程序設(shè)計(jì)，數(shù)據(jù)共享等。Linux系統(tǒng)下的多線程遵循POSIX線程接口，稱為pthread。2014-08-08
淺談Linux C語(yǔ)言動(dòng)態(tài)庫(kù)及靜態(tài)庫(kù)
下面小編就為大家?guī)硪黄獪\談Linux C語(yǔ)言動(dòng)態(tài)庫(kù)及靜態(tài)庫(kù)。小編覺得挺不錯(cuò)的，現(xiàn)在就分享給大家，也給大家做個(gè)參考。一起跟隨小編過來看看吧2017-01-01
本篇文章主要介紹了NodeJs在Linux下使用的各種問題解決，可以解決各種問題，具有一定的參考價(jià)值，有興趣的可以了解一下。2017-01-01
linux上TCP connection timeout問題解決辦法
這篇文章主要介紹了 linux上TCP connection timeout問題解決辦法的相關(guān)資料,需要的朋友可以參考下2017-04-04
使用CDN之后APACHE日志記錄中IP地址不正確的解決方案
這篇文章主要介紹了使用CDN之后APACHE日志記錄中IP地址不正確的解決方案,需要的朋友可以參考下2014-12-12
目前LAMP (Linux + Apache + MySQL + PHP) 近幾年來發(fā)展迅速，已經(jīng)成為Web 服務(wù)器的事實(shí)標(biāo)準(zhǔn)。本文我們將介紹基于LAMP組合的服務(wù)器的性能優(yōu)化技巧：加速PHP。2012-02-02
大家好，本篇文章主要講的是linux系統(tǒng)下用戶管理相關(guān)介紹，感興趣的同學(xué)趕快來看一看吧，對(duì)你有幫助的話記得收藏一下哦，方便下次瀏覽2021-12-12
Linux下Apache安裝/增加mod_rewrite模塊的方法
如果你的apache已經(jīng)安裝好了，現(xiàn)在只想編譯出mod_rewrite.so模塊，在apache中進(jìn)行加載，下面我們就介紹這個(gè)方法。2011-04-04