Skip to content

Latest commit

 

History

History

pattern-3-kubernetes

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
README.adoc
README.adoc
 
 
agent-sidecar.yaml
agent-sidecar.yaml
 
 
collector.yaml
collector.yaml
 
 
daemonset.png
daemonset.png
 
 
sidecar.png
sidecar.png
 
 

README.adoc

Pattern #3 - Kubernetes

This pattern can be used when deploying the OpenTelemetry Collector on Kubernetes. It comes with the following variants:

  • Agent as sidecar, where a container is added to the workload pod with the OpenTelemetry Collector. This instance is then configured to send data to an external collector, potentially in a different namespace or cluster.

  • Agent as DaemonSet, where a DaemonSet is used instead, so that we have one agent pod per Kubernetes node. Note that this is not recommended for multitenant deployments, as the agent will receive data from all of the pods in the node, irrespective of namespace.

sidecar
Figure 1. Kubernetes pattern, with sidecars.
daemonset
Figure 2. Kubernetes pattern, with daemon sets.

Running

The blog post "Deploying the OpenTelemetry Collector on Kubernetes" shows in details how to achieve both scenarios. The OpenTelemetry Operator can also be used for that, including the ability to inject sidecars into the workload pods automatically.