Skip to main content

​
Kubernetes Version

Odigos requires Kubernetes version 1.21.12 or higher.
Odigos eBPF-based data collection requires, at minimum, platforms that have underlying Linux kernel versions of 5.4.0.The required Linux capabilities depend on your kernel version:
  • Kernel 5.4 – 5.7: requires CAP_SYS_ADMIN.
  • Kernel 5.8 and later: requires CAP_BPF and CAP_SYS_PTRACE.
We recommend running on kernel 5.8 or later when possible, as the more granular capabilities (CAP_BPF and CAP_SYS_PTRACE) follow the principle of least privilege compared to CAP_SYS_ADMIN.
What to expect if some nodes don’t meet the Kernel requirement:
  • eBPF Agents: If a node’s kernel version is below 5.4.0, eBPF-based data collection will not be applied to workloads on that node. An error will appear in the UI for any source running on unsupported nodes, indicating that instrumentation was not possible.
  • Non-eBPF Agents: Non-eBPF-based agents are not affected by kernel version requirements and will run and instrument workloads on any Linux version.
This allows users to maintain observability on nodes that meet the requirements without needing to upgrade all cluster nodes immediately.

​
Kubernetes Cluster Types

​
Resource Requirements

To achieve its functionality Odigos uses a set of Deployments and DaemonSets.

​
Cluster

The following components run as Deployment and request the following resources (per pod): In addition, Odigos deploys OpenTelemetry Collector Deployment, with auto scaling (multiple replicas) and configurable resources requests and limits. The default values (unless overridden) are: Read more here.

​
Per Node

A DaemonSet running on every node in the cluster, consuming resources as outlined below: You can override these values by providing a custom configuration (read more here).

​
Network Requirements

Ensure that any network-layer components are properly configured to allow the required connectivity between Odigos components. Improper configuration may impact the correct operation of Odigos.
To ensure proper operation of Odigos components and instrumented applications, the following network connectivity must be allowed inside the Kubernetes cluster:

​
Core Network Connectivity

​
Network Layer Considerations

In some environments, the following network components may affect traffic between these services:
  • Service meshes (e.g. Istio, Linkerd, Cilium, Consul)
  • HTTP proxies or egress gateways
  • Transparent proxies (corporate or cluster-level)
  • Network security appliances (WAFs, L7 firewalls, DPI systems)
  • Kubernetes NetworkPolicies