So the table will route the packets to correct ~]# iptables -n -L -t nat | grep nodejs-ex The pod network subnet is 10.244.0.0/16 and broken up per host: Inet6 fe80::341b:eeff:fe06:7ec/64 scope linkĬni0 is a bridge where one side of the veth interface pair is ~]# bridge link showĦ: vethb4424886 state UP mtu 1450 master cni0 state forwarding priority 32 cost 2ħ: veth1657737b state UP mtu 1450 master cni0 state forwarding priority 32 cost 2Ĩ: vethdfd32c87 state UP mtu 1450 master cni0 state forwarding priority 32 cost 2ĩ: vethed0f8c9a state UP mtu 1450 master cni0 state forwarding priority 32 cost 2ġ0: veth05e4e005 state UP mtu 1450 master cni0 state forwarding priority 32 cost 2ġ1: veth25933a54 state UP mtu 1450 master cni0 state forwarding priority 32 cost 2ġ2: vethe3d701e7 state UP mtu 1450 master cni0 state forwarding priority 32 cost 2 Inet6 fe80::cc4e:fbff:fe41:1daf/64 scope linkĥ: cni0: mtu 1450 qdisc noqueue state UP qlen 1000 Link/ether ce:4e:fb:41:1d:af brd ff:ff:ff:ff:ff:ff Inet6 fe80::5054:ff:fe97:a6ee/64 scope linkĤ: flannel.1: mtu 1450 qdisc noqueue state UNKNOWN Review DNS for Services and Pods for additional ~]# ip aĢ: eth0: mtu 1500 qdisc pfifo_fast state UP qlen 1000 This allows us to use the hostname mongodb to connect to MongoDB. One each for mongodb and nodejs applications.
There are two services defined in the manifest that was deployed above.
Then we will finish up with two scenarios: virtual machine to virtual machine communication and ingress to virtual machine. Now that we have a clearier picture of kubevirt networking we will continue with details regarding kubernetes objects, host, pod and virtual machine networking components. The network details - the IP address, gateway, routes, DNS servers and suffixes are taken from the pod which will be served to the virtual machine. This DHCP server only provides a single address to a client in this case the virtual machine that will be started. StartDHCP → DHCPServer → SingleClientDHCPServer This will provide libvirt a bridge to use for the virtual machine that will be created. Once the current details of the pod interface have been stored following operations are performed:ĭelete the IP address from the pod interface This is stored for later use in configuring DHCP. This function gathers the following information about the pod interface: This function calls three functions that are detailed below discoverPodNetworkInterface, preparePodNetworkInterface and StartDHCP discoverPodNetworkInterface virtwrap managerīefore the virtual machine is started the preStartHook will run SetupPodNetwork. We are only going to concentrate on the network portion in this post.
Virt-launcher is the pod that runs the necessary components instantiate and run a virtual machine. KubeVirt networking virt-launcher - virtwrap
0 kommentar(er)
