Today in our newest take on “older technology is better”: why NAT rules!

  • Thiakil
    link
    fedilink
    arrow-up
    2
    ·
    5 months ago

    Even if you give it multiple ip6 cidrs to allocate?

    • Justin@lemmy.jlh.name
      link
      fedilink
      English
      arrow-up
      1
      ·
      5 months ago

      I haven’t really looked into it, but it doesn’t seem like it.

      Heres the documentation about having multiple cidr pools in one cluster with the Cilium network driver, and it seems to imply that each Pod only gets one IP.

      https://docs.cilium.io/en/stable/network/concepts/ipam/multi-pool/

      There’s something called Multus that I haven’t looked into, but even then it looks like that is for multiple interfaces per Pod, not multiple IPS per interface.

      https://github.com/k8snetworkplumbingwg/multus-cni

      Containers are just network namespaces on Linux, and all the routing is done in iptables or ebpf, so it’s theoretically possible to have multiple IP addresses, but doesn’t look like anybody has started implementing it. There’s actually a lot of Kubernetes clusters that just use stateful IPv6 NAT for the internal Pod network, unfortunately.