Welcome to Cilium’s documentation! The documenta�on is divided into the following sec�ons: Ge�ng Started Guides: Provides a simple tutorial for running a small Cilium setup on your laptop. Intended as how these components integrate with exis�ng architectures, such as Kubernetes. Installa�on : Details instruc�ons for installing, configuring, and troubleshoo�ng Cilium in different deployment modes. Policy formats. Monitoring & Metrics : Instruc�ons for configuring metrics collec�on from Cilium. Troubleshoo�ng : Describes how to troubleshoot Cilium in different deployment modes. BPF and XDP Reference Guide

ng-25560078 2019-07-23T06:05:35Z 0 2 0 m5.large ami- 0923e4b35a30a5f53 eksctl scale nodegroup --cluster eni-cluster -n ng-25560078 -N 2 2 [ℹ] scaling nodegroup stack "eksctl-test-cluster-nodegroup-ng- 25560078" in cluster eksctl-test-cluster-cluster [ℹ] scaling nodegroup, desired capacity from 0 to 2 Validate the Installation You can SetAccessCode and GetStatus while still allowing GetName, GetLocation, and RequestMaintenance? Since gRPC build on top of HTTP, this can be achieved easily by understanding how a gRPC call is mapped to an HTTP

ng-25560078 2019-07-23T06:05:35Z 0 2 0 m5.large ami- 0923e4b35a30a5f53 eksctl scale nodegroup --cluster test-cluster -n ng-25560078 -N -N 2 [ℹ] scaling nodegroup stack "eksctl-test-cluster-nodegroup-ng- 25560078" in cluster eksctl-test-cluster-cluster [ℹ] scaling nodegroup, desired capacity from 0 to 2 Validate the Installation You SetAccessCode and GetStatus while still allowing GetName, GetLocation, and RequestMaintenance? Since gRPC build on top of HTTP, this can be achieved easily by understanding how a gRPC call is mapped to an HTTP

io/v1alpha5 kind: ClusterConfig metadata: name: ${NAME} region: eu-west-1 managedNodeGroups: - name: ng-1 desiredCapacity: 2 privateNetworking: true # taint nodes so that application pods are # not create the cluster: apiVersion: eksctl.io/v1alpha5 kind: ClusterConfig ... managedNodeGroups: - name: ng-1 ... # taint nodes so that application pods are # not scheduled/executed until Cilium is deployed create the cluster: apiVersion: eksctl.io/v1alpha5 kind: ClusterConfig ... managedNodeGroups: - name: ng-1 ... # taint nodes so that application pods are # not scheduled/executed until Cilium is deployed

io/v1alpha5 kind: ClusterConfig metadata: name: ${NAME} region: eu-west-1 managedNodeGroups: - name: ng-1 desiredCapacity: 2 privateNetworking: true # taint nodes so that application pods are # not create the cluster: apiVersion: eksctl.io/v1alpha5 kind: ClusterConfig ... managedNodeGroups: - name: ng-1 ... # taint nodes so that application pods are # not scheduled/executed until Cilium is deployed create the cluster: apiVersion: eksctl.io/v1alpha5 kind: ClusterConfig ... managedNodeGroups: - name: ng-1 ... # taint nodes so that application pods are # not scheduled/executed until Cilium is deployed

SetAccessCode and GetStatus while still allowing GetName, GetLocation, and RequestMaintenance? Since gRPC build on top of HTTP, this can be achieved easily by understanding how a gRPC call is mapped to an HTTP .. graceful restart; } Setting up Cluster Mesh This is a step-by-step guide on how to build a mesh of Kubernetes clusters by connecting them together, enabling pod-to-pod connectivity across io/v1alpha5 kind: ClusterConfig metadata: name: test-cluster region: us-west-2 nodeGroups: - name: ng-1 instanceType: m5n.xlarge desiredCapacity: 2 ssh: allow: true The nodegroup is created

SetAccessCode and GetStatus while still allowing GetName, GetLocation, and RequestMaintenance? Since gRPC build on top of HTTP, this can be achieved easily by understanding how a gRPC call is mapped to an HTTP .. graceful restart; } Setting up Cluster Mesh This is a step-by-step guide on how to build a mesh of Kubernetes clusters by connecting them together, enabling pod-to-pod connectivity across io/v1alpha5 kind: ClusterConfig metadata: name: test-cluster region: us-west-2 nodeGroups: - name: ng-1 instanceType: m5n.xlarge desiredCapacity: 2 ssh: allow: true The nodegroup is created

nux-next.git /source/linux cd linux mkdir build make O=$PWD/build ARCH=x86_64 x86_64_defconfig make O=$PWD/build ARCH=x86_64 menuconfig make O=$PWD/build ARCH=x86_64 -j16 Kernel image Remember to: filesystem image - Enable networking - Enable the SSH daemon cd /source/linux qemu-system-x86_64 -kernel build/arch/x86/boot/bzImage \ --enable-kvm \ -nic user,hostfwd=tcp::2222-:22 \ -boot c -m 2049M -hda /s 115200 acpi=off nokaslr" \ -serial stdio -display none Start the test VM cd /source/linux gdb build/vmlinux (gdb) target remote localhost:1234 (gdb) bpf/syscall.c:4180 (gdb) bpf/syscall.c:796 (gdb)

limit the number of consumers • But adding such a feature in RabbitMQ could be a long process… Build a Limiter in BPF • Let’s use BPF to get a quick win! • Track how many “AMQP consumers” have been

3: Linux tracing utility ○ strace/ftrace ○ LTTng/USDT Option 4: eBPF ? What are we going to build? eBPF [0] % objdump --syms app|grep computeE 00000000006609a0 g F .text 000000000000004b