Centos7部署Kubernetes集群
阿新 • • 發佈：2017-09-30
ctu 好的 service ech false order leg source modify
1、環境介紹及準備：
1.1 物理機操作系統
物理機操作系統采用Centos7.3 64位，細節如下。
[[email protected] ~]# uname -a Linux localhost.localdomain 3.10.0-514.6.1.el7.x86_64 #1 SMP Wed Jan 18 13:06:36 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux [[email protected] ~]# cat /etc/redhat-release CentOS Linux release 7.3.1611 (Core)
1.2 主機信息
本文準備了三臺機器用於部署k8s的運行環境，細節如下：
|
節點及功能 |
主機名 |
IP |
|
Master、etcd、registry |
K8s-master |
10.0.251.148 |
|
Node1 |
K8s-node-1 |
10.0.251.153 |
|
Node2 |
K8s-node-2 |
10.0.251.155 |
設置三臺機器的主機名：
Master上執行：
[[email protected] ~]# hostnamectl --static set-hostname k8s-master
Node1上執行：
[[email protected] ~]# hostnamectl --static set-hostname k8s-node-1
Node2上執行：
[roo[email protected] ~]# hostnamectl --static set-hostname k8s-node-2
在三臺機器上設置hosts，均執行如下命令：
echo ‘10.0.251.148 k8s-master 10.0.251.148 etcd 10.0.251.148 registry 10.0.251.153 k8s-node-1 10.0.251.155 k8s-node-2‘ >> /etc/hosts
1.3 關閉三臺機器上的防火墻
systemctl disable firewalld.service systemctl stop firewalld.service
2、部署etcd
k8s運行依賴etcd，需要先部署etcd，本文采用yum方式安裝：
[[email protected] ~]# yum install etcd -y
yum安裝的etcd默認配置文件在/etc/etcd/etcd.conf。編輯配置文件，更改以下帶顏色部分信息：
[[email protected] ~]# vi /etc/etcd/etcd.conf # [member] ETCD_NAME=master ETCD_DATA_DIR="/var/lib/etcd/default.etcd" #ETCD_WAL_DIR="" #ETCD_SNAPSHOT_COUNT="10000" #ETCD_HEARTBEAT_INTERVAL="100" #ETCD_ELECTION_TIMEOUT="1000" #ETCD_LISTEN_PEER_URLS="http://0.0.0.0:2380" ETCD_LISTEN_CLIENT_URLS="http://0.0.0.0:2379,http://0.0.0.0:4001" #ETCD_MAX_SNAPSHOTS="5" #ETCD_MAX_WALS="5" #ETCD_CORS="" # #[cluster] #ETCD_INITIAL_ADVERTISE_PEER_URLS="http://localhost:2380" # if you use different ETCD_NAME (e.g. test), set ETCD_INITIAL_CLUSTER value for this name, i.e. "test=http://..." #ETCD_INITIAL_CLUSTER="default=http://localhost:2380" #ETCD_INITIAL_CLUSTER_STATE="new" #ETCD_INITIAL_CLUSTER_TOKEN="etcd-cluster" ETCD_ADVERTISE_CLIENT_URLS="http://etcd:2379,http://etcd:4001" #ETCD_DISCOVERY="" #ETCD_DISCOVERY_SRV="" #ETCD_DISCOVERY_FALLBACK="proxy" #ETCD_DISCOVERY_PROXY=""
啟動並驗證狀態
[[email protected] ~]# systemctl start etcd [[email protected] ~]# etcdctl set testdir/testkey0 0 0 [[email protected] ~]# etcdctl get testdir/testkey0 0 [[email protected] ~]# etcdctl -C http://etcd:4001 cluster-health member 8e9e05c52164694d is healthy: got healthy result from http://0.0.0.0:2379 cluster is healthy [[email protected] ~]# etcdctl -C http://etcd:2379 cluster-health member 8e9e05c52164694d is healthy: got healthy result from http://0.0.0.0:2379 cluster is healthy
擴展：Etcd集群部署參見——http://www.cnblogs.com/zhenyuyaodidiao/p/6237019.html
3、部署master
3.1 安裝Docker
[[email protected] ~]# yum install docker
配置Docker配置文件，使其允許從registry中拉取鏡像。
[[email protected] ~]# vim /etc/sysconfig/docker
# /etc/sysconfig/docker
# Modify these options if you want to change the way the docker daemon runs
OPTIONS=‘--selinux-enabled --log-driver=journald --signature-verification=false‘
if [ -z "${DOCKER_CERT_PATH}" ]; then
DOCKER_CERT_PATH=/etc/docker
fi
OPTIONS=‘--insecure-registry registry:5000‘
設置開機自啟動並開啟服務
[[email protected] ~]# chkconfig docker on [[email protected] ~]# service docker start
3.2 安裝kubernets
[[email protected] ~]# yum install kubernetes
3.3 配置並啟動kubernetes
在kubernetes master上需要運行以下組件：
Kubernets API Server
Kubernets Controller Manager
Kubernets Scheduler
相應的要更改以下幾個配置中帶顏色部分信息：
3.3.1 /etc/kubernetes/apiserver
[[email protected] ~]# vim /etc/kubernetes/apiserver ### # kubernetes system config # # The following values are used to configure the kube-apiserver # # The address on the local server to listen to. KUBE_API_ADDRESS="--insecure-bind-address=0.0.0.0" # The port on the local server to listen on. KUBE_API_PORT="--port=8080" # Port minions listen on # KUBELET_PORT="--kubelet-port=10250" # Comma separated list of nodes in the etcd cluster KUBE_ETCD_SERVERS="--etcd-servers=http://etcd:2379" # Address range to use for services KUBE_SERVICE_ADDRESSES="--service-cluster-ip-range=10.254.0.0/16" # default admission control policies #KUBE_ADMISSION_CONTROL="--admission-control=NamespaceLifecycle,NamespaceExists,LimitRanger,SecurityContextDeny,ServiceAccount,ResourceQuota" KUBE_ADMISSION_CONTROL="--admission-control=NamespaceLifecycle,NamespaceExists,LimitRanger,SecurityContextDeny,ResourceQuota" # Add your own! KUBE_API_ARGS=""
3.3.2 /etc/kubernetes/config
[[email protected] ~]# vim /etc/kubernetes/config ### # kubernetes system config # # The following values are used to configure various aspects of all # kubernetes services, including # # kube-apiserver.service # kube-controller-manager.service # kube-scheduler.service # kubelet.service # kube-proxy.service # logging to stderr means we get it in the systemd journal KUBE_LOGTOSTDERR="--logtostderr=true" # journal message level, 0 is debug KUBE_LOG_LEVEL="--v=0" # Should this cluster be allowed to run privileged docker containers KUBE_ALLOW_PRIV="--allow-privileged=false" # How the controller-manager, scheduler, and proxy find the apiserver KUBE_MASTER="--master=http://k8s-master:8080"
啟動服務並設置開機自啟動
[[email protected] ~]# systemctl enable kube-apiserver.service [[email protected] ~]# systemctl start kube-apiserver.service [[email protected] ~]# systemctl enable kube-controller-manager.service [[email protected] ~]# systemctl start kube-controller-manager.service [[email protected] ~]# systemctl enable kube-scheduler.service [[email protected] ~]# systemctl start kube-scheduler.service
4、部署node
4.1 安裝docker
參見3.1
4.2 安裝kubernets
參見3.2
4.3 配置並啟動kubernetes
在kubernetes node上需要運行以下組件：
Kubelet
Kubernets Proxy
相應的要更改以下幾個配置文中帶顏色部分信息：
4.3.1 /etc/kubernetes/config
[[email protected] ~]# vim /etc/kubernetes/config ### # kubernetes system config # # The following values are used to configure various aspects of all # kubernetes services, including # # kube-apiserver.service # kube-controller-manager.service # kube-scheduler.service # kubelet.service # kube-proxy.service # logging to stderr means we get it in the systemd journal KUBE_LOGTOSTDERR="--logtostderr=true" # journal message level, 0 is debug KUBE_LOG_LEVEL="--v=0" # Should this cluster be allowed to run privileged docker containers KUBE_ALLOW_PRIV="--allow-privileged=false" # How the controller-manager, scheduler, and proxy find the apiserver KUBE_MASTER="--master=http://k8s-master:8080"
4.3.2 /etc/kubernetes/kubelet
[[email protected] ~]# vim /etc/kubernetes/kubelet ### # kubernetes kubelet (minion) config # The address for the info server to serve on (set to 0.0.0.0 or "" for all interfaces) KUBELET_ADDRESS="--address=0.0.0.0" # The port for the info server to serve on # KUBELET_PORT="--port=10250" # You may leave this blank to use the actual hostname KUBELET_HOSTNAME="--hostname-override=k8s-node-1" # location of the api-server KUBELET_API_SERVER="--api-servers=http://k8s-master:8080" # pod infrastructure container KUBELET_POD_INFRA_CONTAINER="--pod-infra-container-image=registry.access.redhat.com/rhel7/pod-infrastructure:latest" # Add your own! KUBELET_ARGS=""
啟動服務並設置開機自啟動
[[email protected] ~]# systemctl enable kubelet.service [[email protected] ~]# systemctl start kubelet.service [[email protected] ~]# systemctl enable kube-proxy.service [[email protected] ~]# systemctl start kube-proxy.service
4.4 查看狀態
在master上查看集群中節點及節點狀態
[[email protected] ~]# kubectl -s http://k8s-master:8080 get node NAME STATUS AGE k8s-node-1 Ready 3m k8s-node-2 Ready 16s [[email protected] ~]# kubectl get nodes NAME STATUS AGE k8s-node-1 Ready 3m k8s-node-2 Ready 43s
至此，已經搭建了一個kubernetes集群，但目前該集群還不能很好的工作，請繼續後續的步驟。
5、創建覆蓋網絡——Flannel
5.1 安裝Flannel
在master、node上均執行如下命令，進行安裝
[[email protected] ~]# yum install flannel
版本為0.0.5
5.2 配置Flannel
master、node上均編輯/etc/sysconfig/flanneld，修改紅色部分
[[email protected] ~]# vi /etc/sysconfig/flanneld # Flanneld configuration options # etcd url location. Point this to the server where etcd runs FLANNEL_ETCD_ENDPOINTS="http://etcd:2379" # etcd config key. This is the configuration key that flannel queries # For address range assignment FLANNEL_ETCD_PREFIX="/atomic.io/network" # Any additional options that you want to pass #FLANNEL_OPTIONS=""
5.3 配置etcd中關於flannel的key
Flannel使用Etcd進行配置，來保證多個Flannel實例之間的配置一致性，所以需要在etcd上進行如下配置：（‘/atomic.io/network/config’這個key與上文/etc/sysconfig/flannel中的配置項FLANNEL_ETCD_PREFIX是相對應的，錯誤的話啟動就會出錯）
[[email protected] ~]# etcdctl mk /atomic.io/network/config ‘{ "Network": "10.0.0.0/16" }‘
{ "Network": "10.0.0.0/16" }
5.4 啟動
啟動Flannel之後，需要依次重啟docker、kubernete。
在master執行：
systemctl enable flanneld.service systemctl start flanneld.service service docker restart systemctl restart kube-apiserver.service systemctl restart kube-controller-manager.service systemctl restart kube-scheduler.service
在node上執行：
systemctl enable flanneld.service systemctl start flanneld.service service docker restart systemctl restart kubelet.service systemctl restart kube-proxy.service
Centos7部署Kubernetes集群