README.md

June 24, 2026 · View on GitHub

Tracing Module

License

Tracing Module provides a tracing stack for SIGHUP Distribution (SD).

If you are new to SD please refer to the official documentation on how to get started with SD.

Overview

Tracing Module uses a collection of open source tools to provide a resilient and robust tracing stack for the cluster, built around Grafana Tempo. All the components are deployed in the tracing namespace.

Packages

The following packages are included in Tracing Module:

Package	Version	Description
tempo-distributed	`2.10.5`	Distributed Tempo deployment
minio-ha	`RELEASE.2026-05-20T23-44-52Z`	Three nodes HA MinIO deployment

Click on each package to see its full documentation.

Compatibility

Kubernetes Version	Compatibility	Notes
`1.29.x`	:white_check_mark:	No known issues
`1.30.x`	:white_check_mark:	No known issues
`1.31.x`	:white_check_mark:	No known issues
`1.32.x`	:white_check_mark:	No known issues
`1.33.x`	:white_check_mark:	No known issues
`1.34.x`	:white_check_mark:	No known issues
`1.35.x`	:white_check_mark:	No known issues

Check the compatibility matrix for additional information about previous releases of the modules.

Usage

Tracing Module is part of SIGHUP Distribution (SD) and is deployed automatically by furyctl when you create or update a cluster. You don't need to download, vendor or install its packages manually.

Configuration

You configure the module under spec.distribution.modules.tracing in your furyctl.yaml. The type field selects whether the tracing stack is deployed: tempo to deploy Grafana Tempo (the default), or none to disable the module. The other fields are optional and fall back to sensible defaults.

apiVersion: kfd.sighup.io/v1alpha2
kind: KFDDistribution
spec:
  distribution:
    modules:
      tracing:
        type: tempo
        minio:
          storageSize: "20Gi"

See the configuration reference for your cluster kind for the full list of available options: EKSCluster, KFDDistribution or OnPremises.

To install SD from scratch, follow the Getting started guide.

Sending traces to Tempo

To send traces from an instrumented application to Tempo, point the application to the Distributor's service:

tempo-distributed-distributor.tracing.svc.cluster.local:4317

Note

4317 is the port for the OpenTelemetry Protocol (OTLP). The Distributor supports other protocols, but OTLP is recommended for performance reasons.

Warning

For production workloads, it is better to use something like the OpenTelemetry Collector instead of pushing traces directly to Tempo, so the application can offload traces quickly and minimize the impact on its performance.