Uninstall
This document guides you through the complete uninstallation of Alauda AI and its related components from your cluster. The uninstallation process is divided into two main parts: first, uninstalling the optional Alauda AI Model Serving and its instances, and then, uninstalling the core Alauda AI instance and Operator.
If you don't need the Serverless capability or want to use only the essential core features to save resources, you can choose to perform only the first step to remove the Alauda AI Model Serving components.
Note: Before proceeding with the uninstallation, ensure you have backed up all important data and models. The uninstallation process will permanently delete all resources and configurations associated with Alauda AI.
TOC
Uninstalling Alauda AI Model Serving Components
This section guides you on how to uninstall the components that provide Serverless capabilities.
Deleting the Alauda AI Model Serving Instance
Before deleting the Alauda AI Model Serving Instance, you must check the Serverless parameter configuration.
For versions 1.4 and later:
Ensure the BuiltIn Knative Serving field is set to Unmanaged.
For version 1.3:
Ensure the Knative Serving Mode field is set to Unmanaged.
Procedure
From the Administrator view:
- Click Marketplace / OperatorHub.
- At the top of the console, from the Cluster dropdown list, select the cluster you want to uninstall from.
- Find and select Alauda AI Model Serving.
- On the Alauda AI Model Serving page, click the All Instances tab.
- Find the instance (commonly named
default-knative-serving, or your custom instance name). - Click the
...menu on the right side of the instance, then select Delete. - In the confirmation window, confirm the deletion, then click Delete.
Verification
Verify that the instance has been deleted with the following command:
If the instance was successfully deleted, the command will return "No resources found in knative-serving namespace."
Uninstalling the Alauda AI Model Serving Operator
Procedure
From the Administrator view:
- Click Marketplace / OperatorHub.
- At the top of the console, from the Cluster dropdown list, select the cluster you want to uninstall from.
- Find and select Alauda AI Model Serving.
- On the Alauda AI Model Serving page, click Uninstall.
- In the confirmation window, check the installation location of the Alauda AI Model Serving Operator (default is kserveless-operator).
- Click the Uninstall button.
Verification
Confirm that the Alauda AI Model Serving tile's status has changed from Installed to Not Installed or has disappeared from the list.
Uninstalling Core Alauda AI Components
After completing the first section, you can proceed to uninstall the core Alauda AI components.
Deleting the Alauda AI Instance
Procedure
From the Administrator view:
- Click Marketplace / OperatorHub.
- At the top of the console, from the Cluster dropdown list, select the cluster you want to uninstall from.
- Find and select Alauda AI.
- On the Alauda AI page, click the All Instances tab.
- Find the instance named
default. - Click the
...menu on the right side of the instance, then select Delete. - In the confirmation window, confirm the deletion, then click Delete.
Verification
Verify that the instance has been deleted with the following command:
If the instance was successfully deleted, the command will return No resources found or a similar message.
Uninstalling the Alauda AI Operator
Procedure
From the Administrator view:
- Click Marketplace / OperatorHub.
- At the top of the console, from the Cluster dropdown list, select the cluster you want to uninstall from.
- Find and select Alauda AI.
- On the Alauda AI page, click Uninstall.
- In the confirmation window, check the installation location of the Alauda AI Operator (default is aml-operator).
- Click the Uninstall button.
Verification
Confirm that the Alauda AI tile's status has changed from Installed to Not Installed or has disappeared from the list.
Cleaning Up Remaining Resources
CRDs are not removed automatically when an operator is uninstalled. You can manually clean up these remaining resources, and be aware that:
Deleting a CRD will permanently delete all associated data.
The amlnamespaces.manage.aml.dev CRD, which is responsible for managing namespaces, is not included in the deletion commands below. To ensure a complete deletion of resources, you must manually remove the finalizer field after the CRD deletion operation.
It's generally recommended to keep this CRD unless you are certain you no longer need its management capabilities.