The container orchestrator landscape [LWN.net]

The container orchestrator landscape

Posted Aug 24, 2022 7:58 UTC (Wed) by bartoc (guest, #124262)
In reply to: The container orchestrator landscape by rjones
Parent article: The container orchestrator landscape

> The idea is that you needed to have a way for Kubernetes to easily adapt to a wide variety of different cloud architectures. The people that are running them don't have control over the addresses they get, addresses are very expensive, and they don't have control over any of the network infrastructure. Ipv6 isn't even close to a option for most of these types of setup.

Well, I don't care about any cloud architectures except mine :). More seriously though the people running clouds absolutely do have control over the addresses they get! And tunneling works just as well if you want to provide access to the ipv6 internet on container hosts that only have ipv4, except in that situation you have some hope of getting rid of the tunnels once you no longer need ipv4.

> Generally speaking you'll want to have 3 LANs. One for the pod network, one for the service network, and one for external network. More sophisticated setups might want to have a dedicated network for storage on top of that, and I am sure that people can find uses for even more then that.

IMO this is _nuts_, I want _ONE_ network and I want that network to be the internet (with stateful firewalls, obviously).