资源规划
| 名称 | ip | 资源配置 |
|---|---|---|
| master | 192.168.163.100 | 2c,2u,50g |
| node1 | 192.168.163.101 | 2c,2u,50g |
| node2 | 192.168.163.102 | 2c,2u,50g |
VMware 安装环境系统
系统 CentOS:CentOS-7-x86_64-DVD-1804.iso
先安装master,后面使用 VMware 的虚拟机复制,编辑 hostname 和 编辑 IP 配置。
编辑hostname: vim /etc/hostname
编辑ip:vim /etc/sysconfig/network-scripts/ifconfig-ens33
参考:VMware 如何通过现有虚拟机克隆新的虚拟机 (图文)
统一用户名 root,密码 123456(只是为了测试方便而已)
kubectl apply -f kube-flannel.yml 报错
不知道,怎么就好了,参考了一下 K8s 配置网络插件flannel
调整 kube-flannel.yml
net-conf.json: |{"Network": "10.244.0.0/16","Backend": {"Type": "vxlan","Directrouting":true #新加}
和 kubectl delete -f kube-flannel.yml
[root@master ~]# kubectl apply -f kube-flannel.ymlpodsecuritypolicy.policy/psp.flannel.unprivileged createdclusterrole.rbac.authorization.k8s.io/flannel createdclusterrolebinding.rbac.authorization.k8s.io/flannel createdserviceaccount/flannel createdconfigmap/kube-flannel-cfg createddaemonset.apps/kube-flannel-ds created[root@master ~]# kubectl get nodesNAME STATUS ROLES AGE VERSIONmaster NotReady master 2m35s v1.17.4node1 NotReady <none> 110s v1.17.4node2 NotReady <none> 106s v1.17.4[root@master ~]# kubectl apply -f kube-flannel.ymlpodsecuritypolicy.policy/psp.flannel.unprivileged configuredclusterrole.rbac.authorization.k8s.io/flannel unchangedclusterrolebinding.rbac.authorization.k8s.io/flannel unchangedserviceaccount/flannel unchangedconfigmap/kube-flannel-cfg unchangeddaemonset.apps/kube-flannel-ds unchanged[root@master ~]# vim kube-flannel.yml[root@master ~]#[root@master ~]#[root@master ~]#[root@master ~]# kubectl apply -f kube-flannel.ymlpodsecuritypolicy.policy/psp.flannel.unprivileged configuredclusterrole.rbac.authorization.k8s.io/flannel unchangedclusterrolebinding.rbac.authorization.k8s.io/flannel unchangedserviceaccount/flannel unchangedconfigmap/kube-flannel-cfg unchangeddaemonset.apps/kube-flannel-ds configured[root@master ~]# vim kube-flannel.yml[root@master ~]#[root@master ~]# ip router showObject "router" is unknown, try "ip help".[root@master ~]# ip route showdefault via 192.168.163.2 dev ens33 proto static metric 10010.244.0.0/24 dev cni0 proto kernel scope link src 10.244.0.110.244.1.0/24 via 10.244.1.0 dev flannel.1 onlink10.244.2.0/24 via 10.244.2.0 dev flannel.1 onlink172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1192.168.163.0/24 dev ens33 proto kernel scope link src 192.168.163.100 metric 100[root@master ~]# ls -a. .bash_history .bashrc .cshrc .pki.. .bash_logout .cache .kube .tcshrcanaconda-ks.cfg .bash_profile .config kube-flannel.yml .viminfo[root@master ~]# ll -a总用量 44dr-xr-x---. 6 root root 229 6月 28 11:17 .dr-xr-xr-x. 17 root root 224 6月 28 10:12 ..-rw-------. 1 root root 1281 6月 28 10:12 anaconda-ks.cfg-rw-------. 1 root root 2925 6月 28 11:01 .bash_history-rw-r--r--. 1 root root 18 12月 29 2013 .bash_logout-rw-r--r--. 1 root root 176 12月 29 2013 .bash_profile-rw-r--r--. 1 root root 176 12月 29 2013 .bashrcdrwxr-xr-x. 3 root root 18 6月 28 10:16 .cachedrwxr-xr-x. 3 root root 18 6月 28 10:16 .config-rw-r--r--. 1 root root 100 12月 29 2013 .cshrcdrwxr-xr-x 4 root root 51 6月 28 11:09 .kube-rw-r--r-- 1 root root 4879 6月 28 11:24 kube-flannel.ymldrwxr----- 3 root root 19 6月 28 10:50 .pki-rw-r--r--. 1 root root 129 12月 29 2013 .tcshrc-rw------- 1 root root 5294 6月 28 11:17 .viminfo[root@master ~]# kubectl apply -f kube-flannel.ymlpodsecuritypolicy.policy/psp.flannel.unprivileged configuredclusterrole.rbac.authorization.k8s.io/flannel unchangedclusterrolebinding.rbac.authorization.k8s.io/flannel unchangedserviceaccount/flannel unchangedconfigmap/kube-flannel-cfg configureddaemonset.apps/kube-flannel-ds unchanged[root@master ~]# kubectl delete -f kube-flannel.ymlpodsecuritypolicy.policy "psp.flannel.unprivileged" deletedclusterrole.rbac.authorization.k8s.io "flannel" deletedclusterrolebinding.rbac.authorization.k8s.io "flannel" deletedserviceaccount "flannel" deletedconfigmap "kube-flannel-cfg" deleteddaemonset.apps "kube-flannel-ds" deleted[root@master ~]# kubectl apply -f kube-flannel.ymlpodsecuritypolicy.policy/psp.flannel.unprivileged createdclusterrole.rbac.authorization.k8s.io/flannel createdclusterrolebinding.rbac.authorization.k8s.io/flannel createdserviceaccount/flannel createdconfigmap/kube-flannel-cfg createddaemonset.apps/kube-flannel-ds created[root@master ~]# kubeadm get nodesunknown command "get" for "kubeadm"To see the stack trace of this error execute with --v=5 or higher[root@master ~]# kubectl get nodesNAME STATUS ROLES AGE VERSIONmaster Ready master 17m v1.17.4node1 Ready <none> 17m v1.17.4node2 Ready <none> 17m v1.17.4
