This talk aims to be a deep dive into how some of the OpenShift networking
is implemented under the hood. Since OpenShift 4.12, the default certified
Container Network Interface (CNI) has been ovn-kubernetes (OVN-K8s). OVN-K8s
provides a Kubernetes networking solution by using the open source
Open Virtual Networking (OVN) and Open vSwitch (OVS) projects at its core.

While we plan to briefly describe how OVN-K8s configures the OVN logical
network topology, this talk will not focus on that. Instead, the goal of
this talk is to describe how individual packets are processed in the kernel
OVS datapath and to provide a bottom-up way of mapping the processing
steps to the upper layers, in this order:
- OVS kernel datapath flows
- OVS OpenFlow rules
- OVN logical flows
- OVN logical network constructs (e.g., switches, routers)
- Kubernetes objects

RISC-V is an open standard instruction set architecture that has potential to be widely used as an alternative to existing ARM and x86 solutions. For the software developers it's beneficial to keep up with this technology and test early. At the moment it might be challenging to get real RISC-V hardware, however there is an alternative by using emulators such as QEMU. This short talk presents the journey and challenges we faced when testing our application on RISC-V Fedora in a VM and in a podman container.