The undeploy.sh script is available for download from My Esri and is delivered as a .tar.gz file.
This script deletes all of the Kubernetes resources from your namespace that are associated with the ArcGIS Enterprise on Kubernetes organization. This is commonly used for the following:
- Preparing to perform a restore when the organization is no longer accessible
- Cleaning up a temporary organization that was used for testing purposes
To retain the ingress object, include the -r argument when running the script. This can prevent an extra step to update the organization's DNS record for a subsequent deployment and configuration.
For cloud deployments, the tool also removes the associated load balancer that was provisioned during deployment. Using the -r argument retains the load balancer.
The following are examples of using the script to undeploy ArcGIS Enterprise on Kubernetes:
- Undeploy using a specified namespace
- undeploy.sh -n <my-namespace>
- Undeploy using a saved properties file
- undeploy.sh -f <my.properties>
- Undeploy silently and retain the ingress controller
- undeploy.sh -f <my.properties> -r -s
If the -s argument is not used when running the script, a prompt appears for confirmation as to whether to undeploy the organization interactively:
- If you specify n for no, the script immediately exits and preserves the deployment. This is the assumed default input.
- If you specify y for yes, the script proceeds and undeploys ArcGIS Enterprise on Kubernetes from the cluster.
Script options
The options described in the following table are available in the undeploy.sh script:
| Option | Details |
|---|---|
-h | Usage |
-f <properties_file> | Use specified properties file for undeployment |
-n <namespace> | Undeploy using the specified namespace |
-s or -y | Force undeployment without prompting input |
-r | Do not undeploy the ingress controller service |
-v | Show kubectl commands (verbose) |