ForgeOps

CDK shutdown and removal

When you’re done working with the CDK, shut it down and remove it from your namespace:

  1. Set the active namespace in your local Kubernetes context to the namespace that you created when you performed the setup task.

  2. If you’ve made changes to the AM and IDM configurations in the Git repository on the CDK that you want to save, export the changes to your local forgeops repository clone. If you don’t export the configurations before you run the forgeops delete command, all the changes that you’ve made to the configurations will be lost.

    For more information on syncing changes to your local forgeops repository clone, see:

  3. Remove the CDK:

    • Use the forgeops command

    • Use Helm (technology preview)

    If you installed the CDK with the forgeops install command, remove all CDK 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 CDK with the helm upgrade --install command, remove the CDK 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