- Overview
- Requirements
- Pre-installation
- Preparing the installation
- Downloading the installation packages
- Configuring the OCI-compliant registry
- Granting installation permissions
- Installing and configuring the service mesh
- Installing and configuring the GitOps tool
- Installing the External Secrets Operator in Kubernetes
- Applying miscellaneous configurations
- Running uipathctl
- Installation
- Post-installation
- Migration and upgrade
- Monitoring and alerting
- Cluster administration
- Product-specific configuration
- Troubleshooting

Automation Suite on EKS/AKS installation guide
-
Kubectl CLI (
kubectl) installed and configured. -
Appropriate permissions to delete resources in the target namespaces.
Before proceeding, you must gather the following information:
-
UiPath namespace where Dapr is installed.
-
ArgoCD namespace (typically
argocdoropenshift-gitops).
-
Delete the Dapr application from ArgoCD:
# Verify the application exists first kubectl get application.argoproj.io dapr -n <argocd_namespace> # If it exists, delete it kubectl delete application.argoproj.io dapr -n <argocd_namespace># Verify the application exists first kubectl get application.argoproj.io dapr -n <argocd_namespace> # If it exists, delete it kubectl delete application.argoproj.io dapr -n <argocd_namespace>Wait for resources to be deleted.
-
Delete Dapr custom resources:
# Delete all Dapr components in the UiPath namespace kubectl delete components.dapr.io --all -n <uipath_namespace> # Delete all Dapr configurations in the UiPath namespace kubectl delete configurations.dapr.io --all -n <uipath_namespace> # Delete all Dapr resiliencies in the UiPath namespace kubectl delete resiliencies.dapr.io --all -n <uipath_namespace> # Delete all Dapr subscriptions in the UiPath namespace kubectl delete subscriptions.dapr.io --all -n <uipath_namespace># Delete all Dapr components in the UiPath namespace kubectl delete components.dapr.io --all -n <uipath_namespace> # Delete all Dapr configurations in the UiPath namespace kubectl delete configurations.dapr.io --all -n <uipath_namespace> # Delete all Dapr resiliencies in the UiPath namespace kubectl delete resiliencies.dapr.io --all -n <uipath_namespace> # Delete all Dapr subscriptions in the UiPath namespace kubectl delete subscriptions.dapr.io --all -n <uipath_namespace> -
Delete Dapr custom resource definitions (CRDs):
# Delete Dapr CRDs kubectl delete crd components.dapr.io kubectl delete crd configurations.dapr.io kubectl delete crd resiliencies.dapr.io kubectl delete crd subscriptions.dapr.io# Delete Dapr CRDs kubectl delete crd components.dapr.io kubectl delete crd configurations.dapr.io kubectl delete crd resiliencies.dapr.io kubectl delete crd subscriptions.dapr.io -
Remove Dapr webhook configurations:
# Delete the Dapr sidecar injector webhook kubectl delete mutatingwebhookconfigurations dapr-sidecar-injector# Delete the Dapr sidecar injector webhook kubectl delete mutatingwebhookconfigurations dapr-sidecar-injector -
Remove Dapr-specific role bindings
# Verify if the role binding exists kubectl get rolebinding -n <uipath_namespace> | grep dapr # If it exists, delete dapr specific role binding kubectl delete rolebinding <dapr-role-binding> -n <uipath_namespace># Verify if the role binding exists kubectl get rolebinding -n <uipath_namespace> | grep dapr # If it exists, delete dapr specific role binding kubectl delete rolebinding <dapr-role-binding> -n <uipath_namespace> -
Remove Dapr-specific roles:
# Check if the dapr-creator role exists kubectl get role -n <uipath_namespace> | grep dapr # If it exists, delete dapr specific rolekubectl delete role <dapr-role> -n <uipath_namespace># Check if the dapr-creator role exists kubectl get role -n <uipath_namespace> | grep dapr # If it exists, delete dapr specific rolekubectl delete role <dapr-role> -n <uipath_namespace> -
Clean up remaining Dapr resources
-
Pods:
# List all Dapr-related pods kubectl get pods -n <uipath_namespace> | grep dapr # Delete each Dapr pod if any kubectl delete pod <pod_name> -n <uipath_namespace># List all Dapr-related pods kubectl get pods -n <uipath_namespace> | grep dapr # Delete each Dapr pod if any kubectl delete pod <pod_name> -n <uipath_namespace> -
Services:
# List all Dapr-related services kubectl get svc -n <uipath_namespace> | grep dapr # Delete each Dapr service if any kubectl delete svc <service_name> -n <uipath_namespace># List all Dapr-related services kubectl get svc -n <uipath_namespace> | grep dapr # Delete each Dapr service if any kubectl delete svc <service_name> -n <uipath_namespace> -
Deployments:
# List all Dapr-related deployments kubectl get deployments -n <uipath_namespace> | grep dapr # Delete each Dapr deployment kubectl delete deployment <deployment_name> -n <uipath_namespace># List all Dapr-related deployments kubectl get deployments -n <uipath_namespace> | grep dapr # Delete each Dapr deployment kubectl delete deployment <deployment_name> -n <uipath_namespace>
-
After completing all the uninstallation steps, verify that all Dapr components have been removed:
# Check for any remaining Dapr resources
kubectl get pods -n <uipath_namespace> | grep dapr
kubectl get svc -n <uipath_namespace> | grep dapr
kubectl get deployments -n <uipath_namespace> | grep dapr
kubectl get crd | grep dapr# Check for any remaining Dapr resources
kubectl get pods -n <uipath_namespace> | grep dapr
kubectl get svc -n <uipath_namespace> | grep dapr
kubectl get deployments -n <uipath_namespace> | grep dapr
kubectl get crd | grep daprIf certain resources cannot be deleted:
-
Ensure you have the necessary permissions.
-
Check if the resources are being managed by another controller.
-
Investigate any dependencies that might be preventing deletion.