Skip to main content

​
Kubernetes Version

Odigos requires Kubernetes version 1.21.12 or higher.

​
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):
Component NameMemory RequestMemory LimitCPU RequestCPU Limit
odigos-autoscaler64Mi512Mi10m500m
odigos-instrumentor (2 replicas)64Mi512Mi10m500m
odigos-scheduler64Mi512Mi10m500m
odigos-ui64Mi512Mi10m500m
In addition, Odigos deploys OpenTelemetry Collector Deployment, with auto scaling (multiple replicas) and configurable resources requests and limits. The default values (unless overridden) are:
Component NameMemory RequestMemory LimitCPU RequestCPU Limit
odigos-gateway600Mi600Mi1000m1000m
Read more here.

​
Per Node

A DaemonSet running on every node in the cluster, consuming resources as outlined below:
Component NameMemory RequestMemory LimitCPU RequestCPU Limit
odiglet500Mi500Mi500m500m
data-collection250Mi500Mi250m500m
deviceplugin200Mi300Mi40m100m
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

SourceDestination ServicePortsPurpose
Instrumented Application Podsodiglet-local4320Retrieve instrumentation configuration from Odiglet
Instrumented Application Podsodigos-data-collection-local-traffic4317 (gRPC), 4318 (HTTP)Export application telemetry data (OTLP protocol)
Odiglet Podsodigos-data-collection-local-traffic4318Export eBPF-collected telemetry data

​
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