# Install Jaeger

> [HTML Version](installation-jaeger.html)

Jaeger is software that is used to trace and troubleshoot issues in interconnected software components, known as microservices. Multiple microservices interact with each other to perform a single software function.

Developers use Jaeger to visualize the chain of events when microservices interact to isolate a problem when something goes wrong. This is also referred to as Jaeger tracing because it tracks or traces the path of a request through a series of interactions between microservices.

You can also use the [Tempo](install-tempo.md) tool to work with traces.

Jaeger installation consists of three steps:

1. [Download the Helm chart and configuration file](#download-helm-chart-and-config-file).

2. [Fill out the configuration file](#fill-config-file).

3. [Install the Jaeger chart using helm in the Kubernetes cluster](#install-jaeger-chart).

## Step 1: Download the Helm chart and configuration file

For installation via the internet, obtain the configuration file \[OBJECT\] by executing the command:

````
helm repo add brix365 https://charts.brix365.com  
helm repo update  
helm show values brix365/jaeger > values-jaeger.yaml

````
Getting the configuration file for installation in a closed-loop environment without internet access

1. On a computer with internet access, download the archive of the latest version of the Jaeger chart from the BRIX repository by executing the following command:

````
helm repo add brix365 https://charts.brix365.com  
helm repo update  
helm pull brix365/jaeger

2. ````
Copy the obtained chart archive \[OBJECT\] to the server where the installation will be performed.

3. Unpack this chart and copy the default configuration file \[OBJECT\] to \[OBJECT\]:

````
tar -xf jaeger-X.Y.Z.tgz  
cp jaeger/values.yaml values-jaeger.yaml
````

## ````
Step 2: Fill out the configuration file

Fill out the configuration file \[OBJECT\] for Jaeger installation.

````
\# Jaeger settings  
jaeger:  
  resources:  
    requests:  
      cpu: 100m  
      memory: 256Mi  
    limits:  
      cpu: 500m  
      memory: 8Gi  
  tolerations:  
    - effect: NoSchedule  
      key: dedicated  
      operator: Equal  
      value: monitoring  
  service:  
    name: jaeger-nodeport  
    # Port for accessing Jaeger when ingress is disabled  
    nodePort: 32121  
  ingress:  
    # enable host in ingress  
    enabled: false  
    className: ""  
    annotations:  
      kubernetes.io/ingress.class: nginx  
    # annotations for cert-manager operation  
    # certmanager.io/cluster-issuer: letsencrypt  
    hosts:  
      # domain (FQDN) through which the system will be accessible  
      - host: example.ru  
        paths:  
          - path: /  
            pathType: ImplementationSpecific  
     # enable encryption, when using cert-manager, specify the used secretName letsencrypt  
\#    tls:  
\#      - secretName: example-ru-cert  
\#        hosts:  
\#          - example.ru  
  # enable creation of a secret with custom certificates  
  #  indicate the path to the certificate in the lines key: and cert:  
  secret:  
    enabled: false  
    key: "files/my\_cert.key"  
    cert: "files/my\_cert.crt"  
  # To prevent the problem of insufficient memory, specify an integer value for tracing  
  memory\_max\_traces: 50000  
  # number of replicas for high availability  
  replicaCount: 1  
...

````
Filling out the parameters for connection to a private registry for installation in a closed loop without internet access

  
To connect to a private registry, you need to:

1. Download the BRIX images and upload them to the local image registry. For more details, see [Download BRIX images](downloadin-images-elma365.md).

2. Set the address and path for the parameter \[OBJECT\].

3. Indicate the name of the secret with access rights to the private registry in the parameter \[OBJECT\]. The secret must be created manually and encrypted in Base64.

````
\# Jaeger settings  
jaeger:  
...  
  # connection parameters to a private registry  
  image:  
    # address and path for the private registry  
    repository: registry.example.com/jaeger  
    tag: "1.47"  
  # the secret with access rights to the private registry must be created manually, encrypted in Base64  
  pullSecrets:  
    - myRegistryKeySecretName

````
Where the repository** **format is:

- Addres is \[OBJECT\].

- Path is \[OBJECT\].

## Step 3: Install the Jaeger chart using Helm in the Kubernetes cluster

Install the Jaeger chart in \[OBJECT\].

For installation via the internet, execute the command:

````
helm upgrade --install jaeger brix365/jaeger -f values-jaeger.yaml -n monitoring

````
For offline installation without internet access, navigate to the directory with the downloaded chart and execute the command:

````
helm upgrade --install jaeger ./jaeger -f values-jaeger.yaml -n monitoring

## ````
Delete the Jaeger chart using Helm in the Kubernetes cluster

To delete the jaeger chart in \[OBJECT\], execute the command:

````
helm uninstall jaeger -n monitoring
````