Skip to content

otel-collector

OpenTelemetry collector resources supplied directly from the deploy repo.

Deployment Scope

  • Cluster scope: global or site
  • Values keys: global.otel_collector, site.otel_collector
  • ArgoCD Application template: charts/argocd-understack/templates/application-otel-collector.yaml

How ArgoCD Builds It

  • ArgoCD renders only the sources declared directly in the Application template.
  • The current template does not read a deploy-repo values.yaml for this component.
  • The deploy repo overlay directory for this component is the only source for this Application, so kustomization.yaml and any referenced manifests are the final Application content.

How to Enable

Enable this component under the scope that matches your deployment model:

$CLUSTER_NAME/deploy.yaml
global:
  otel_collector:
    enabled: true
site:
  otel_collector:
    enabled: true

Deployment Repo Content

Use any secret delivery mechanism you prefer. The contract that matters is the final Kubernetes Secret or manifest shape described below.

Required or commonly required items:

  • kustomization.yaml: Include the collector manifests that should run in this environment.
  • Backend credential Secret: Create the Secret name referenced by your collector manifests and populate it with username and password when exporters write to an authenticated log or metrics backend.

Optional additions:

  • Node collector manifests: Add a DaemonSet, RBAC, or other collector workloads if you want node-level telemetry. The current example includes both.
  • Additional collector pipelines: Add more Deployments, ConfigMaps, or Secrets as telemetry requirements grow.