Remove a ForgeOps deployment

This page provides instructions for removing ForgeOps deployments for the following scenarios:

Remove a Helm deployment from GKE, EKS, or AKS

Set up your Kubernetes context:
1. Set the KUBECONFIG environment variable so that your Kubernetes context references the cluster in which you deployed the platform.
2. Set the active namespace in your Kubernetes context to the Kubernetes namespace in which you deployed the platform:
  $ kubens my-namespace
Remove the ForgeOps deployment:
```
$ cd /path/to/forgeops/charts/identity-platform
$ helm uninstall identity-platform
```
Running helm uninstall identity-platform doesn’t delete PVCs and the amster job from your namespace.
(Optional) To delete PVCs, use the kubectl command. For example, to delete data-ds-idrepo-0 and data-ds-cts-0:
```
$ kubectl delete pvc data-ds-idrepo-0 data-ds-cts-0
```
(Optional) To delete the amster job, use the kubectl command:
```
$ kubectl delete job amster
```
(Optional) Delete your cluster:
1. Change to the directory in your forgeops-extras repository clone that contains Terraform artifacts:
  $ cd /path/to/forgeops-extras/terraform
2. Run the tf-destroy script to create your cluster:
  $ ./tf-destroy
  Respond yes to the Do you really want to destroy all resources? prompt.

Set the active namespace in your Kubernetes context to the Kubernetes namespace in which you deployed the platform:
```
$ kubens my-namespace
```
Remove the ForgeOps deployment:
```
$ cd /path/to/forgeops/charts/identity-platform
$ helm uninstall identity-platform
```
Running helm uninstall identity-platform doesn’t delete PVCs and the amster job from your namespace.
(Optional) To delete PVCs, use the kubectl command. For example, to delete data-ds-idrepo-0 and data-ds-cts-0:
```
$ kubectl delete pvc data-ds-idrepo-0 data-ds-cts-0
```
(Optional) To delete the amster job, use the kubectl command:
```
$ kubectl delete job amster
```
(Optional) Delete your cluster:
```
$ minikube stop
$ minikube delete
```

Set up your Kubernetes context:
1. Set the KUBECONFIG environment variable so that your Kubernetes context references the cluster in which you deployed the platform.
2. Set the active namespace in your Kubernetes context to the Kubernetes namespace in which you deployed the platform:
  $ kubens my-namespace
Remove the ForgeOps deployment:
```
$ cd /path/to/forgeops/bin
$ ./forgeops delete --env-name my-env
```
Respond Y to all the OK to delete? prompts.
(Optional) Delete your cluster:
1. Change to the directory in your forgeops-extras repository clone that contains Terraform artifacts:
  $ cd /path/to/forgeops-extras/terraform
2. Run the tf-destroy script to create your cluster:
  $ ./tf-destroy
  Respond yes to the Do you really want to destroy all resources? prompt.

Set the active namespace in your Kubernetes context to the Kubernetes namespace in which you deployed the platform:
```
$ kubens my-namespace
```
Remove the ForgeOps deployment:
```
$ cd /path/to/forgeops/bin
$ ./forgeops delete --env-name my-env
```
Respond Y to all the OK to delete? prompts.
(Optional) Delete your cluster:
```
$ minikube stop
$ minikube delete
```