Uninstalling the Agent

The following procedure removes Protegrity Agent 1.2.0 (Helm chart 2.0.0) from supported AWS and Azure PPC environments. If custom resource names were used during installation, substitute the default names in the commands accordingly.

Before beginning the uninstallation process, verify that the correct Kubernetes context is selected and back up any required data, credentials, or configuration information stored outside the Agent volumes. The uninstallation process may remove resources such as the backup Persistent Volume Claim (PVC) and the database Secret created through External Secrets.

To uninstall Agent v1.2.0, perform the following steps:

1. Remove the Agent product registration before proceeding with the uninstallation. Ensure that the platform controllers remain operational throughout the process to support the successful removal of Agent resources. Run the following command.

   kubectl delete productconfigurations.pty.com proagent \
   -n pty-protegrity-agent --ignore-not-found --wait=true --timeout=120s
   

2. To uninstall the Helm release and wait for the cleanup, run the following command.

   helm uninstall protegrity-agent -n pty-protegrity-agent --wait --timeout=10m
   

3. To verify the Agent node cleanup before reinstalling or deleting the namespace, run the following command:

   kubectl get nodepool protegrity-agent --ignore-not-found
   kubectl get nodeclaims,nodes -l karpenter.sh/nodepool=protegrity-agent
   

   Additionally, verify the node class for the required cloud.

   Cloud	Verification Command
   AWS	kubectl get ec2nodeclass protegrity-agent-nodeclass --ignore-not-found
   Azure	kubectl get aksnodeclass protegrity-agent-nodeclass --ignore-not-found

   No resources should be returned by the verification commands. If cleanup is still in progress, wait for the associated resources to be removed and repeat the verification steps.

   If Karpenter resources are disabled, node class verification can be skipped. Any node classes that are managed outside of the Agent deployment should remain in place and must not be removed.

4. Optionally, delete the Agent namespace to perform a complete removal of all Agent resources. Deleting the namespace removes any remaining Persistent Volume Claims (PVCs), Secrets, and other namespace-scoped resources.

   Note: Skip this step if these resources must be retained for a future reinstallation or recovery scenario.

   Run the following command:

   kubectl delete namespace pty-protegrity-agent --wait=true --timeout=10m
   

   Note: If a command fails or times out, stop and ask your PPC administrator to investigate. Do not automatically remove finalizers; they protect controller cleanup. Neither AWS nor Azure requires a finalizer patch for normal uninstall.