Deleting profiler container (pod) jobs
removes all the Custom Sensitivity Profiler rules and other updates to the specified profiler.
To overcome this situation, when you decide to delete the profiler cluster, there
is a provision to retain the status of the Custom Sensitivity Profiler rules. If your
profiler cluster has rules that are not changed or updated, you can directly delete the
profiler cluster. If the rules were modified or updated, you have an option to download
the modified rules along with deletion. The modified rules consist of the suspended
System rules and the deployed Custom rules.Using the downloaded rules, you can manually
add or modify them to your newly added profiler cluster.
- When you delete the scheduled jobs, the associated Kubernetes cron job
object is deleted from the Kubernetes cluster.
- The associated data of the profilers from the Management Console
database is also deleted for the specified data lake.
-
On the search page, select the Data Lake from the list.
-
Click the Actions drop-down menu and select
Delete Cluster.
-
Click Yes to proceed.
-
If you agree, select the warning message I understand this action
cannot be undone.
-
Click Delete.
The application displays the following message.
The profiler cluster is deleted
successfully.
