K8s虚拟机集群静态IP问题

sydml
1,093 阅读2分钟

虚拟机静态IP解决

解决的问题

  • 设置静态ip后无法联网
  • 虚拟机设置静态ip可依ping通ip，ping不同www.baidu.com 域名（一定要设置好dns，网络上推荐使用114.114.114.114或则8.8.8.8我这里都没生效，最后cmd下查看本机ipconfig配置的dns修改成功）
  • 可以联网，但是xshell无法连接虚拟机

本机测试以上问题出现过，并且已解决

1.设置vmware虚拟机静态IP

2.win下cmd查看主机的dns后配置虚拟机文件

vi /etc/sysconfig/network-scripts/ifcfg-ens33

这里配置虚拟机NAT设置面板下的网关，掩码，及添加的虚拟机ip
GATEWAY=192.168.59.2
IPADDR=192.168.59.144 
NETMASK=255.255.255.0

3. 设置win网络

4. 重启网络：service network restart

5. 虚拟机停机后再重启可能会出现以下错误参照：www.cndba.cn/dave/articl…

  • 启动network可能报错
[root@www.cndba.cn~]# systemctl start network.service
Job for network.service failed because the control process exited with error code. See "systemctl status network.service" and "journalctl -xe" for details.
  • 先看下network状态
[root@www.cndba.cn~]# systemctl status network.service
● network.service - LSB: Bring up/down networking
   Loaded: loaded (/etc/rc.d/init.d/network; bad; vendor preset: disabled)
   Active: failed (Result: exit-code) since 日 2019-12-29 21:08:02 CST; 18s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 19628 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=1/FAILURE)

12月 29 21:08:02 dw8_monitor network[19628]: RTNETLINK answers: File exists
12月 29 21:08:02 dw8_monitor network[19628]: RTNETLINK answers: File exists
12月 29 21:08:02 dw8_monitor network[19628]: RTNETLINK answers: File exists
12月 29 21:08:02 dw8_monitor network[19628]: RTNETLINK answers: File exists
12月 29 21:08:02 dw8_monitor network[19628]: RTNETLINK answers: File exists
12月 29 21:08:02 dw8_monitor network[19628]: RTNETLINK answers: File exists
12月 29 21:08:02 dw8_monitor systemd[1]: network.service: control process exited, code=exited status=1
12月 29 21:08:02 dw8_monitor systemd[1]: Failed to start LSB: Bring up/down networking.
12月 29 21:08:02 dw8_monitor systemd[1]: Unit network.service entered failed state.
12月 29 21:08:02 dw8_monitor systemd[1]: network.service failed.

处理方式

  • systemctl stop NetworkManager
  • systemctl disable NetworkManager

重启

  • service network restart
  • ping以下百度是否联网正常，查看下ifconfig，xshell就能正常连接了

克隆VM 镜像快照重启后k8s出现以下问题

  1. 加入主节点失败
[root@com10-81 ~]# kubeadm join --token xxxx 10.4.37.167:6443 --discovery-token-ca-cert-hash sha256:xxxxxx
[preflight] Running pre-flight checks.
    [WARNING SystemVerification]: docker version is greater than the most recently validated version. Docker version: 17.12.1-ce. Max validated version: 17.03
    [WARNING FileExisting-crictl]: crictl not found in system path
[preflight] Some fatal errors occurred:
    [ERROR Port-10250]: Port 10250 is in use
    [ERROR FileAvailable--etc-kubernetes-pki-ca.crt]: /etc/kubernetes/pki/ca.crt already exists
    [ERROR FileAvailable--etc-kubernetes-kubelet.conf]: /etc/kubernetes/kubelet.conf already exists
  • kubeadm reset 重置后再次加入成功
  1. kubectl get pods命令出现如下错误
# kubectl get pods
W0504 22:52:02.915343   59377 loader.go:223] Config not found: /etc/kubernetes/admin.conf
The connection to the server localhost:8080 was refused - did you specify the right host or port?
  • 移动主节点的同一个目录配置到该虚拟机下
  • 重启：source ~/.bash_profile
  • kubectl get nodes 查看成功
avatar
文章
阅读
粉丝