centos7使用Minikube「快速搭建「出Kubernetes本地實驗環境(踩坑集錦及解決方案)
先決條件(先假設你做完這兩步驟)
- 檢查Linux是否支援虛擬化,驗證輸出是否為非空如何開啟虛擬化
grep -E --color 'vmx|svm' /proc/cpuinfo
- 安裝 kubectl
判斷是否成功安裝kubectl
kubectl version
安裝Minikube
Linux
curl -Lo minikube //kubernetes.oss-cn-hangzhou.aliyuncs.com/minikube/releases/v1.13.0/minikube-linux-amd64 && chmod +x minikube && sudo mv minikube /usr/local/bin/
啟動
minikube start
當你執行minkube start會出現這個錯誤,大概意思是需要加個 –driver=none的參數
錯誤一:
-
* The "docker" driver should not be used with root privileges. * If you are running minikube within a VM, consider using --driver=none: * //minikube.sigs.k8s.io/docs/reference/drivers/none/ X Exiting due to DRV_AS_ROOT: The "docker" driver should not be used with root privileges.
加了參數以後那就恐怖了
[WARNING IsDockerSystemdCheck]: detected "cgroupfs" as the Docker cgroup driver. The recommended driver is "systemd". Please follow the guide at //kubernetes.io/docs/setup/cri/
1.[WARNING Swap]: running with swap on is not supported. Please disable swap
2.[WARNING Service-Kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'
71489 configset.go:348] WARNING: kubeadm cannot validate component configs for API groups [kubelet.config.k8s.io kubeproxy.config.k8s.io]
error execution phase preflight: [preflight] Some fatal errors occurred:
[ERROR FileContent--proc-sys-net-bridge-bridge-nf-call-iptables]: /proc/sys/net/bridge/bridge-nf-call-iptables contents are not set to 1
[preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...`
警告1.關閉Swap緩衝區(running with swap on is not supported. Please disable swap)
# 關閉Swap，機器重啟後不生效
swapoff -a
# 修改/etc/fstab永久關閉Swap
cp -p /etc/fstab /etc/fstab.bak$(date '+%Y%m%d%H%M%S')
# Redhat
sed -i "s/\/dev\/mapper\/rhel-swap/\#\/dev\/mapper\/rhel-swap/g" /etc/fstab
# CentOS
sed -i "s/\/dev\/mapper\/centos-swap/\#\/dev\/mapper\/centos-swap/g" /etc/fstab
# 修改後重新掛載全部掛載點
mount -a
# 查看Swap
free -m
cat /proc/swaps
systemctl daemon-reload
systemctl restart kubelet
警告2.kubelet service is not enabled, please run ‘systemctl enable kubelet.service’
//啟動kubelet服務
systemctl enable kubelet.service
錯誤3. FileContent–proc-sys-net-bridge-bridge-nf-call-iptables]: /proc/sys/net/bridge/bridge-nf-call-iptables contents are not set to 1
echo "1" >/proc/sys/net/bridge/bridge-nf-call-iptables
現在終於沒啥錯了
啟動minikube
為了訪問海外的資源，阿里雲提供了一系列基礎設施，請按照如下參數進行配置。其中常見參數
--driver=***從1.5.0版本開始，Minikube預設使用本地最好的驅動來創建Kubernetes本地環境，測試過的版本docker,kvm--image-mirror-country cn將預設利用 registry.cn-hangzhou.aliyuncs.com/google_containers 作為安裝Kubernetes的容器鏡像倉庫 （阿里雲版本可選）--iso-url=***利用阿里雲的鏡像地址下載相應的 .iso 文件 （阿里雲版本可選）--registry-mirror=***為了拉取Docker Hub鏡像，需要為 Docker daemon 配置鏡像加速，參考阿里雲鏡像服務--cpus=2: 為minikube虛擬機分配CPU核數--memory=2048mb: 為minikube虛擬機分配記憶體數--kubernetes-version=***: minikube 虛擬機將使用的 kubernetes 版本
minikube start --image-mirror-country cn --iso-url=//kubernetes.oss-cn-hangzhou.aliyuncs.com/minikube/iso/minikube-v1.5.0.iso --registrymirror=//pe3ox7bd.mirror.aliyuncs.com --driver="none" --memory=2048
不出意外應該是這樣的
啟動minikube dashboard
minikube dashboard
dashboard 給出了一個訪問地址，可以看出這個地址和埠只是k8s的虛擬地址，只能本機訪問如果要想從電腦上訪問伺服器上虛擬機上的dashboard 你應該
添加集群對外訪問代理：
nohub kubectl proxy --port=[需要暴露的埠號] --address='[伺服器IP]' --accept-hosts='^[外部訪問伺服器的IP]$' >/dev/null 2>&1&
例如：
nohup kubectl proxy --port=41111 --address='192.168.56.165' --accept-hosts='^192.168.56.165$' >/dev/null 2>&1&
訪問地址為:
//192.168.56.165:41111/api/v1/namespaces/kubernetes-dashboard/services/http:kubernetes-dashboard:/proxy/#/overview?namespace=default
