搭建k8s時(shí)，網(wǎng)上全是要么過(guò)時(shí)的,要么殘缺的,大多數(shù)都是2016年,2017年的文檔,照著嘗試了N次,各種卸了重裝,最后centos系統(tǒng)都搞得亂七八糟,各種配置互相沖突,影響,一直在kubeadm init 報(bào)錯(cuò), 后來(lái)實(shí)在無(wú)果,重新安裝了centos系統(tǒng),從頭再來(lái)。
環(huán)境：
阿里云ECS，master4核8G，node2核4G
CentOS Linux release 7.6.1810 (Core)
Linux iZbp1izzt8ihoenra1iscfZ 3.10.0-957.5.1.el7.x86_64 #1 SMP Fri Feb 1 14:54:57 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
安裝docker-ce
Master、Node節(jié)點(diǎn)都需要安裝、配置Docker
# 卸載原來(lái)的docker
sudo yum remove docker \
docker-client \
docker-client-latest \
docker-common \
docker-latest \
docker-latest-logrotate \
docker-logrotate \
docker-engine
# 安裝依賴
sudo yum update -y && sudo yum install -y yum-utils \
device-mapper-persistent-data \
lvm2
# 添加官方y(tǒng)um庫(kù)
sudo yum-config-manager \
--add-repo \
https://download.docker.com/linux/centos/docker-ce.repo
#如果用阿里云源（官網(wǎng)的源比較慢）
sudo yum-config-manager --add-repo http://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo
# 安裝docker
sudo yum install docker-ce docker-ce-cli containerd.io
# 查看docker版本
docker --version
# 開機(jī)啟動(dòng)
systemctl enable --now docker
或者使用腳本一鍵安裝
curl -fsSL "https://get.docker.com/" | sh
systemctl enable --now docker
修改docker cgroup驅(qū)動(dòng)，與k8s一致，使用systemd
# 修改docker cgroup驅(qū)動(dòng)：native.cgroupdriver=systemd
cat > /etc/docker/daemon.json <<EOF
{
"exec-opts": ["native.cgroupdriver=systemd"],
"log-driver": "json-file",
"log-opts": {
"max-size": "100m"
},
"storage-driver": "overlay2",
"storage-opts": [
"overlay2.override_kernel_check=true"
]
}
EOF
systemctl restart docker # 重啟使配置生效
安裝 kubelet kubeadm kubectl
master、node節(jié)點(diǎn)都需要安裝kubelet kubeadm kubectl。
安裝kubernetes的時(shí)候，需要安裝kubelet, kubeadm等包，但k8s官網(wǎng)給的yum源是packages.cloud.google.com，國(guó)內(nèi)訪問(wèn)不了，此時(shí)我們可以使用阿里云的yum倉(cāng)庫(kù)鏡像。
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
# 關(guān)閉SElinux
setenforce 0
sed -i 's/^SELINUX=enforcing$/SELINUX=disabled/' /etc/selinux/config
# 安裝kubelet kubeadm kubectl
yum install -y kubelet kubeadm kubectl --disableexcludes=kubernetes
systemctl enable --now kubelet # 開機(jī)啟動(dòng)kubelet
# centos7用戶還需要設(shè)置路由：
yum install -y bridge-utils.x86_64
modprobe br_netfilter # 加載br_netfilter模塊，使用lsmod查看開啟的模塊
cat <<EOF > /etc/sysctl.d/k8s.conf
net.bridge.bridge-nf-call-ip6tables = 1
net.bridge.bridge-nf-call-iptables = 1
EOF
sysctl --system # 重新加載所有配置文件
systemctl disable --now firewalld # 關(guān)閉防火墻
# k8s要求關(guān)閉swap (qxl)
swapoff -a && sysctl -w vm.swappiness=0 # 關(guān)閉swap
sed -ri '/^[^#]*swap/s@^@#@' /etc/fstab # 取消開機(jī)掛載swap
創(chuàng)建集群準(zhǔn)備工作
# Master端：
kubeadm config images pull # 拉取集群所需鏡像，這個(gè)需要翻墻
# --- 不能翻墻可以嘗試以下辦法 ---
kubeadm config images list # 列出所需鏡像
#(不是一定是下面的,根據(jù)實(shí)際情況來(lái))
# 根據(jù)所需鏡像名字先拉取國(guó)內(nèi)資源
docker pull mirrorgooglecontainers/kube-apiserver:v1.14.1
docker pull mirrorgooglecontainers/kube-controller-manager:v1.14.1
docker pull mirrorgooglecontainers/kube-scheduler:v1.14.1
docker pull mirrorgooglecontainers/kube-proxy:v1.14.1
docker pull mirrorgooglecontainers/pause:3.1
docker pull mirrorgooglecontainers/etcd:3.3.10
docker pull coredns/coredns:1.3.1 # 這個(gè)在mirrorgooglecontainers中沒(méi)有
# 修改鏡像tag
docker tag mirrorgooglecontainers/kube-apiserver:v1.14.1 k8s.gcr.io/kube-apiserver:v1.14.1
docker tag mirrorgooglecontainers/kube-controller-manager:v1.14.1 k8s.gcr.io/kube-controller-manager:v1.14.1
docker tag mirrorgooglecontainers/kube-scheduler:v1.14.1 k8s.gcr.io/kube-scheduler:v1.14.1
docker tag mirrorgooglecontainers/kube-proxy:v1.14.1 k8s.gcr.io/kube-proxy:v1.14.1
docker tag mirrorgooglecontainers/pause:3.1 k8s.gcr.io/pause:3.1
docker tag mirrorgooglecontainers/etcd:3.3.10 k8s.gcr.io/etcd:3.3.10
docker tag coredns/coredns:1.3.1 k8s.gcr.io/coredns:1.3.1
# 把所需的鏡像下載好，init的時(shí)候就不會(huì)再拉鏡像，由于無(wú)法連接google鏡像庫(kù)導(dǎo)致出錯(cuò)
# 刪除原來(lái)的鏡像
docker rmi mirrorgooglecontainers/kube-apiserver:v1.14.1
docker rmi mirrorgooglecontainers/kube-controller-manager:v1.14.1
docker rmi mirrorgooglecontainers/kube-scheduler:v1.14.1
docker rmi mirrorgooglecontainers/kube-proxy:v1.14.1
docker rmi mirrorgooglecontainers/pause:3.1
docker rmi mirrorgooglecontainers/etcd:3.3.10
docker rmi coredns/coredns:1.3.1
# --- 不能翻墻可以嘗試使用 ---
# Node端：
# 根據(jù)所需鏡像名字先拉取國(guó)內(nèi)資源
docker pull mirrorgooglecontainers/kube-proxy:v1.14.1
docker pull mirrorgooglecontainers/pause:3.1
# 修改鏡像tag
docker tag mirrorgooglecontainers/kube-proxy:v1.14.1 k8s.gcr.io/kube-proxy:v1.14.1
docker tag mirrorgooglecontainers/pause:3.1 k8s.gcr.io/pause:3.1
# 刪除原來(lái)的鏡像
docker rmi mirrorgooglecontainers/kube-proxy:v1.14.1
docker rmi mirrorgooglecontainers/pause:3.1
# 不加載鏡像node節(jié)點(diǎn)不能
使用kubeadm創(chuàng)建集群
# 第一次初始化過(guò)程中/etc/kubernetes/admin.conf該文件存在，是空文件（我自己手動(dòng)創(chuàng)建的），會(huì)報(bào)錯(cuò)：panic: runtime error: invalid memory address or nil pointer dereference
ls /etc/kubernetes/admin.conf && mv /etc/kubernetes/admin.conf.bak # 移走備份
# 初始化Master（Master需要至少2核）此處會(huì)各種報(bào)錯(cuò),異常...成功與否就在此
kubeadm init --apiserver-advertise-address 192.168.200.25 --pod-network-cidr 10.244.0.0/16 # --kubernetes-version 1.14.1
# --apiserver-advertise-address 指定與其它節(jié)點(diǎn)通信的接口
# --pod-network-cidr 指定pod網(wǎng)絡(luò)子網(wǎng)，使用fannel網(wǎng)絡(luò)必須使用這個(gè)CIDR
# --image-repository=registry.aliyuncs.com/google_containers初始化時(shí)可以添加下載鏡像的源地址。因?yàn)槟J(rèn)是google的，國(guó)內(nèi)無(wú)法訪問(wèn)。這樣前面就不要提前下載好鏡像了。
- 運(yùn)行初始化，程序會(huì)檢驗(yàn)環(huán)境一致性，可以根據(jù)實(shí)際錯(cuò)誤提示進(jìn)一步修復(fù)問(wèn)題。
- 程序會(huì)訪問(wèn)https://dl.k8s.io/release/sta...，訪問(wèn)這個(gè)連接需要FQ，如果無(wú)法訪問(wèn)，則會(huì)使用kubeadm client的版本作為安裝的版本號(hào)，使用kubeadm version查看client版本。也可以使用--kubernetes-version明確指定版本。
# 初始化結(jié)果：
[init] Using Kubernetes version: v1.14.1
[preflight] Running pre-flight checks
[preflight] Pulling images required for setting up a Kubernetes cluster
[preflight] This might take a minute or two, depending on the speed of your internet connection
[preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[kubelet-start] Activating the kubelet service
[certs] Using certificateDir folder "/etc/kubernetes/pki"
[certs] Using existing etcd/ca certificate authority
[certs] Using existing etcd/server certificate and key on disk
[certs] Using existing etcd/peer certificate and key on disk
[certs] Using existing etcd/healthcheck-client certificate and key on disk
[certs] Using existing apiserver-etcd-client certificate and key on disk
[certs] Using existing ca certificate authority
[certs] Using existing apiserver certificate and key on disk
[certs] Using existing apiserver-kubelet-client certificate and key on disk
[certs] Using existing front-proxy-ca certificate authority
[certs] Using existing front-proxy-client certificate and key on disk
[certs] Using the existing "sa" key
[kubeconfig] Using kubeconfig folder "/etc/kubernetes"
[kubeconfig] Writing "admin.conf" kubeconfig file
[kubeconfig] Writing "kubelet.conf" kubeconfig file
[kubeconfig] Writing "controller-manager.conf" kubeconfig file
[kubeconfig] Writing "scheduler.conf" kubeconfig file
[control-plane] Using manifest folder "/etc/kubernetes/manifests"
[control-plane] Creating static Pod manifest for "kube-apiserver"
[control-plane] Creating static Pod manifest for "kube-controller-manager"
[control-plane] Creating static Pod manifest for "kube-scheduler"
[etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s
[apiclient] All control plane components are healthy after 21.503375 seconds
[upload-config] storing the configuration used in ConfigMap "kubeadm-config" in the "kube-system" Namespace
[kubelet] Creating a ConfigMap "kubelet-config-1.14" in namespace kube-system with the configuration for the kubelets in the cluster
[upload-certs] Skipping phase. Please see --experimental-upload-certs
[mark-control-plane] Marking the node master as control-plane by adding the label "node-role.kubernetes.io/master=''"
[mark-control-plane] Marking the node master as control-plane by adding the taints [node-role.kubernetes.io/master:NoSchedule]
[bootstrap-token] Using token: w2i0mh.5fxxz8vk5k8db0wq
[bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles
[bootstrap-token] configured RBAC rules to allow Node Bootstrap tokens to post CSRs in order for nodes to get long term certificate credentials
[bootstrap-token] configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token
[bootstrap-token] configured RBAC rules to allow certificate rotation for all node client certificates in the cluster
[bootstrap-token] creating the "cluster-info" ConfigMap in the "kube-public" namespace
[addons] Applied essential addon: CoreDNS
[addons] Applied essential addon: kube-proxy
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:
#每個(gè)機(jī)器創(chuàng)建的master以下部分都不同,需要自己保存好-qxl
kubeadm join 192.168.200.25:6443 --token our9a0.zl490imi6t81tn5u \
--discovery-token-ca-cert-hash sha256:b93f710eb9b389a69f0cd0d6dcf7c82e389a68f009eb6b2028f69d54b099de16
初始化報(bào)錯(cuò)
k8s報(bào)錯(cuò)1.png
此報(bào)錯(cuò)大概意思是一些服務(wù)沒(méi)有起來(lái)，通過(guò)查看日志，主要是6443這個(gè)端口不能訪問(wèn)。通過(guò)網(wǎng)上搜索：
echo 'Environment="KUBELET_EXTRA_ARGS=--fail-swap-on=false"' >> /etc/systemd/system/kubelet.service.d/10-kubeadm.conf
systemctl daemon-reload
systemctl restart kubelet
#1.14.1版本沒(méi)有這個(gè)文件，我修改的/etc/sysconfig/kubelet
#但是不起作用，還是一直報(bào)錯(cuò)。折騰許久，重裝系統(tǒng)。開始時(shí)用的centos7.2，升級(jí)centos7.6后。成功！
普通用戶設(shè)置權(quán)限
mkdir -p $HOME/.kube
sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
sudo chown $(id -u):$(id -g) $HOME/.kube/config
用戶權(quán)限設(shè)置這一步，我用root用戶，以為沒(méi)事，開始就沒(méi)有執(zhí)行。結(jié)果下一步創(chuàng)建網(wǎng)絡(luò)一直報(bào)錯(cuò)。
報(bào)錯(cuò)如下：
k8s報(bào)錯(cuò).png
root用戶執(zhí)行上面的用戶設(shè)置權(quán)限后，解決！
應(yīng)用flannel網(wǎng)絡(luò)
kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml
node加入機(jī)器
# node1:
kubeadm join 192.168.200.25:6443 --token w2i0mh.5fxxz8vk5k8db0wq \
--discovery-token-ca-cert-hash sha256:65e82e987f50908f3640df7e05c7a91f390a02726c9142808faa739d4dc24252
# node2:
kubeadm join 192.168.200.25:6443 --token w2i0mh.5fxxz8vk5k8db0wq \
--discovery-token-ca-cert-hash sha256:65e82e987f50908f3640df7e05c7a91f390a02726c9142808faa739d4dc24252
輸出日志：
[preflight] Running pre-flight checks
[preflight] Reading configuration from the cluster...
[preflight] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -oyaml'
[kubelet-start] Downloading configuration for the kubelet from the "kubelet-config-1.14" ConfigMap in the kube-system namespace
[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet-start] Activating the kubelet service
[kubelet-start] Waiting for the kubelet to perform the TLS Bootstrap...
This node has joined the cluster:
* Certificate signing request was sent to apiserver and a response was received.
* The Kubelet was informed of the new secure connection details.
Run 'kubectl get nodes' on the control-plane to see this node join the cluster.
# master：
kubectl get pods --all-namespaces
# ---輸出信息---
NAMESPACE NAME READY STATUS RESTARTS AGE
kube-system coredns-fb8b8dccf-rn8kd 1/1 Running 0 170m
kube-system coredns-fb8b8dccf-slwr4 1/1 Running 0 170m
kube-system etcd-master 1/1 Running 0 169m
kube-system kube-apiserver-master 1/1 Running 0 169m
kube-system kube-controller-manager-master 1/1 Running 0 169m
kube-system kube-flannel-ds-amd64-l8c7c 1/1 Running 0 130m
kube-system kube-flannel-ds-amd64-lcmxw 1/1 Running 1 117m
kube-system kube-flannel-ds-amd64-pqnln 1/1 Running 1 72m
kube-system kube-proxy-4kcqb 1/1 Running 0 170m
kube-system kube-proxy-jcqjd 1/1 Running 0 72m
kube-system kube-proxy-vm9sj 1/1 Running 0 117m
kube-system kube-scheduler-master 1/1 Running 0 169m
# ---輸出信息---
kubectl get nodes
# ---輸出信息---
NAME STATUS ROLES AGE VERSION
master Ready master 171m v1.14.1
node1 Ready <none> 118m v1.14.1
node2 Ready <none> 74m v1.14.1
# ---輸出信息---
排錯(cuò)
journalctl -f # 當(dāng)前輸出日志
journalctl -f -u kubelet # 只看當(dāng)前的kubelet進(jìn)程日志
至此，結(jié)束！
