#Uninstalling Alauda Distributed Tracing

#Delete the OpenTelemetry Collector instance

1. In the Alauda Container Platform web console, navigate to Administrator.
2. Select Marketplace > OperatorHub.
3. Search for the Alauda Build of OpenTelemetry v2.
4. Locate the Alauda Build of OpenTelemetry v2, and click to select it.
5. Click All Instances tab.
6. From the Filter by instance type dropdown, select OpenTelemetryCollector.
7. Locate the otel instance in the Jaeger namespace (default: jaeger-system), click the "⋮" button, then click Delete in the menu.
8. When prompted, confirm the action by clicking Delete.

#Delete the Jaeger v2 instance

In the Alauda Build of OpenTelemetry v2 view of OperatorHub:

1. Click All Instances tab.
2. From the Filter by instance type dropdown, select OpenTelemetryCollector.
3. Locate the jaeger instance in the Jaeger namespace (default: jaeger-system), click the "⋮" button, then click Delete in the menu.
4. When prompted, confirm the action by clicking Delete.

#Delete the Jaeger namespace

Delete the Jaeger namespace using the CLI:

kubectl delete namespace jaeger-system

#(Optional) Uninstall the Alauda Build of OpenTelemetry v2 Operator

If the Operator is no longer needed, uninstall it from the web console:

In the Alauda Build of OpenTelemetry v2 view of OperatorHub:

1. Click the Uninstall button in the top-right corner.
2. In the confirmation prompt, read the uninstall notice: Removing the operator will not remove any of its custom resource definitions or managed resources. If you have created a resource instance, you need to delete it manually.
3. Click Uninstall.

For more details, see Uninstalling Alauda Build of OpenTelemetry v2.

#(Optional) Uninstall the Alauda Build of Jaeger v2 Cluster Plugin

1. In the platform management view, navigate to Administrator > Marketplace > Cluster Plugins.
2. Select the cluster where the tracing components were deployed.
3. Find Alauda Build of Jaeger v2 and click Uninstall.
4. When prompted, confirm the action.

#Set environment variables

Set the environment variables to match the values used during installation:

export JAEGER_NS="jaeger-system"
export JAEGER_INSTANCE_NAME="jaeger"

#Delete the OpenTelemetry Collector instance

Delete the otel OpenTelemetry Collector instance:

kubectl delete opentelemetrycollector otel -n ${JAEGER_NS}

Example output

opentelemetrycollector.opentelemetry.io "otel" deleted

#Delete the Jaeger v2 instance

Delete the Jaeger OpenTelemetry Collector instance:

kubectl delete opentelemetrycollector ${JAEGER_INSTANCE_NAME} -n ${JAEGER_NS}

Example output

opentelemetrycollector.opentelemetry.io "jaeger" deleted

#Delete the Jaeger namespace

kubectl delete namespace ${JAEGER_NS}

Example output

namespace "jaeger-system" deleted

#(Optional) Uninstall the Alauda Build of OpenTelemetry v2 Operator

If the Operator is no longer needed, delete the opentelemetry-operator2 subscription:

kubectl delete subscription opentelemetry-operator2 -n opentelemetry-operator2

Example output

subscription.operators.coreos.com "opentelemetry-operator2" deleted

For more details, see Uninstalling Alauda Build of OpenTelemetry v2.

#(Optional) Uninstall the Alauda Build of Jaeger v2 Cluster Plugin

Cluster plugins are uninstalled by deleting their ModuleInfo resource in the global cluster, regardless of which cluster the plugin targets.

1. Run the following command in the global cluster to list the installed plugin. The CLUSTER column shows which cluster each entry targets:

   kubectl get moduleinfo -l cpaas.io/module-name=jaeger-cluster-plugin

2. Delete the ModuleInfo of the target cluster in the global cluster. Replace <target-cluster> with the name of the cluster where the tracing components were deployed:

   kubectl delete moduleinfo -l cpaas.io/module-name=jaeger-cluster-plugin,cpaas.io/cluster-name=<target-cluster>

   Example output

   moduleinfo.cluster.alauda.io "<moduleinfo-name>" deleted
   NOTE

   Select the resource by label rather than by name: the platform renames the ModuleInfo after installation, so its name no longer matches the one used during installation.

3. Verify that the ConfigMap created by the plugin has been removed (run against the target cluster):

   kubectl get configmap jaeger-cluster-plugin-manifest -n cpaas-system

   Example output

   Error from server (NotFound): configmaps "jaeger-cluster-plugin-manifest" not found