hswaw

k0 is sadly ipv4-only, let's fix it.

Since dual-stack in Kubernetes is weird, we should probably focus on just IPv6 access to LoadBalancer services. I'm pretty sure some address translation system would let us map a chunk of our v6 to be used to access our v4 address space (or at least to part of the v4 space that's used for the k0 metallb pool), and that could be applied statelessly bidirectionally on our edge.