一.機器信息
[root@kube-gmg-03-master-1 ~]# uname -a
Linux kube-gmg-03-master-1 3.10.0-957.el7.x86_64 #1 SMP Thu Nov 8 23:39:32 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
[root@kube-gmg-03-master-1 ~]# cat /etc/redhat-release
CentOS Linux release 7.9.2009 (Core)
二、主機信息
本文準備了三臺機器用於部署k8s的運行環境，細節如下：
|
節點及功能 |
主機名 |
IP |
|
Master、etcd、registry |
K8s-master |
10.255.61.1 |
|
Node1 |
K8s-node-1 |
10.255.61.2 |
|
Node2 |
K8s-node-2 |
10.255.61.3 |
三、設置三臺機器的主機名
Master上執行：
hostnamectl --static set-hostname k8s-master
Node1上執行：
hostnamectl --static set-hostname k8s-node-1
Node2上執行：
hostnamectl --static set-hostname k8s-node-2
四、設置hosts
三臺機器均執行如下命令：
echo '10.255.61.1 k8s-master 10.255.61.1 etcd 10.255.61.1 registry 10.255.61.2 k8s-node-1 10.255.61.3 k8s-node-2' >> /etc/hosts
五、關閉三臺機器上的防火牆
systemctl disable firewalld.service
systemctl stop firewalld.service
六、三臺機器部署etcd
k8s運行依賴etcd，需要先部署etcd，本文采用yum方式安裝：
yum install etcd -y
yum安裝的etcd默認配置文件在/etc/etcd/etcd.conf。編輯配置文件，更改以下帶顏色部分信息：
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=""
啓動並驗證狀態（先啓動master的etcd）
systemctl start etcd etcdctl set testdir/testkey0 0 etcdctl get testdir/testkey0 etcdctl -C http://etcd:4001 cluster-health etcdctl -C http://etcd:2379 cluster-health
擴展：Etcd集羣部署參見——http://www.cnblogs.com/zhenyuyaodidiao/p/6237019.html
七、部署master
7.1 安裝docker
yum install docker -y
配置Docker配置文件，使其允許從registry中拉取鏡像。
vim /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'
設置開機自啓動並開啓服務
systemctl enable docker.service systemctl start docker
7.2 安裝kubernets
yum install kubernetes -y
7.3 配置並啓動kubernetes
在kubernetes master上需要安裝運行以下組件：
Kubernets API Server
Kubernets Controller Manager
Kubernets Scheduler
7.4 相應的要更改以下幾個配置中帶顏色部分信息：
$ 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=""
$ 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"
7.5 啓動服務並設置開機自啓動，運行如下命令
systemctl enable kube-apiserver.service systemctl start kube-apiserver.service systemctl enable kube-controller-manager.service systemctl start kube-controller-manager.service systemctl enable kube-scheduler.service systemctl start kube-scheduler.service
八、部署node節點
8.1 參考7.1安裝docker 參考7.2安裝kubernets
8.2 node節點啓動kubernets
在kubernetes node上需要運行以下組件：
Kubelet
Kubernets Proxy
8.2.1 配置文件
$ 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"
[root@K8s-node-1 ~]# 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=""
8.3 啓動服務並設置開機自啓動
systemctl enable kubelet.service systemctl start kubelet.service systemctl enable kube-proxy.service systemctl start kube-proxy.service
8.4 查看狀態
在master上查看集羣中節點及節點狀態
$ kubectl -s http://k8s-master:8080 get node NAME STATUS AGE k8s-node-1 Ready 3m k8s-node-2 Ready 16s $ kubectl get nodes NAME STATUS AGE k8s-node-1 Ready 3m k8s-node-2 Ready 43s
至此，已經搭建了一個kubernetes集羣，但目前該集羣還不能很好的工作，請繼續後續的步驟。
九、創建覆蓋網絡——Flannel
9.1 安裝Flannel
在master、node上均執行如下命令，進行安裝
[root@k8s-master ~]# yum install flannel
9.2 配置Flannel
master、node上均編輯/etc/sysconfig/flanneld，修改紅色部分
[root@k8s-master ~]# 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=""
9.3 配置etcd中關於flannel的key
Flannel使用Etcd進行配置，來保證多個Flannel實例之間的配置一致性，所以需要在etcd上進行如下配置：（‘/atomic.io/network/config’這個key與上文/etc/sysconfig/flannel中的配置項FLANNEL_ETCD_PREFIX是相對應的，錯誤的話啓動就會出錯）
[root@k8s-master ~]# etcdctl mk /atomic.io/network/config '{ "Network": "10.0.0.0/16" }'
{ "Network": "10.0.0.0/16" }
9.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
涉及到的書籍——Kubernetes實戰、Kubernetes權威指南：從Docker到Kubernetes實踐全接觸、每天5分鐘玩轉Docker容器技術 、Docker容器：利用Kubernetes、Flannel、Cockpit和Atomic構建和部署
感謝https://www.cnblogs.com/zhenyuyaodidiao/p/6500830.html
結束！