Delete Connector Application from Privacera Portal¶
This document outlines the complete steps required to delete a PolicySync Connector application from the Privacera Self-Managed Portal. It also covers ths necessary steps to manually delete the corresponding Kubernetes pod from the Privacera Manager (PM) host.
This is supported only from Privacera Release Version 9.0.22.1 for the connectors listed below.
Connector Name | Supported from Privacera Release Version |
---|---|
9.0.22.1 |
Use Case¶
Delete a Connector application from Privacera Portal and ensure that its associated Kubernetes pod is properly cleaned up after removal.
Steps to Delete Connector Application from Portal¶
-
Navigate to Settings → Applications in the Self-Managed Portal.
-
Locate the application you want to delete in the list of configured applications.
-
Click the Delete icon next to the application name.
-
In the confirmation window:
- Type
delete
to confirm the action. - Click the Delete button to proceed.
- Type
Note: Deleting the application from the portal does NOT automatically delete the running Kubernetes pod. The following additional manual steps are required to remove the running pod from the cluster:
Steps to Delete the Running Connector Pod¶
After deleting the application from the portal, follow the steps below to manually clean up the running pod.
-
Run the command to list all installed Helm charts in the target namespace and identify the connector chart name, which will be used in the next step.
Bash -
Use the
helm uninstall
command to remove the connector deployment from the desired namespace.
Example:helm uninstall bigquery-dev -n dev-namespace
Bash -
After uninstalling the deployment, clean up the connector configuration and generated files to complete the connector removal.
-
Delete the connector configuration directory related to the connector type and environment.
Example:rm -rf config/custom-vars/connectors/bigquery/dev
-
Delete the generated Helm chart output directory corresponding to the connector type and environment.
Example:
rm -rf output/kubernetes/helm/connector/bigquery/dev
-
Important Notes¶
- Deleting the application from the portal does not automatically remove the running Kubernetes pod.
- The pod will continue to operate using the last configuration set before the application was deleted.
- Manual uninstallation and configuration cleanup are required to fully remove the connector.
- Prev Connector Guide