this post was submitted on 19 Jun 2024
312 points (85.5% liked)

Programmer Humor

19572 readers
978 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 1 year ago
MODERATORS
 

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

you are viewing a single comment's thread
view the rest of the comments
[–] Thiakil@aussie.zone 1 points 5 months ago (1 children)

Point is, you should be able to have them have both. Or stick a reverse proxy in front that can translate. Unless they're somehow meant to be directly internet reachable the public addresses could be autogenerated

Full disclosure though I don't know anything about kubernetes.

[–] jlh@lemmy.jlh.name 1 points 5 months ago (1 children)

Yeah, I wonder if there's any proposals to allow for multiple IPV6 addresses in Kubernetes, it would be a much better solution than NAT.

As far as I know, it's currently not possible. Every container/Pod receives a single IPv4 and/or IPv6 address on creation from the networking driver.

[–] Thiakil@aussie.zone 2 points 5 months ago (1 children)

Even if you give it multiple ip6 cidrs to allocate?

[–] jlh@lemmy.jlh.name 1 points 5 months ago (1 children)

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.

[–] Thiakil@aussie.zone 2 points 4 months ago

Weird! Though I guess a lot of these would be sitting behind load balancers / reverse proxies anyway (so ipv4 is fine) and unlikely to up and change isps very often? Lol

If I had to, I'd be trying to add an extra cidr to one of the options listed at https://kubernetes.io/docs/concepts/services-networking/dual-stack/#configure-ipv4-ipv6-dual-stack But as you say, probably doesn't work!