Hello! How difficult would it be change the pods' and services' subnets on RKE2 rancher?

not supported to change these post cluster creation

Thanks. I guess I could create a new cluster with the new subnets and move the nodes one by one.

github.com/rancher/rke2/issues/2326 I am sure there are people that have done it - and could be successfully.. this is ultimately your decision ; especially if this is your production - mission critical environment and if you want to take that chance even so, I would probably spin up a new environment and experiment there before trying in prod

Yeah, testing it before goes without saying, of course.

If you are addressing IP exhaustion... I know Amazon created a "work around" to deal with IP exhaustion (not sure if that is what you are solving for) aws.amazon.com/blogs/containers/addressing-ipv4-address-exhaustion-in-amazon-eks-clusters-using-private-nat-gateways I recalled that Cilium also had shared they had a solution - which is not EKS-specific isovalent.com/blog/post/overcoming-kubernetes-ip-address-exhaustion-with-cilium I think, generally, the advice is to deploy a new cluster and migrate stateful data.

No, it's about subnet overlapping.

that ^^^ was always a struggle, especially in the early days - I'd be talking with customers about the infra requirements and inevitably the CIDR for Pod/Security/Machines would come up and either the systems team, or the infra team would ask: what on earth do you need a /16 for (I was at Red Hat back then)

🙂 In my case the IT departament just chose the wrong subnet, because... well... this is what they are like. They generally manage the network, so they don't have much of an excuse. Anyway, in the meantime they said that they would change the subnet on the other end, so I won't be needing to change the subnet on the kubernetes cluster anymore. So I guess that's fine, although the process would have interested me – I would have liked to see if I could do it without having to set up a new cluster, even if it were offline.

sounds fortunate they were able to change on their side this time - and now they have an idea of how to collab to avoid in the future! 😉

Yeah. Well, actually they were mostly responsible for this. But yeah 🙂