Skip to main content
Version: 3.0.0-beta8

Uninstalling Litmus

Chaos Delegate

To disconnect the Chaos Delegate connected to the ChaosCenter, follow these steps -

  1. Remove the ChaosEngines of the respective Chaos Delegate

    kubectl delete chaosengine <CHAOSENGINE_NAMEs> --all -<AGENT_NAMESPACE>

    If ChaosEngines is unable to delete successfully then the Kubernetes finalizers need to be removed manually.

  2. Login to the ChaosCenter and navigate to the Chaos Delegates Tab.

  3. Click on the Disconnect icon Disconnect Icon of the respective Chaos Delegate you want to disconnect.

  4. On the Modal that appears, confirm your selection by clicking Yes and the selected Chaos Delegate would be disconnected from the ChaosCenter.


    The above disconnect would remove the subscriber component from Chaos Delegate and thus removing the connectivity between the Chaos Delegate and the ChaosCenter.

    If the Chaos Delegate is not reachable it would remove only the entry from the database of the ChaosCenter

Remove the CRs

To remove the CRs Litmus uses, use the following command:

  • To remove individual CRs
kubectl delete chaosexperiments <CHAOSEXPERIMENTS_NAMEs> -n <AGENT_NAMESPACE>
kubectl delete chaosresults <CHAOSRESULTS_NAMEs> -n <AGENT_NAMESPACE>
kubectl delete workflows <WORKFLOW_NAMEs> -n <AGENT_NAMESPACE>
kubectl delete cronworkflows <CRONWORKFLOW_NAMEs> -n <AGENT_NAMESPACE>
kubectl delete eventtrackerpolicies -n <AGENT_NAMESPACE>
  • To remove all CRs
kubectl delete chaosengine,chaosexperiments,chaosresults --all <AGENT_NAMESPACE>
kubectl delete workflows cronworflows --all <AGENT_NAMESPACE>
kubectl delete eventtrackerpolicies -n <AGENT_NAMESPACE>

Delete the Deployments

To remove the respective deployments of the Chaos Delegates you need to manually delete them.

kubectl delete deployment chaos-operator-ce event-tracker workflow-controller chaos-exporter -n <AGENT_NAMESPACE>

Removing Service Account, Role Bindings and Roles

For Cluster Scope

kubectl delete sa argo argo-chaos litmus-admin litmus-cluster-scope event-tracker-sa -n -<AGENT_NAMESPACE>
kubectl delete clusterrolebindings argo-binding chaos-cluster-role-binding event-tracker-clusterole-binding litmus-admin litmus-cluster-scope subscriber-cluster-role-binding
kubectl delete clusterrole litmus-admin chaos-cluster-role subscriber-cluster-role event-tracker-cluster-role litmus-cluster-scope argo-aggregate-to-admin argo-aggregate-to-edit argo-aggregate-to-view argo-cluster-role

For Namespace Scope

kubectl delete sa rolebindings role --all -n <NAMESPACE>

Remove the Litmus CRDs


If the Litmus CRDs are deleted in the Cluster Scope all the respective custom resources in the individual namespaces would stop working.

To remove all the CRDs Litmus uses, use the following command:

kubectl delete -f


To remove the Self Chaos Delegate Resources you need to follow the above Chaos Delegate Uninstall process

To uninstall the ChaosCenter from the system, follow these steps -

Using Kubectl

For Cluster Scope

  • Litmus 2.0.0

    kubectl delete -f

    To delete any specific version of the ChaosCenter, replace the above command with the below command. kubectl delete -f<VERSION>/docs/<VERSION/litmus-<VERSION>.yaml

  • Litmus Master Manifest

    kubectl delete -f

For Namespace Scope

kubectl delete -f ${LITMUS_PORTAL_NAMESPACE}-ns-scoped-litmus-portal-manifest.yml -n ${LITMUS_PORTAL_NAMESPACE}

Using Helm

helm uninstall litmuschaos  --namespace litmus
kubectl delete ns litmus

The namespace doesn't have to be litmus necessarily, instead it should be the same namespace where Litmus ChaosCenter is installed.