eBPF allows rewriting of the kernel, changing default behaviours to create new functionality or understand what is occurring. On a bare metal server hardware devices are were they're expected, system libraries live in default locations. Introducing Kubernetes and you introduce numerous network adapters inside pods, libraries live inside of container images.. suddenly your simple eBPF program needs to become a lot more complicated. This session will introduce eBPF and Kubernetes, and how to reconcile where your eBPF program should attach and how to understand this cloud native architecture!