https://eljirari.me/tags/networking/Recent content in networking on Youssef El JirariHugo -- gohugo.ioenhttps://eljirari.me/posts/ipam-at-scale/Mon, 01 Jan 0001 00:00:00 +0000https://eljirari.me/posts/ipam-at-scale/IP address management looks unnecessary when the environment is small. You have a few VNets, somebody keeps a spreadsheet with the CIDRs, and before creating a new network you check that the range is not already used. It works. Then the cloud estate grows. You have tens or hundreds of subscriptions, multiple regions, separate production and non-production environments, connectivity hubs, private endpoints, on-premises networks and different teams deploying infrastructure independently. At that point, the problem is no longer which CIDR should I use?https://eljirari.me/posts/kubernetes-cni/Mon, 01 Jan 0001 00:00:00 +0000https://eljirari.me/posts/kubernetes-cni/When people compare Kubernetes CNIs, the discussion quickly becomes a feature matrix. Does it support NetworkPolicy? BGP? eBPF? Encryption? Observability? Those are useful questions, but I think they miss the first one: What networking problem does this cluster actually need the CNI to solve? A three-node K3s cluster and a large multi-tenant Kubernetes platform do not need the same network architecture. Start with what the CNI does A pod needs an IP address and it needs to communicate with other pods.