Uninstalling Alauda Distributed Tracing
You can uninstall the Alauda Distributed Tracing components from your Alauda Container Platform. This can be done through the Alauda Container Platform web console or the command line interface (CLI).
Uninstalling the Alauda Distributed Tracing involves deleting the following components:
- OpenTelemetry Collector (
otel) instance - Jaeger v2 (
jaeger) instance - Jaeger namespace
Optionally, you can also uninstall the Alauda Build of OpenTelemetry v2 Operator if it is no longer needed.
Uninstalling via the web console
Procedure
Delete the OpenTelemetry Collector instance
- In the Alauda Container Platform web console, navigate to Administrator.
- Select Marketplace > OperatorHub.
- Search for the
Alauda Build of OpenTelemetry v2. - Locate the Alauda Build of OpenTelemetry v2, and click to select it.
- Click All Instances tab.
- From the Filter by instance type dropdown, select
OpenTelemetryCollector. - Locate the
otelinstance in the Jaeger namespace (default:jaeger-system), click the "⋮" button, then click Delete in the menu. - When prompted, confirm the action by clicking Delete.
Delete the Jaeger v2 instance
In the Alauda Build of OpenTelemetry v2 view of OperatorHub:
- Click All Instances tab.
- From the Filter by instance type dropdown, select
OpenTelemetryCollector. - Locate the
jaegerinstance in the Jaeger namespace (default:jaeger-system), click the "⋮" button, then click Delete in the menu. - When prompted, confirm the action by clicking Delete.
Delete the Jaeger namespace
Delete the Jaeger namespace using the CLI:
Replace jaeger-system with the namespace you used during installation if it differs from the default.
(Optional) Uninstall the Alauda Build of OpenTelemetry v2 Operator
The Alauda Build of OpenTelemetry v2 Operator is installed cluster-wide and may be used by other components such as OpenTelemetry Collector instances in other namespaces. Before uninstalling the Operator, verify that no other OpenTelemetryCollector or Instrumentation resources depend on it.
If the Operator is no longer needed, uninstall it from the web console:
In the Alauda Build of OpenTelemetry v2 view of OperatorHub:
- Click the Uninstall button in the top-right corner.
- 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.
- Click Uninstall.
For more details, see Uninstalling Alauda Build of OpenTelemetry v2.
Uninstalling via the CLI
Procedure
Set environment variables
Set the environment variables to match the values used during installation:
If you customized these values during installation, replace them with your actual values.
Delete the OpenTelemetry Collector instance
Delete the otel OpenTelemetry Collector instance:
Example output
Delete the Jaeger v2 instance
Delete the Jaeger OpenTelemetry Collector instance:
Example output
Delete the Jaeger namespace
Example output
(Optional) Uninstall the Alauda Build of OpenTelemetry v2 Operator
The Alauda Build of OpenTelemetry v2 Operator is installed cluster-wide and may be used by other components such as OpenTelemetry Collector instances in other namespaces. Before uninstalling the Operator, verify that no other OpenTelemetryCollector or Instrumentation resources depend on it.
If the Operator is no longer needed, delete the opentelemetry-operator2 subscription:
Example output
For more details, see Uninstalling Alauda Build of OpenTelemetry v2.