关键词：
一、Flannel网络部署
为Flannel生成证书
[[email protected] ssl]# vim flanneld-csr.json "CN": "flanneld", "hosts": [], "key": "algo": "rsa", "size": 2048 , "names": [ "C": "CN", "ST": "BeiJing", "L": "BeiJing", "O": "k8s", "OU": "System" ]
生成证书
[[email protected] ssl]# cfssl gencert -ca=/opt/kubernetes/ssl/ca.pem -ca-key=/opt/kubernetes/ssl/ca-key.pem -config=/opt/kubernetes/ssl/ca-config.json -profile=kubernetes flanneld-csr.json | cfssljson -bare flanneld 2018/05/31 16:19:46 [INFO] generate received request 2018/05/31 16:19:46 [INFO] received CSR 2018/05/31 16:19:46 [INFO] generating key: rsa-2048 2018/05/31 16:19:46 [INFO] encoded CSR 2018/05/31 16:19:46 [INFO] signed certificate with serial number 655739903410343916627289078414999108781865584022 2018/05/31 16:19:46 [WARNING] This certificate lacks a "hosts" field. This makes it unsuitable for websites. For more information see the Baseline Requirements for the Issuance and Management of Publicly-Trusted Certificates, v.1.1.6, from the CA/Browser Forum (https://cabforum.org); specifically, section 10.2.3 ("Information Requirements"). [[email protected]-node1 ssl]# ll flanneld* -rw-r--r-- 1 root root 997 May 31 16:19 flanneld.csr -rw-r--r-- 1 root root 221 May 31 16:18 flanneld-csr.json -rw------- 1 root root 1679 May 31 16:19 flanneld-key.pem -rw-r--r-- 1 root root 1391 May 31 16:19 flanneld.pem
分发证书
[[email protected] ssl]# scp flanneld*.pem 192.168.56.12:/opt/kubernetes/ssl/ [[email protected]-node1 ssl]# scp flanneld*.pem 192.168.56.13:/opt/kubernetes/ssl/
下载Flannel软件包
# wget https://github.com/coreos/flannel/releases/download/v0.10.0/flannel-v0.10.0-linux-amd64.tar.gz [[email protected]-node1 ssl]# cd /usr/local/src/ [[email protected]-node1 src]# pwd /usr/local/src [[email protected]-node1 src]# tar zxf flannel-v0.10.0-linux-amd64.tar.gz [[email protected]-node1 src]# cp flanneld mk-docker-opts.sh /opt/kubernetes/bin/ #复制到linux-node2、linux-node3节点上 [[email protected]-node1 src]# scp flanneld mk-docker-opts.sh 192.168.56.12:/opt/kubernetes/bin/ [[email protected]-node1 src]# scp flanneld mk-docker-opts.sh 192.168.56.13:/opt/kubernetes/bin/ 复制对应脚本到/opt/kubernetes/bin目录下。 [[email protected]-node1 src]# cd /usr/local/src/kubernetes/cluster/centos/node/bin/ [[email protected]-node1 bin]# ll total 8 -rwxr-xr-x 1 root root 2590 Apr 12 23:24 mk-docker-opts.sh -rwxr-xr-x 1 root root 850 Apr 12 23:24 remove-docker0.sh [[email protected]-node1 bin]# cp remove-docker0.sh /opt/kubernetes/bin/ [[email protected]-node1 bin]# scp remove-docker0.sh 192.168.56.12:/opt/kubernetes/bin/ [[email protected]-node1 bin]# scp remove-docker0.sh 192.168.56.13:/opt/kubernetes/bin/
配置Flannel
[[email protected] bin]# vim /opt/kubernetes/cfg/flannel FLANNEL_ETCD="-etcd-endpoints=https://192.168.56.11:2379,https://192.168.56.12:2379,https://192.168.56.13:2379" FLANNEL_ETCD_KEY="-etcd-prefix=/kubernetes/network" FLANNEL_ETCD_CAFILE="--etcd-cafile=/opt/kubernetes/ssl/ca.pem" FLANNEL_ETCD_CERTFILE="--etcd-certfile=/opt/kubernetes/ssl/flanneld.pem" FLANNEL_ETCD_KEYFILE="--etcd-keyfile=/opt/kubernetes/ssl/flanneld-key.pem" 复制配置到其它节点上 [[email protected]-node1 bin]# scp /opt/kubernetes/cfg/flannel 192.168.56.12:/opt/kubernetes/cfg/ [[email protected]-node1 bin]# scp /opt/kubernetes/cfg/flannel 192.168.56.13:/opt/kubernetes/cfg/
设置Flannel系统服务
[[email protected] bin]# vim /usr/lib/systemd/system/flannel.service [[email protected]-node1 bin]# cat /usr/lib/systemd/system/flannel.service [Unit] Description=Flanneld overlay address etcd agent After=network.target Before=docker.service [Service] EnvironmentFile=-/opt/kubernetes/cfg/flannel ExecStartPre=/opt/kubernetes/bin/remove-docker0.sh ExecStart=/opt/kubernetes/bin/flanneld $FLANNEL_ETCD $FLANNEL_ETCD_KEY $FLANNEL_ETCD_CAFILE $FLANNEL_ETCD_CERTFILE $FLANNEL_ETCD_KEYFILE ExecStartPost=/opt/kubernetes/bin/mk-docker-opts.sh -d /run/flannel/docker Type=notify [Install] WantedBy=multi-user.target RequiredBy=docker.service 复制系统服务脚本到其它节点上 [[email protected]-node1 bin]# scp /usr/lib/systemd/system/flannel.service 192.168.56.12:/usr/lib/systemd/system/ [[email protected]-node1 bin]# scp /usr/lib/systemd/system/flannel.service 192.168.56.13:/usr/lib/systemd/system/
二、Flannel CNI集成
下载CNI插件
#下载CNI插件 https://github.com/containernetworking/plugins/releases wget https://github.com/containernetworking/plugins/releases/download/v0.7.1/cni-plugins-amd64-v0.7.1.tgz [[email protected] bin]# mkdir /opt/kubernetes/bin/cni
[[email protected] ssl]# mkdir /opt/kubernetes/bin/cni
[[email protected] ssl]# mkdir /opt/kubernetes/bin/cni
[[email protected]-node1 bin]# cd /usr/local/src/ [[email protected]-node1 src]# tar zxf cni-plugins-amd64-v0.7.1.tgz -C /opt/kubernetes/bin/cni [[email protected]-node1 src]# scp -r /opt/kubernetes/bin/cni/* 192.168.56.12:/opt/kubernetes/bin/cni/ [email protected] src]# scp -r /opt/kubernetes/bin/cni/* 192.168.56.13:/opt/kubernetes/bin/cni/
创建Etcd的key
[email protected] src]# /opt/kubernetes/bin/etcdctl --ca-file /opt/kubernetes/ssl/ca.pem --cert-file /opt/kubernetes/ssl/flanneld.pem --key-file /opt/kubernetes/ssl/flanneld-key.pem --no-sync -C https://192.168.56.11:2379,https://192.168.56.12:2379,https://192.168.56.13:2379 \ mk /kubernetes/network/config ‘ "Network": "10.2.0.0/16", "Backend": "Type": "vxlan", "VNI": 1 ‘ >/dev/null 2>&1
启动flannel
######################linux-node1启动############################# [[email protected]-node1 src]# systemctl daemon-reload [[email protected]-node1 src]# systemctl enable flannel Created symlink from /etc/systemd/system/multi-user.target.wants/flannel.service to /usr/lib/systemd/system/flannel.service. Created symlink from /etc/systemd/system/docker.service.requires/flannel.service to /usr/lib/systemd/system/flannel.service. [[email protected]-node1 src]# chmod +x /opt/kubernetes/bin/* [[email protected] src]# systemctl start flannel ######################linux-node2启动############################# [[email protected] src]# systemctl daemon-reload [[email protected] src]# systemctl enable flannel Created symlink from /etc/systemd/system/multi-user.target.wants/flannel.service to /usr/lib/systemd/system/flannel.service. Created symlink from /etc/systemd/system/docker.service.requires/flannel.service to /usr/lib/systemd/system/flannel.service. [[email protected] src]# chmod +x /opt/kubernetes/bin/* [[email protected] src]# systemctl start flannel ######################linux-node3启动############################# [[email protected] ssl]# systemctl daemon-reload [[email protected] ssl]# systemctl enable flannel Created symlink from /etc/systemd/system/multi-user.target.wants/flannel.service to /usr/lib/systemd/system/flannel.service. Created symlink from /etc/systemd/system/docker.service.requires/flannel.service to /usr/lib/systemd/system/flannel.service. [[email protected] ssl]# chmod +x /opt/kubernetes/bin/* [[email protected] ssl]# systemctl start flannel
查看服务状态
[[email protected] src]# systemctl status flannel
[[email protected] src]# systemctl status flannel
[[email protected] ssl]# systemctl status flannel
[[email protected]node1 src]# ifconfig eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.56.11 netmask 255.255.255.0 broadcast 192.168.56.255 inet6 fe80::20c:29ff:fea0:10ca prefixlen 64 scopeid 0x20<link> ether 00:0c:29:a0:10:ca txqueuelen 1000 (Ethernet) RX packets 386026 bytes 62831393 (59.9 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 768980 bytes 1204891659 (1.1 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 flannel.1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1450 inet 10.2.9.0 netmask 255.255.255.255 broadcast 0.0.0.0 inet6 fe80::2404:bbff:fee0:41a6 prefixlen 64 scopeid 0x20<link> ether 26:04:bb:e0:41:a6 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 8 overruns 0 carrier 0 collisions 0 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1 (Local Loopback) RX packets 232562 bytes 59255512 (56.5 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 232562 bytes 59255512 (56.5 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
[[email protected]node2 src]# ifconfig eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.56.12 netmask 255.255.255.0 broadcast 192.168.56.255 inet6 fe80::20c:29ff:fef9:ca25 prefixlen 64 scopeid 0x20<link> ether 00:0c:29:f9:ca:25 txqueuelen 1000 (Ethernet) RX packets 669708 bytes 372005370 (354.7 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 470811 bytes 63787801 (60.8 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 flannel.1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1450 inet 10.2.13.0 netmask 255.255.255.255 broadcast 0.0.0.0 inet6 fe80::4031:7ff:fe2d:9c2f prefixlen 64 scopeid 0x20<link> ether 42:31:07:2d:9c:2f txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 8 overruns 0 carrier 0 collisions 0 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1 (Local Loopback) RX packets 960 bytes 72576 (70.8 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 960 bytes 72576 (70.8 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
[[email protected]node3 ssl]# ifconfig eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.56.13 netmask 255.255.255.0 broadcast 192.168.56.255 inet6 fe80::20c:29ff:feca:800d prefixlen 64 scopeid 0x20<link> ether 00:0c:29:ca:80:0d txqueuelen 1000 (Ethernet) RX packets 548452 bytes 359854149 (343.1 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 353542 bytes 51778767 (49.3 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 flannel.1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1450 inet 10.2.17.0 netmask 255.255.255.255 broadcast 0.0.0.0 inet6 fe80::c86c:3ff:fe2e:d4ca prefixlen 64 scopeid 0x20<link> ether ca:6c:03:2e:d4:ca txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 8 overruns 0 carrier 0 collisions 0 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1 (Local Loopback) RX packets 804 bytes 48598 (47.4 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 804 bytes 48598 (47.4 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
[[email protected] ssl]# cat /run/flannel/docker DOCKER_OPT_BIP="--bip=10.2.17.1/24" DOCKER_OPT_IPMASQ="--ip-masq=true" DOCKER_OPT_MTU="--mtu=1450" DOCKER_OPTS=" --bip=10.2.17.1/24 --ip-masq=true --mtu=1450"
三、配置Docker使用Flannel
[email protected] ~]# vim /usr/lib/systemd/system/docker.service [Unit] #在Unit下面修改After和增加Requires After=network-online.target firewalld.service flannel.service Wants=network-online.target Requires=flannel.service [Service] #增加EnvironmentFile=-/run/flannel/docker Type=notify EnvironmentFile=-/run/flannel/docker ExecStart=/usr/bin/dockerd $DOCKER_OPTS
将配置复制到另外两个节点
[[email protected] src]# scp /usr/lib/systemd/system/docker.service 192.168.56.12:/usr/lib/systemd/system/ [[email protected]-node1 src]# scp /usr/lib/systemd/system/docker.service 192.168.56.13:/usr/lib/systemd/system/
重启Docker
#####################linux-node1重启Docker服务######################## [[email protected]-node1 src]# systemctl daemon-reload [[email protected]-node1 src]# systemctl restart docker #####################linux-node3重启Docker服务######################## [[email protected]-node2 src]# systemctl daemon-reload [[email protected]-node2 src]# systemctl restart docker #####################linux-node3重启Docker服务######################## [[email protected]-node3 ssl]# systemctl daemon-reload [[email protected]-node3 ssl]# systemctl restart docker
[[email protected]node1 src]# ifconfig docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 inet 10.2.9.1 netmask 255.255.255.0 broadcast 10.2.9.255 ether 02:42:18:d5:e0:d1 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.56.11 netmask 255.255.255.0 broadcast 192.168.56.255 inet6 fe80::20c:29ff:fea0:10ca prefixlen 64 scopeid 0x20<link> ether 00:0c:29:a0:10:ca txqueuelen 1000 (Ethernet) RX packets 426666 bytes 68740555 (65.5 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 809174 bytes 1211522272 (1.1 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 flannel.1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1450 inet 10.2.9.0 netmask 255.255.255.255 broadcast 0.0.0.0 inet6 fe80::2404:bbff:fee0:41a6 prefixlen 64 scopeid 0x20<link> ether 26:04:bb:e0:41:a6 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 8 overruns 0 carrier 0 collisions 0 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1 (Local Loopback) RX packets 254544 bytes 65389446 (62.3 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 254544 bytes 65389446 (62.3 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
[[email protected]node2 src]# ifconfig docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 inet 10.2.13.1 netmask 255.255.255.0 broadcast 10.2.13.255 ether 02:42:6a:cf:66:9f txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.56.12 netmask 255.255.255.0 broadcast 192.168.56.255 inet6 fe80::20c:29ff:fef9:ca25 prefixlen 64 scopeid 0x20<link> ether 00:0c:29:f9:ca:25 txqueuelen 1000 (Ethernet) RX packets 724138 bytes 379110250 (361.5 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 524129 bytes 71071850 (67.7 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 flannel.1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1450 inet 10.2.13.0 netmask 255.255.255.255 broadcast 0.0.0.0 inet6 fe80::4031:7ff:fe2d:9c2f prefixlen 64 scopeid 0x20<link> ether 42:31:07:2d:9c:2f txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 8 overruns 0 carrier 0 collisions 0 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1 (Local Loopback) RX packets 1264 bytes 88416 (86.3 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1264 bytes 88416 (86.3 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
[[email protected]node3 ssl]# ifconfig docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 inet 10.2.17.1 netmask 255.255.255.0 broadcast 10.2.17.255 ether 02:42:e3:78:53:2d txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.56.13 netmask 255.255.255.0 broadcast 192.168.56.255 inet6 fe80::20c:29ff:feca:800d prefixlen 64 scopeid 0x20<link> ether 00:0c:29:ca:80:0d txqueuelen 1000 (Ethernet) RX packets 584443 bytes 365047002 (348.1 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 390601 bytes 57109546 (54.4 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 flannel.1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1450 inet 10.2.17.0 netmask 255.255.255.255 broadcast 0.0.0.0 inet6 fe80::c86c:3ff:fe2e:d4ca prefixlen 64 scopeid 0x20<link> ether ca:6c:03:2e:d4:ca txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 8 overruns 0 carrier 0 collisions 0 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1 (Local Loopback) RX packets 880 bytes 52582 (51.3 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 880 bytes 52582 (51.3 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
kubernetes二进制部署——flannel网络(代码片段)
Kubernetes二进制部署——Flannel网络一、Flannel简介二、Flannel原理三、Flannel的作用四、Flannel网络配置1.node节点安装docker2.master配置1、写入分配的子网段到ETCD中，供flannel使用(master主机）3、node节点操作1、上传flannel软件包到... 查看详情
kubernetes二进制部署——flannel网络(代码片段)
Kubernetes二进制部署——Flannel网络一、Flannel简介二、Flannel原理三、Flannel的作用四、Flannel网络配置1.node节点安装docker2.master配置1、写入分配的子网段到ETCD中，供flannel使用(master主机）3、node节点操作1、上传flannel软件包到... 查看详情
kubernetes二进制部署——flannel网络(代码片段)
Kubernetes二进制部署——Flannel网络一、Flannel简介二、Flannel原理三、Flannel的作用四、Flannel网络配置1.node节点安装docker2.master配置1、写入分配的子网段到ETCD中，供flannel使用(master主机）3、node节点操作1、上传flannel软件包到... 查看详情
dockerflannel网络部署和路由走向分析(代码片段)
1.flannel介绍flannel是coreos开发的容器网络解决方案。flannel为每个host分配一个subnet，容器从此subnet中分配ip。这些ip可以在host间路由，容器间无需nat和portmapping就可以跨主机通讯。每个subnet都是从一个更大的ip池中划分的，flannel会... 查看详情
k8s单master部署二：flannel网络部署(代码片段)
以下所有操作均在node节点进行Flannel网络概述Flannel通过给每台宿主机分配一个子网的方式为容器提供虚拟网络，它基于LinuxTUN/TAP，使用UDP/VXLAN封装IP包来创建overlay网络，并借助etcd(也支持kubernetes)维护网络的分配情况。服务器角... 查看详情
第三篇（二进制部署k8s集群---flannel网络和keepalived+haproxy高可用）(代码片段)
此文将搭建flannel网络，目的使跨主机的docker能够互相通信，也是保障kubernetes集群的网络基础和保障，和ha高可用。部署的服务器为：master1192.168.206.31master2192.168.206.32master3192.168.206.33node1192.168.206.41node2192.168.206.42node3192.168.206.43VIP... 查看详情
kubernetes集群之二进制安装部署（单master节点）(代码片段)
...验证etcd集群状态四、在所有Node节点上部署Docker引擎五、Flannel网络配置5.1不同Node上Pod之间的通信？5.2通信方式之：OverlayNetwork与VXLAN5.3Flannel介绍5.4Flannel的工作流程5.5ETCD之Flannel提供说明5.6Flannel配置配置步骤5.6.1在Master01节... 查看详情
kubernetes节点服务搭建————二进制部署|单master节点配置（一)(etcd和flannel)(代码片段)
...集群master01上操作部署在node节点上修改配置部署Docker引擎flannel网络配置常见的通信方式flannel的工作流程flannel的搭建部署总结常见的K8s按照部署方式MinikubeMinikube是一个工具，可以在本地快速运行一个单节点微型K8S，仅用... 查看详情
kubernetes节点服务搭建————二进制部署|单master节点配置（一)(etcd和flannel)(代码片段)
...集群master01上操作部署在node节点上修改配置部署Docker引擎flannel网络配置常见的通信方式flannel的工作流程flannel的搭建部署总结常见的K8s按照部署方式MinikubeMinikube是一个工具，可以在本地快速运行一个单节点微型K8S，仅用... 查看详情
k8s安装pod网络插件（flannel）报错(代码片段)
问题描述：我在用kubeadm方式部署k8s，安装pod网络插件的时候出现以下报错[root@masterk8s]#kubectlapply-fhttps://raw.githubusercontent.com/coreos/flannel/a70459be0084506e4ec919aa1c114638878db11b/Documentation/kube-f 查看详情
flannel网络问题：node节点flannel网络问题导致该node上的pod与其他node节点网络不通的排查思路与解决(代码片段)
flannel网络问题：node节点flannel网络问题导致该node上的pod与其他node节点网络不通的排查思路与解决一、问题发现二、问题排查一、问题发现在部署一个replicas：4的nginxdeployment之后在master节点通过curl+podIP+端口的形式... 查看详情
运维实战容器部分kubernetes集群部署(代码片段)
...实践ClusterIP方式创建ServiceMatalLBIngressK8S网络通信使用场景Flannelvxlan模式跨主机通信原理Flannel网络Flannel网络原理Flannel支持的后端配置FlannelCalico网络插件入门简介网络架构Calico网络插件Calico网络策略实验限制访问指定服务允许指... 查看详情
kubernetes二进制部署（单master节点）（理论部分，详细部署步骤在下一篇哦~）(代码片段)
...流程5、使用证书访问的工作流程:四、部署docker引擎五、flannel网络配置1、K8S中Pod网络通信:2、Flannel3、Flannel工作原理:4、搭建flannel5、flannel的操作流程一、部署master组件二、部署node组件三、搭建流程master搭建流程node搭建流程k8s... 查看详情
二进制部署k8s单节点(代码片段)
...群状态二、Node部署docker1.所有node部署docker2.镜像加速三、Flannel容器集群网络部署1.写入分配的子网段到etcd中，供flanel使用2.拷贝flannel包到node节点3.配置文件和启动脚本4.启动flannel5.配置docker连接flannel6.重启docker7.查看flannel网... 查看详情
linux企业运维——kubernetesk8s网络通信(代码片段)
...Kubernetes（七）k8s网络通信1、k8s网络通信简介2、flannel网络2.1、flannel网络简介2.2、flannel网络原理2.3、flannel配置3、calico网络插件3.1、calico简介3.2、calico的安装部署4、 查看详情
flannel配置详解(代码片段)
目录1、简介2、Flannel实现原理2.1、原理说明2.2、数据转发流程3、Flannel安装配置3.1、环境准备3.2、安装etcd3.3、安装Flannel3.4、启动Flannel3.5、验证Flannel网络3.6、配置Docker3.7、验证容器互通3.8、配置backend为host-gw1、简介Flannel是一种... 查看详情
k8s部署flannel网络
1yum安装flannel包：yuminstallflannel-y2编辑配置文件vim/etc/sysconfig/flanneldFLANNEL_ETCD_ENDPOINTS="http://192.168.233.130:2379"FLANNEL_ETCD_PREFIX="/coreos.com/network"#FLANNEL_OPTIONS=&qu 查看详情
kubernetes节点服务搭建————二进制部署|单master节点配置（一)(etcd和flannel)(代码片段)
...集群master01上操作部署在node节点上修改配置部署Docker引擎flannel网络配置常见的通信方式flannel的工作流程flannel的搭建部署总结常见的K8s按照部署方式MinikubeMinikube是一个工具，可以在本地快速运行一个单节点微型K8S，仅用... 查看详情