---
title: "eBPF"
description: "1 posts about eBPF, summarised, each linking to the original."
---

# eBPF
> 1 posts about eBPF, summarised, each linking to the original.

## Articles

### [Red Hat OpenShift networking: Default OVN-Kubernetes vs. Cilium operator](https://yomu.fyi/post/red-hat-openshift-networking-default-ovn-kubernetes-vs-cilium-operator.md)
- Company: [Red Hat](https://yomu.fyi/company/red-hat.md)
- Author: Amjed Jabari (AJ), Wuxin Zeng, Rodrigo Gonzalez
- Published: Sep 18, 2026
- Type: Explainer

The article compares Red Hat OpenShift’s default OVN-Kubernetes CNI with the Cilium operator for teams managing microservices, AI workloads, and declarative multi-cluster infrastructure with Cluster API (CAPI). It describes OVN-Kubernetes as natively managed by the OpenShift Cluster Network Operator, with Open vSwitch foundations, hardware offloading, Multus and OpenShift Virtualization compatibility, and OVN Interconnect for large-scale deployments. Cilium uses kernel-level eBPF programs and offers identity-based policies, sidecarless service mesh capabilities, and Hubble Layer 7 observability, while CAPI manifests and MachineSets support declarative worker-node provisioning. The source recommends Cilium for new clusters when eBPF capabilities and CAPI integration justify added operational complexity, while positioning OVN-Kubernetes as the simpler choice for integrated lifecycle management and hardware acceleration.