Jaeger
As part of the add-on there is Jaeger collector, which requires storage to work. As a storage backend the Jaeger add-on from VK Cloud uses Elasticsearch, which is deployed in the form of several replicas.
-
Review the system requirements of the add-on to make sure you have enough resources to install it.
Jaeger add-on system requirements depend on the selected number of Elasticsearch replicas and the cluster environment. The minimum number of replicas is two, the default is three. Their number can be changed during the standard installation or installation on dedicated worker nodes.
-
(Optional) Perform manual scaling of worker node groups or set up automatic scaling.
Several installation options are available for the add-on.
-
Install the add-on:
Management console-
Go to your VK Cloud management console.
-
Select the project where the required cluster is located.
-
Go to Kubernetes Clusters → Kubernetes Clusters.
-
Click the name of the required cluster.
-
Go to the Addons tab.
-
Click the Install button on the
jaegeradd-on card, then click Install addon. -
(Optional) Edit:
- application name;
- the name of the namespace where the add-on will be installed.
-
Edit the add-on settings code if:
- you need a non-standard number of Elasticsearch replicas;
- the master nodes and worker nodes are located in different availability zones.
-
Click the Install addon button.
The installation of the add-on in the cluster will begin. This process can take a long time.
-
-
(Optional) Connect to the Query UI.
-
(Optional) Review a how-to guide on using Jaeger with the HotROD microservice demo application. The guide demonstrates:
- How to integrate OpenTelemetry into a microservice application so that it sends the data required for query tracing to Jaeger.
- How to visualize and interpret the data collected by Jaeger using Query UI.
Editing the add-on code is applicable for standard installation and installation on dedicated worker nodes.
You can find the full add-on settings code along with the description of the fields on GitHub.
To set the required number of replicas, change the value of the field in the add-on settings code:
elasticsearch:replicas: <NUMBER_OF_REPLICAS>
Elasticsearch replicas are hosted on the worker nodes of the cluster and use persistent volumes as a storage. By default, these persistent volumes are located in the same availability zone in which the cluster's worker nodes are located. If the cluster worker nodes and persistent volumes are located in different availability zones, then replicas on these nodes will not be able to work with volumes.
To ensure that persistent volumes work with Elasticsearch replicas, set the storage class, the availability zone of which coincides with the availability zone of worker nodes:
elasticsearch:volumeClaimTemplate:accessModes:- ReadWriteOncestorageClassName: "<STORAGE_CLASS_NAME>"
Once done with editing the add-on code, continue with the installation process.