Uninstall Infrastructure Observability
Infrastructure Observability (IO) is deployed as four Helm releases in the virtana-io namespace. Each release manages a distinct layer of the IO stack, from the integration connectors that pull data from external platforms down to the underlying database and Kubernetes infrastructure. Removal follows a top-down order to avoid dependency errors during cleanup.
Caution
If Infrastructure Observability is integrated with GlobalView, remove the integration configuration in GlobalView before uninstalling IO. Removing IO while GlobalView is still actively communicating with it may cause GlobalView to log errors or enter a degraded state.
Also, ensure that any AIFO Collector deployments in your environment have been removed before proceeding, as they send data to the IO backend.
The following table shows the four Helm releases in the virtana-io namespace:
Helm release | Layer | Description |
|---|---|---|
virtana-io-integrations | Integrations | Connectors for third-party platforms, such as VMware, AWS, or Azure. Remove first as it depends on core services. |
virtana-io-core | Core services | Central processing engine, API, and orchestration layer. Depends on the database and infrastructure layers. |
virtana-io-dbs | Databases | Persistent storage layer including time-series and relational databases for IO metrics and configuration. |
virtana-io-infra | Infrastructure | Base Kubernetes infrastructure including operators, CRDs, and cluster-level resources. Remove last. |
Uninstallation steps
Perform the steps:
Uninstall virtana-io-integrations.
The integrations package contains the connectors that collect telemetry from external infrastructure sources such as VMware vCenter, cloud providers, and hardware platforms. Removing it stops all data collection from those sources. This release must be removed before the core package because it registers consumers and job queues that the core services manage.
Run the following command to remove integration connectors for third-party platforms.
helm uninstall virtana-io-integrations -n virtana-io
Uninstall virtana-io-core.
The core package contains the central IO services, including the API server, the data processing pipeline, and the orchestration engine. It depends on the database layer below it. Removing it after the integrations package ensures that no active integrations are trying to write data when the processing layer is taken down.
Run the following command to remove the IO processing engine and API layer.
helm uninstall virtana-io-core -n virtana-io
Uninstall virtana-io-dbs.
The databases package installs and manages the time-series and relational databases used by IO to store collected metrics, configuration, and historical data. Removing it deletes the database workloads but not necessarily the underlying PVCs. If you want to retain IO data for a future reinstallation, back up or detach the PVCs before running this command.
Run the following command to remove the database layer. It results in loss of IO metric and configuration data.
helm uninstall virtana-io-dbs -n virtana-io
To remove any remaining PVCs after this step, run:
kubectl delete pvc -n virtana-io --all
Uninstall virtana-io-infra.
The infrastructure package contains the base Kubernetes resources that all other IO packages depend on, including any operators and cluster-level configurations. This must be removed last. Removing it while other IO packages are still installed would leave those packages in a broken state with missing dependencies.
Run the following command to remove base infrastructure, operators, and cluster-level resources.
helm uninstall virtana-io-infra -n virtana-io
After all four charts have been uninstalled, verify that no IO resources remain in the namespace:
kubectl get all -n virtana-io
If you want a complete cleanup, delete the namespace once you have confirmed all workloads have terminated:
kubectl delete namespace virtana-io