Day 1: Understand and install Cilium, then observe network flows
5 topics, Tap to openTap to close
10:00–11:00Understand Cilium's Role in Kubernetes Networking
Cilium combines CNI responsibilities, the eBPF datapath, and network observability in one Kubernetes model. Participants relate the Cilium Agent, Operator, and Hubble to their technical roles and examine how a workload appears across their states in the lab. They compare which perspective describes configuration, traffic, or observability data and where initial diagnostic questions are most useful.
11:00–12:00Choose Installation Values and Install Cilium
A Cilium installation depends on its prerequisites and selected operating modes. Participants check kernel capabilities, CNI state, routing, and IPAM constraints, derive suitable installation values, and install Cilium with the CLI or Helm in the provided cluster. In the DevNinjas Dojo, our cloud learning environment, they then consider which states are relevant to an initial assessment of the installation.
13:00–14:00Trace Pod and Service Paths
After installation, a green status indicator is not yet a network model. Participants trace a pod-to-pod request and a Service request through endpoints, security identities, routing, and load balancing. They form a hypothesis about source, destination, and path and compare it with the observable Cilium and Kubernetes state.
14:00–15:00Inspect Network Flows with Hubble
When dependencies appear only as IP addresses, Hubble flows help relate them to the application. The group enables Hubble Relay, uses the Hubble CLI as its primary tool, and optionally opens the open-source UI as a Service map. Participants generate test traffic, filter flows by namespace, pod, direction, and verdict, and compare what the different views reveal about the datapath.
15:00–16:00Assess Installation with Cilium Connectivity Tests
Connectivity Tests cover more network paths than isolated ping requests, but their interpretation still needs context. Participants run the Cilium Connectivity Test, distinguish test failures from lab environment problems, and inspect selected paths with Hubble. They discuss which observations point to the installation, the test setup, or another deviation.

