Can be if the same IP exists on multiple nodes than literally it's on the nodes NICs a you said but doesn't mean that the VIP is used by all of them. It floats. So in those circumstances floating value of that NIC which is the IP itself can be and should be outside the box because it moves whenever it needs.
I want to pods running on independent host with static ip and want to communicate with pods running in Kubernetes cluster. Only way to communicate is using static ip. How can I do that? I tried to use weavenet, but it works fine between two independent hosts, I can join multiple hosts to weavenet but how can I make it work with Kubernetes cluster.
Great talk!
The audio quality degrades after the 35 minute mark in the Q&A then it gets good again.
Is this possible to demonstrate in packet tracer for example?
Neat rundown of the options in Pod Internetworking, thanks.
The audio clips all the time, the talk is great though
25:40 : I think the VIP is assigned to the node. ( Same NIC with multiple IPs ) If this is true, VIP should not be shown as a box outside the cluster.
Can be if the same IP exists on multiple nodes than literally it's on the nodes NICs a you said but doesn't mean that the VIP is used by all of them. It floats. So in those circumstances floating value of that NIC which is the IP itself can be and should be outside the box because it moves whenever it needs.
I want to pods running on independent host with static ip and want to communicate with pods running in Kubernetes cluster. Only way to communicate is using static ip. How can I do that? I tried to use weavenet, but it works fine between two independent hosts, I can join multiple hosts to weavenet but how can I make it work with Kubernetes cluster.
k8s great
cluster CIDR range doesn't have to be "taken" from the network range right? so Cluster:10.0.0.0/16 has nothing to do with Network:10.0.0.0/8?
That's just for model