Delete an App

Open Source Helm App Deletion

The Open Source App Deletion process is a critical and irreversible operation that results in the complete removal of a Helm-based application from your Kubernetes environment. This operation will permanently delete all resources, configurations, and associated components of your deployed open source application. Please read this documentation thoroughly before proceeding, as this action cannot be undone once initiated.

Who Can Delete an Open Source App?

To maintain security and prevent accidental deletions, app deletion permissions are strictly controlled:

• Super Admin: Can delete applications across all workspaces.

• Workspace Owner: Has full permissions to delete any application within their workspace.

• Application Owner: Has permission to delete applications they deployed within their assigned workspace.

Critical Disclaimer – Proceed with Caution

IMPORTANT: Open source app deletion is an irreversible process. Once initiated, the following components will be permanently removed:

Helm and ArgoCD Resources

• Complete Helm release and associated resources

• All ArgoCD applications managing the Helm deployment

• Helm charts configurations and values

• Release history and rollback points

• ArgoCD project configurations specific to your application

Kubernetes Resources

• All deployments, pods, and containers created by the Helm chart

• Service configurations and endpoints

• Configmap and Secrets created during deployment

• Any persistent volumes or volume claims

• Application-specific network policies

• Resource quotas and limits defined by the chart

DNS Configuration

• CNAME records pointing to your application

• All associated DNS entries

• Service discovery configurations

Container Registry Resources

• All container images associated with your application

• Image tags and versions

• Registry-specific configurations

• Build artifacts and layers

Git Repository Resources

• Complete application repository

• All Helm chart configurations

• Values files across different environments

• CI/CD configurations

• Documentation and deployment guides

Additional Impact

• All running instances of your application will be terminated

• Active connections to your application will be disrupted

• Application monitoring and logging configurations will be removed

• Access to application metrics and historical data will be lost

• Integration points with other services may be affected

Deletion Process Flow

1. Preparing Deletion Context

   • System validates authorization

   • Confirms application exists and is eligible for deletion

   • Creates deletion audit trail

   • Verifies Helm release status

2. Delete App from ArgoCD

   • Removes Helm release from ArgoCD management

   • Terminates continuous deployment pipeline

   • Cleans up ArgoCD application configurations

   • Removes Helm release history

3. Delete App from K8s Cluster

   • Uninstalls Helm release

   • Removes all Kubernetes resources created by the chart

   • Terminates running pods and containers

   • Cleans up associated configurations

4. Delete CNAME Record

   • Removes DNS entries

   • Updates routing configurations

   • Cleans up service discovery settings

5. Delete Container Registry Repository

   • Removes the container images

   • Deletes image tags and versions

   • Cleans up registry configurations

6. Delete Repository from Git

   • Removes entire application repository

   • Deletes all Helm chart configurations

   • Cleans up CI/CD configurations

   • Removes deployment documentation

7. Finalize Deletion

   • Verifies complete removal of all components

   • Updates system records

   • Finalizes audit logging

   • Confirms Helm release uninstallation

Pre-Deletion Checklist

Before proceeding with open source app deletion, ensure you have:

1. Backed up any custom values files or configurations

2. Documented any modifications made to the original Helm chart

3. Exported any necessary application data

4. Verified that no other applications depend on this deployment

5. Noted down the chart version and configuration for future reference if needed

6. Checked for any persistent volumes containing important data

Irreversibility Warning

This operation cannot be undone. Once you confirm the deletion:

• There is no rollback mechanism

• Deleted Helm releases cannot be recovered

• Container images will be permanently removed

• Application restoration would require complete redeployment

• Historical data and configurations will be permanently lost

Audit and Compliance

All application deletion actions are logged for audit purposes, including:

• Timestamp of deletion

• User who initiated the deletion

• Helm release information

• Complete inventory of deleted resources

• Verification of deletion completion

• Container registry clean up status