Skip to content

Kubernetes · Editable reference architecture

Cilium networking architecture

An editable cilium networking architecture reference showing Pod → eBPF datapath → Service backend. Policy and observability depend on deployment configuration.

Open & Edit in DrawArc (Free, No Login Required)

Your changes stay in a separate draft on this browser. Download an editable project to keep a portable copy.

LinkedInTelegramReddit

Cilium networking architecture diagram: Pod, eBPF datapath, Service backend, Cilium agent and their connections
Cilium networking architecture — follow the component relationships, then open the editor to adapt the design. View diagram image.

7 components · 5 connections · Open the editor to zoom, move nodes and edit source.

Architectural overview

Cilium networking architecture addresses the responsibilities and boundaries shown in this reference rather than prescribing an entire production deployment. The primary flow starts at Pod and reaches Service backend through eBPF datapath. Use this view to explain which component initiates work, which component owns a decision, and where a dependency can affect the caller. Policy and observability depend on deployment configuration.

The diagram contains 7 distinct components and 5 directed relationships. A separate path connects Cilium agent → eBPF datapath. A separate path connects Operator → Cilium agent. A separate path connects Hubble → Flow visibility. These arrows describe logical interactions; they do not establish authentication, network access, atomic transactions or delivery guarantees. Label the actual protocol, payload contract and owner when adapting the drawing to your system. Keep synchronous and asynchronous boundaries explicit so that a reviewer can identify where a request ends and a later operation begins.

Before implementing this architecture, define expected load, data classification, latency budgets and recovery objectives. Give Pod a bounded dependency timeout and a documented failure response. Assign ownership to any state or external service added during implementation. Validate the decision above against your workload instead of treating the presence of a component as proof of reliability. Open the editable canvas, replace generic labels with real deployment units, and document the decisions that differ from this reference.

The real-world problem

Design or explain cilium networking architecture with explicit ownership and dependency paths. Policy and observability depend on deployment configuration.

Data flow

Connections from this diagram. Branches and control signals are not a single chronological sequence.

  • Pod → eBPF datapath. Define the interaction contract and trace the resulting response or state change.
  • eBPF datapath → Service backend. Define the interaction contract and trace the resulting response or state change.
  • Cilium agent → eBPF datapath. Define the interaction contract and trace the resulting response or state change.
  • Operator → Cilium agent. Define the interaction contract and trace the resulting response or state change.
  • Hubble → Flow visibility. Define the interaction contract and trace the resulting response or state change.

Security boundaries

  • Authenticate callers at the boundary before eBPF datapath accepts protected work; authorize the specific operation rather than trusting network placement.
  • Use separate service identities and least-privilege permissions for eBPF datapath, Service backend, Cilium agent. Encrypt sensitive traffic, protect credentials and avoid placing confidential payloads in logs.
  • Validate untrusted inputs and restrict administrative/configuration endpoints separately from the main flow.

Failure handling

Pod is unavailable or slow

Response: Apply bounded timeouts and controlled backoff only where retrying is safe. Return an explicit failure or durable acceptance; do not report success before required work is committed.

Verify: Interrupt Pod in an isolated test and measure errors, recovery and any repeated side effects.

A dependency repeats or drops a request

Response: Use operation identifiers and explicit acknowledgement/reconciliation where needed. Verify idempotency before enabling retries.

Verify: Exercise the failure path with representative records and verify both the visible response and the resulting state.

An invalid or incompatible input reaches eBPF datapath

Response: Validate the input contract before effects are committed. Preserve rejected input identifiers without exposing secrets, and document a safe replay or correction procedure.

Verify: Send malformed and older-version inputs through Pod and verify rejection, observability and unchanged valid state.

Trade-offs and alternatives

Policy and observability depend on deployment configuration.

Benefit
Makes the ownership and interaction boundaries visible for a focused design review.
Cost
The 7 illustrated components still require contracts, monitoring and operational ownership; extra boundaries can add latency and failure modes.
Alternative
Use a simpler deployment when it meets the same requirements, or split a boundary only after measuring a specific need.

Logical boundaries versus deployment units in Cilium networking architecture

Benefit
Keeps the responsibilities of Pod, eBPF datapath, Service backend visible without requiring a separate server for each box.
Cost
A logical view does not establish isolation, independent scaling or high availability; those require a separate deployment design and operational tests.
Alternative
Co-locate components in a simpler deployment first when ownership and workload requirements permit it.

When to use this architecture

  • Explain cilium networking architecture to engineers or stakeholders using a concrete visual flow.
  • Review this decision before deployment: Policy and observability depend on deployment configuration.
  • Adapt a starting diagram for your own requirements, then record and validate every changed boundary.

Key components

Pod
Pod participates in cilium networking architecture. Pod → eBPF datapath. Define its contract, owner and access permissions in your implementation.
eBPF datapath
eBPF datapath participates in cilium networking architecture. Pod → eBPF datapath; eBPF datapath → Service backend; Cilium agent → eBPF datapath. Define its contract, owner and access permissions in your implementation.
Service backend
Service backend participates in cilium networking architecture. eBPF datapath → Service backend. Define its contract, owner and access permissions in your implementation.
Cilium agent
Cilium agent participates in cilium networking architecture. Cilium agent → eBPF datapath; Operator → Cilium agent. Define its contract, owner and access permissions in your implementation.
Operator
Operator participates in cilium networking architecture. Operator → Cilium agent. Define its contract, owner and access permissions in your implementation.
Hubble
Hubble participates in cilium networking architecture. Hubble → Flow visibility. Define its contract, owner and access permissions in your implementation.
Flow visibility
Flow visibility participates in cilium networking architecture. Hubble → Flow visibility. Define its contract, owner and access permissions in your implementation.

Questions about this template

What does this cilium networking architecture diagram show?

It shows 7 components with the core flow Pod → eBPF datapath → Service backend. Policy and observability depend on deployment configuration.

Can I edit this diagram without signing in?

Yes. Open the template in the browser-local canvas to change nodes, connections and source. AI generation and cloud account storage require sign-in.

Is this a complete production implementation?

No. It is an editable reference. Validate the security controls, dependency behavior, capacity and recovery plan against your own requirements before implementation.

Validate your implementation

Use the relevant platform documentation to verify service limits, supported features and configuration. This diagram is an original reference rather than a reproduction of a provider deployment.