3 ms·
I've read the article twice. Did they just reinvent putting DHCP behind a NAT? What does that combination of systems not do that Fan does? *Remap 50 addresse
by stephengillie 11y ago
I've read the article twice. Did they just reinvent putting DHCP behind a NAT? What does that combination of systems not do that Fan does?
*Remap 50 addresses from one range to another.
*Dynamically assign those addresses to servers.
*Special Something that Fan does.
What's the benefit of using a full class A subnet when you are only using 250 addresses?
- dustinkirkland 11y agoSure, DHCP/NAT is used by each container, to get out. But how does it route to another container on some other host elsewhere in your cloud? That's what the Fan addresses.
- stephengillie 11y ago> Sure, DHCP/NAT is used by each container, to get out. So...Each physical host has its software networking pass through a NAT before hitting the physical adapter? And it's already using DHCP to assign addresses to its containers? > But how does it route to another container on some other host elsewhere in your cloud? That's what the Fan addresses. You use DNS to create a lookup table matching container to IP? Since this isn't being done, it must not work. What does Fan do instead? Is there some other complicating factor to which I'm ignorant? Are we talking about having multiple Kubernetes clusters inside containers inside VMs inside a physical host? Also, HOW does Fan address this problem? What does it use instead of one kind of database lookup or another, like a distributed database system such as DNS? Or does Fan use fancy subnet math?