Edit

OpenTelemetry Kube Stack

Purpose: For platform engineers, operators, SREs, documents the OpenTelemetry Kube Stack service in openCenter-gitops-base.

opentelemetry-kube-stack provides collectors, operator support, and telemetry pipelines for traces and logs. It is the primary ingestion and processing layer for the observability stack in this repository.

What This Repo Deploys

  • HelmRelease/opentelemetry-kube-stack

  • Base values from the service helm-values/ directory

  • Optional opentelemetry-kube-stack-values-override

When to Use It

  • You want a standard OTLP-based telemetry pipeline.

  • You want Kubernetes-native collector deployment through the OpenTelemetry operator.

  • You want logs and traces routed into Loki, Tempo, or other OTLP-capable backends.

Key Integration Points

  • Tempo is the main tracing backend.

  • Loki is the main logging backend.

  • Grafana and kube-prometheus-stack are typically used for visualization and alerting around collector health.

Example

apiVersion: opentelemetry.io/v1beta1
kind: OpenTelemetryCollector
metadata:
  name: cluster
spec:
  mode: daemonset

Configuration Surfaces

  • Service path: applications/base/services/observability/opentelemetry-kube-stack/

  • Namespace: observability

  • Flux object: HelmRelease/opentelemetry-kube-stack

  • Base values Secret: opentelemetry-kube-stack-values-base

  • Override values Secret: opentelemetry-kube-stack-values-override

  • ../../operations/services/opentelemetry-kube-stack.md[OpenTelemetry Kube Stack Configuration Guide]

  • ../../concepts/opentelemetry-architecture.md[OpenTelemetry Notes]

Upstream References