The container orchestrator landscape

Posted Aug 26, 2022 1:25 UTC (Fri) by thockin (guest, #158217)
In reply to: The container orchestrator landscape by bartoc
Parent article: The container orchestrator landscape

> One thing that always really annoyed me about k8s is the whole networking stack and networking requirements. My servers have real ipv6 addresses, that are routable from everywhere and I really, really do not want to deal with some insane BGP overlay. Each host can good and well get (at least) a /60 that can be further subdivided for each container.

You don't need an overlay if you already have a decent sized range of IPs per node. Just use those IPs.

I don't know where the idea that you NEED an overlay comes from. If you have IPs, just use those. That's what it was designed for.

The container orchestrator landscape

Posted Aug 26, 2022 23:18 UTC (Fri) by bartoc (guest, #124262) [Link]

When I was setting this up I found the supporting infrastructure for just using real ipv6 was really poor. You at least need something to read out whatever prefix you got from DHCP-PD and set up forwarding rules, and either set addresses on the VMs, or start a copy of radvd facing the containers and tell it about said prefix.

Or you could use a virtual switch, that would probably "just work"