ForgeOps

CDM removal

To remove your CDM cluster when you’re done working with it:

  1. Set the KUBECONFIG environment variable so that your Kubernetes context references the cluster in which you deployed the CDM.

  2. Set the active namespace in your local Kubernetes context to the namespace in which you deployed the CDM.

  3. Remove the CDM:

    • Use the forgeops command

    • Use Helm (technology preview)

    If you installed the CDM with the forgeops install command, remove all CDM artifacts with the forgeops delete command:

    $ cd /path/to/forgeops/bin
$ ./forgeops delete

    Respond Y to all the OK to delete? prompts.

    If you installed the CDM with the helm upgrade --install command, remove the CDM with the helm uninstall command:

    $ cd /path/to/forgeops/charts/identity-platform
$ helm uninstall identity-platform

    Running helm uninstall identity-platform does not delete PVCs and the amster job from your namespace.

    To delete PVCs, use the kubectl command:

    $ kubectl delete pvc data-ds-idrepo-0
$ kubectl delete pvc data-ds-cts-0

    To delete the amster job, use the kubectl command:

    $ kubectl delete job amster

  4. Remove 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.