cmcornejocrespo/distributed-tracing

Ansible automation to deploy the OpenShift Distributed stack and grafana configured to use prometheus thanos query endpoint as datasource

Kustomization for Red Hat OpenShift distributed tracing

• You can install Red Hat OpenShift distributed tracing as part of Red Hat OpenShift Service Mesh. Distributed tracing is included by default in the Service Mesh installation. To install Red Hat OpenShift distributed tracing as part of a service mesh, follow the Red Hat Service Mesh Installation instructions. You must install Red Hat OpenShift distributed tracing in the same namespace as your service mesh, that is, the ServiceMeshControlPlane and the Red Hat OpenShift distributed tracing resources must be in the same namespace.

• If you do not want to install a service mesh, you can use the Red Hat OpenShift distributed tracing Operators to install distributed tracing by itself. To install Red Hat OpenShift distributed tracing without a service mesh, use the following instructions.

Note	We’ll install Red Hat OpenShift distributed tracing without a service mesh. We’ll not install the collector.

Prerequisites

Before you can install Red Hat OpenShift distributed tracing, ensure that you meet the prerequisites:

• OCP cluster running

• oc installed

• Logged in a cluster-admin like role

• Ansible

• Kustomize (only if deploy manually)

Deploying the stack

$ ansible-playbook -i inventory/localhost.yml deploy_stack.yaml

Delete the stack

$ ansible-playbook -i inventory/localhost.yml delete_stack.yaml

Deploy components manually

Installing the OpenShift Elasticsearch Operator

$ oc apply -k kustomization/elasticsearch/base

Installing the Red Hat OpenShift distributed tracing platform Operator

$ oc apply -k kustomization/distributed-tracing-platform/base

Installing the Red Hat OpenShift distributed tracing data collection Operator

$ oc apply -k kustomization/distributed-tracing-collector/base

Deploy Jaeger stack

$ oc apply -k kustomization/distributed-tracing-platform/config