Kubernetes Fury Tracing
Kubernetes Fury Tracing provides a tracing stack for the Kubernetes Fury Distribution (KFD).
If you are new to KFD please refer to the official documentation on how to get started with KFD.
Overview
Kubernetes Fury Tracing uses a collection of open source tools to provide the most resilient and robust tracing stack for the cluster.
The module right now contains only the tempo tool from grafana.
All the components are deployed in the tracing namespace in the cluster.
| Package | Version | Description |
|---|---|---|
| tempo-distributed | 2.3.1 | Distributed Tempo deployment |
| minio-ha | vRELEASE.2023-01-12T02-06-16Z | Three nodes HA MinIO deployment |
Click on each package to see its full documentation.
Compatibility
| Kubernetes Version | Compatibility | Notes |
|---|---|---|
1.26.x | ✅ | No known issues |
1.27.x | ✅ | No known issues |
Check the compatibility matrix for additional informations about previous releases of the modules.
Usage
Prerequisites
| Tool | Version | Description |
|---|---|---|
| furyctl | >=0.25.0 | The recommended tool to download and manage KFD modules and their packages. To learn more about furyctl read the official documentation. |
| kustomize | >=3.5.3 | Packages are customized using kustomize. To learn how to create your customization layer with kustomize, please refer to the repository. |
Deployment
- List the packages you want to deploy and their version in a
Furyfile.yml
bases:
- name: tracing
version: "v1.0.2"
See
furyctldocumentation for additional details aboutFuryfile.ymlformat.
-
Execute
furyctl legacy vendor -Hto download the packages -
Inspect the download packages under
./vendor/katalog/tracing. -
Define a
kustomization.yamlthat includes the./vendor/katalog/loggingdirectory as resource.
resources:
- ./vendor/katalog/logging/minio-ha
- ./vendor/katalog/logging/tempo-distributed
- To deploy the packages to your cluster, execute:
kustomize build . | kubectl apply -f -
Note: When installing the packages, you need to ensure that the Prometheus operator is also installed. Otherwise, the API server will reject all ServiceMonitor resources.