With Cilium 1.18, platform engineers can now apply ingress bandwidth limits to pods using a simple Kubernetes annotation, Nico Vibert demonstrates this new feature! Today I'm going to talk about a feature called ingress bandwidth manager. It's a network quality of service feature coming in Cilium 1.18. This feature enables you to control and shape traffic coming into your pod, essentially limiting the amount of traffic that can enter your pod. We've supported what we call egress bandwidth management, which is traffic leaving the pod, for a couple of years. In 1.18, we're now able to control the traffic coming into the pod as well, shaping the traffic on ingress. The beauty of this is that it's really simple. You just need to add an annotation to your pod to say you want the traffic coming into the pod to be limited down to whatever rate you want to set. So let's take a look at a demo. My demo environment is running in AKS. I've got an Azure Kubernetes Service cluster that I deployed in BYO CNI mode, so without a CNI to begin with, and I installed Cilium 1.18 preview zero, which is one of the first beta releases available for Cilium 1.18. Cilium looks good, and we've also enabled the bandwidth manager feature. Let me just double-check that. Here we go. It's quite simple. I've got two pods: one server and one client. They're going to run network performance testing with iperf between the two, and they're located on two different nodes, as you can see here. The IP address of my server is 10.0.2.58. So I'm going to go to my client and run an iperf test against 10.0.2.58, and we're going to see that right now I haven't enforced any traffic control. We're expecting to see over one gigabit, around 1.3 Gbps, which is usually what I get between two pods in AKS running Cilium before we apply any form of traffic shaping. Now, the way to do it with Cilium and bandwidth manager is simply by annotating the pod with a special annotation. We're going to go to our server and add the kubernetes.io/ingress-bandwidth annotation, and let's bring it down to 20M. That's it. Now we're going to run our test again, and I'm expecting to be roughly around 20 Mbps. So that's pretty much all you need to do. Again, you can go ahead and test it. Maybe you'll see 21 or 22 Mbps from the traffic-shaping test. If you want, we can even try 2M if we really want to reduce the bandwidth being used by a particular pod. I just modify the annotation on the server specification, and the ingress bandwidth will be reduced down to around 2 Mbps. Perfect, and that's it. That's all for today. Thank you for watching, and I will see you in the next one.