Removing or Resetting SUSE® Security

To remove the SUSE® Security deployment on Kubernetes, use the same yaml file for deployment in the delete command.

This will remove the services and container deployments of SUSE® Security. You may also want to delete the neuvector namespace, persistent volume and cluster roles and clusterrolebindings created in the deployment steps.

If you deployed SUSE® Security using a Helm chart or operator you should delete SUSE® Security using Helm or the appropriate operator command.

In addition to deleting as discussed above and redeploying SUSE® Security, the following steps can be taken in Kubernetes to reset SUSE® Security, which will remove learned rules, groups, and other configuration but leave the SUSE® Security deployment intact.

The admin password is the key to administering the SUSE® Security deployment and view the cluster network activities. It is important to change the password upon install and keep it safely guarded. Sometimes, the password is guarded too well and become loss or the administrator leaves the company. If you have kubectl access to the cluster, you can reset the admin password to the default using the following steps.

Exec into one of the controllers.

Check that the admin entry exists and save the output json somewhere for safe keeping.

Take the output from the above consul kv get command and replace the password_hash string with below string.

Reset the admin account password back to the default. (REPLACE <UPDATED_consul_kv_get_output_with_new_password_hash> BEFORE EXECUTION!!!)