Debugging the BPF Virtual Machine Lorenzo Fontana October 28, 2020 ● Debugging is useful to understand how things work ● Sometimes, eBPF programs can’t even load ● I couldn’t find good resources on this this, so, here I am ● I break lots of eBPF programs ● The BPF Virtual machine is not easy to understand Why ? The BPF subsystem lives in the kernel AND The kernel can be debugged using gdb The

with ARM support planned [https://github.com/cilium/cilium/issues/9898] for a future release. Install a Master Node The first step is to install a K3s master node making sure to disable support for the the same cluster, there should be no issue as both version are mutually compatible in order to support gradual migration [https://helm.sh/docs/topics/v2_v3_migration/]. Cilium chart is targeting Helm the same cluster, there should be no issue as both version are mutually compatible in order to support gradual migration [https://helm.sh/docs/topics/v2_v3_migration/]. Cilium chart is targeting Helm

Kubernetes Integration Multi-Cluster (Cluster Mesh) Getting Help FAQ Slack GitHub Training Enterprise support Security Bugs Operations System Requirements Summary Linux Distribution Compatibility & Considerations Container Images Developer images Official release images Experimental Docker BuildKit and Buildx support Official Cilium repositories Update cilium-builder and cilium-runtime images Nightly Docker image Cluster Mesh Setting up Cluster Mesh Load-balancing & Service Discovery Network Policy Setting up Support for External Workloads (beta) Operations Running Prometheus & Grafana Istio Getting Started Using

Mesh) Getting Help FAQ Slack GitHub Training Enterprise support Security Bugs Operations System Requirements Summary Architecture Support Linux Distribution Compatibility & Considerations Linux Kernel Container Images Developer images Official release images Experimental Docker BuildKit and Buildx support Official Cilium repositories Update cilium-builder and cilium-runtime images Nightly Docker image Cluster Mesh Setting up Cluster Mesh Load-balancing & Service Discovery Network Policy Setting up Support for External Workloads (beta) Operations Running Prometheus & Grafana Istio Getting Started Using

Kubernetes Integration Multi-Cluster (Cluster Mesh) Getting Help FAQ Slack GitHub Training Enterprise support Security Bugs Operations System Requirements Summary Linux Distribution Compatibility Matrix Linux environment Self-Managed Kubernetes Managed Kubernetes Installer Integrations CNI Chaining Setting up Support for External Workloads (beta) Network Policy Security Tutorials Identity-Aware and HTTP-Aware Policy with ARM support planned [https://github.com/cilium/cilium/issues/9898] for a future release. Install a Master Node The first step is to install a K3s master node making sure to disable support for the

documentation [https://kubernetes.io/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/#support-hostport]. Note Before using HostPort, read the Kubernetes Configuration Best Practices [https://kubernetes policies. It is a detailed walk-through of getting a single-node Cilium environment running on your machine. It is designed to take 15-30 minutes. If you haven’t read the Introduction to Cilium yet, we’d policies. It is a detailed walk-through of getting a single-node Cilium environment running on your machine. It is designed to take 15-30 minutes. If you haven’t read the Introduction to Cilium yet, we’d

with ARM support planned [https://github.com/cilium/cilium/issues/9898] for a future release. Install a Master Node The first step is to install a K3s master node making sure to disable support for the in the same cluster, there should be no issue as both version are mutually compatible in order to support gradual migration [https://helm.sh/docs/topics/v2_v3_migration/]. Cilium chart is targeting Helm the same cluster, there should be no issue as both version are mutually compatible in order to support gradual migration [https://helm.sh/docs/topics/v2_v3_migration/]. Cilium chart is targeting Helm

policies. It is a detailed walk-through of ge�ng a single-node Cilium environment running on your machine. It is designed to take 15-30 minutes. If you haven’t read the Introduc�on to Cilium yet, we’d encourage policies. It is a detailed walk-through of ge�ng a single-node Cilium environment running on your machine. It is designed to take 15-30 minutes. If you haven’t read the Introduc�on to Cilium yet, we’d encourage policies. It is a detailed walk-through of ge�ng a single-node Cilium environment running on your machine. It is designed to take 15-30 minutes. If you haven’t read the Introduc�on to Cilium yet, we’d encourage

The Just-in-Time (JIT) compilation step translates the generic bytecode of the program into the machine-specific instruction set to optimize execution speed. This makes eBPF programs run as efficiently

original packets • `tc` can actually control packets! And use BPF! • Let’s add support for it in RedBPF `tc` Support in RedBPF • BPF programs are all the “same” • “Type” really depends on the input still a worthy tradeoff, especially in preventing misuse More on RedBPF • Plan to make RedBPF support more (all) program types - make it a generic compiler (BCC) • Add utility functions to help dealing