automation-suite
2.2510
true
UiPath logo, featuring letters U and I in white

Automation Suite on OpenShift installation guide

Last updated Nov 13, 2025

Meeting the Process Mining prerequisites

Configuring Airflow

ArgoCD requires the following role during the Airflow installation:
apiVersion: rbac.authorization.k8s.io/v1
kind: Role
metadata:
  name: anyuid-role
  namespace: <uipath>
rules:
  - apiGroups: ["security.openshift.io"]
    resources: ["securitycontextconstraints"]
    resourceNames: ["anyuid"]
    verbs: ["use"]apiVersion: rbac.authorization.k8s.io/v1
kind: Role
metadata:
  name: anyuid-role
  namespace: <uipath>
rules:
  - apiGroups: ["security.openshift.io"]
    resources: ["securitycontextconstraints"]
    resourceNames: ["anyuid"]
    verbs: ["use"]
To create the role binding for a dedicated ArgoCD instance, run the following command:
oc create rolebinding argocd-anyuid-binding --role=anyuid-role \
  --serviceaccount=<argocd>:argocd-argocd-application-controller -n <uipath>oc create rolebinding argocd-anyuid-binding --role=anyuid-role \
  --serviceaccount=<argocd>:argocd-argocd-application-controller -n <uipath>

You do not need to perform any additional configuration for a shared ArgoCD instance.

Uninstalling Cert Manager

Prerequisites

  • OpenShift CLI (oc) installed and configured.

  • Appropriate permissions to delete resources in the target namespaces.

Information required

Before proceeding, you must gather the following information:

  • UiPath namespace where cert-manager resources are being used.

  • Whether this is a shared ArgoCD instance or a dedicated one.

Step-by-step uninstallation process

  1. Delete the role bindings for cert-manager:

    • For dedicated ArgoCD instance:

      # Verify if the role binding exists
oc get rolebinding argocd-cert-manager-binding -n <uipath_namespace>

# If it exists, delete it
oc delete rolebinding argocd-cert-manager-binding -n <uipath_namespace># Verify if the role binding exists
oc get rolebinding argocd-cert-manager-binding -n <uipath_namespace>

# If it exists, delete it
oc delete rolebinding argocd-cert-manager-binding -n <uipath_namespace>

    • For shared ArgoCD instance:

      # Verify if the role binding exists
oc get rolebinding gitops-cert-manager-binding -n <uipath_namespace>

# If it exists, delete it
oc delete rolebinding gitops-cert-manager-binding -n <uipath_namespace># Verify if the role binding exists
oc get rolebinding gitops-cert-manager-binding -n <uipath_namespace>

# If it exists, delete it
oc delete rolebinding gitops-cert-manager-binding -n <uipath_namespace>

  2. Delete the cert-manager role:

    # Check if the role exists
oc get role argocd-cert-manager-role -n <uipath_namespace>

# If it exists, delete it
oc delete role argocd-cert-manager-role -n <uipath_namespace># Check if the role exists
oc get role argocd-cert-manager-role -n <uipath_namespace>

# If it exists, delete it
oc delete role argocd-cert-manager-role -n <uipath_namespace>

  3. Clean up cert-manager resources in the namespace:

    # Delete all certificates
oc delete certificates.cert-manager.io --all -n <uipath_namespace>

# Delete all issuers
oc delete issuers.cert-manager.io --all -n <uipath_namespace>

# Delete all clusterissuers if you created any
oc delete clusterissuers.cert-manager.io --all# Delete all certificates
oc delete certificates.cert-manager.io --all -n <uipath_namespace>

# Delete all issuers
oc delete issuers.cert-manager.io --all -n <uipath_namespace>

# Delete all clusterissuers if you created any
oc delete clusterissuers.cert-manager.io --all

  4. Uninstall the cert-manager via operator hub in the OpenShift console.

  5. Verify remaining resources:

    # Check for any remaining cert-manager resources
oc get all -n <uipath_namespace> | grep cert-manager
oc get crd | grep cert-manager# Check for any remaining cert-manager resources
oc get all -n <uipath_namespace> | grep cert-manager
oc get crd | grep cert-manager

Troubleshooting

If certain resources cannot be deleted:

  • Ensure you have the necessary permissions.

  • Check if the resources are being used by other applications.

  • For resources that are stuck in Terminating state, you may need to remove finalizers.

Notes

  • This uninstallation procedure assumes cert-manager was installed via the OpenShift Operator Hub.

  • Only uninstall cert-manager if it is not being used by other applications in your cluster.

  • If multiple applications depend on cert-manager, consider only removing the UiPath-specific resources.

  • Replace <uipath_namespace> with your actual UiPath namespace.

Uninstalling Dapr

Prerequisites

  • OpenShift CLI (oc) installed and configured.

  • Appropriate permissions to delete resources in the target namespaces.

Information required

Before proceeding, you must gather the following information:

  • UiPath namespace where Dapr is installed.

  • ArgoCD namespace (typically argocd or openshift-gitops).

  • Whether this is a shared ArgoCD instance or a dedicated one.

Step-by-step uninstallation process

  1. Delete the Dapr application from ArgoCD:

    # Verify the application exists first
oc get application.argoproj.io dapr -n <argocd_namespace>

# If it exists, delete it
oc delete application.argoproj.io dapr -n <argocd_namespace># Verify the application exists first
oc get application.argoproj.io dapr -n <argocd_namespace>

# If it exists, delete it
oc delete application.argoproj.io dapr -n <argocd_namespace>

    Wait for resources to be deleted.

  2. Delete Dapr custom resources:

    # Delete all Dapr components in the UiPath namespace
oc delete components.dapr.io --all -n <uipath_namespace>

# Delete all Dapr configurations in the UiPath namespace
oc delete configurations.dapr.io --all -n <uipath_namespace>

# Delete all Dapr resiliencies in the UiPath namespace
oc delete resiliencies.dapr.io --all -n <uipath_namespace>

# Delete all Dapr subscriptions in the UiPath namespace
oc delete subscriptions.dapr.io --all -n <uipath_namespace># Delete all Dapr components in the UiPath namespace
oc delete components.dapr.io --all -n <uipath_namespace>

# Delete all Dapr configurations in the UiPath namespace
oc delete configurations.dapr.io --all -n <uipath_namespace>

# Delete all Dapr resiliencies in the UiPath namespace
oc delete resiliencies.dapr.io --all -n <uipath_namespace>

# Delete all Dapr subscriptions in the UiPath namespace
oc delete subscriptions.dapr.io --all -n <uipath_namespace>

  3. Delete Dapr custom resource definitions (CRDs):

    # Delete Dapr CRDs
oc delete crd components.dapr.io
oc delete crd configurations.dapr.io
oc delete crd resiliencies.dapr.io
oc delete crd subscriptions.dapr.io# Delete Dapr CRDs
oc delete crd components.dapr.io
oc delete crd configurations.dapr.io
oc delete crd resiliencies.dapr.io
oc delete crd subscriptions.dapr.io

  4. Remove Dapr webhook configurations:

    # Delete the Dapr sidecar injector webhook
oc delete mutatingwebhookconfigurations dapr-sidecar-injector# Delete the Dapr sidecar injector webhook
oc delete mutatingwebhookconfigurations dapr-sidecar-injector

  5. Remove Dapr-specific role bindings

    • For shared ArgoCD instance:

      # Verify if the role binding exists
oc get rolebinding gitops-dapr-creator-binding -n <uipath_namespace>

# If it exists, delete it
oc delete rolebinding gitops-dapr-creator-binding -n <uipath_namespace>

# Check for cert-manager binding (may be used by other applications)
oc get rolebinding gitops-cert-manager-binding -n <uipath_namespace>

# If it exists and you determine it's safe to delete, run:
oc delete rolebinding gitops-cert-manager-binding -n <uipath_namespace># Verify if the role binding exists
oc get rolebinding gitops-dapr-creator-binding -n <uipath_namespace>

# If it exists, delete it
oc delete rolebinding gitops-dapr-creator-binding -n <uipath_namespace>

# Check for cert-manager binding (may be used by other applications)
oc get rolebinding gitops-cert-manager-binding -n <uipath_namespace>

# If it exists and you determine it's safe to delete, run:
oc delete rolebinding gitops-cert-manager-binding -n <uipath_namespace>

    • For dedicated ArgoCD instance:

      # Verify if the role binding exists
oc get rolebinding dapr-creator-binding -n <uipath_namespace>

# If it exists, delete it
oc delete rolebinding dapr-creator-binding -n <uipath_namespace># Verify if the role binding exists
oc get rolebinding dapr-creator-binding -n <uipath_namespace>

# If it exists, delete it
oc delete rolebinding dapr-creator-binding -n <uipath_namespace>

  6. Remove Dapr-specific roles:

    # Check if the dapr-creator role exists
oc get role dapr-creator -n <uipath_namespace>

# If it exists, delete it
oc delete role dapr-creator -n <uipath_namespace># Check if the dapr-creator role exists
oc get role dapr-creator -n <uipath_namespace>

# If it exists, delete it
oc delete role dapr-creator -n <uipath_namespace>

  7. Clean up remaining Dapr resources

    • Pods:

      # List all Dapr-related pods
oc get pods -n <uipath_namespace> | grep dapr

# Delete each Dapr pod
oc delete pod <pod_name> -n <uipath_namespace># List all Dapr-related pods
oc get pods -n <uipath_namespace> | grep dapr

# Delete each Dapr pod
oc delete pod <pod_name> -n <uipath_namespace>

    • Services:

      # List all Dapr-related services
oc get svc -n <uipath_namespace> | grep dapr

# Delete each Dapr service
oc delete svc <service_name> -n <uipath_namespace># List all Dapr-related services
oc get svc -n <uipath_namespace> | grep dapr

# Delete each Dapr service
oc delete svc <service_name> -n <uipath_namespace>

    • Deployments:

      # List all Dapr-related deployments
oc get deployments -n <uipath_namespace> | grep dapr

# Delete each Dapr deployment
oc delete deployment <deployment_name> -n <uipath_namespace># List all Dapr-related deployments
oc get deployments -n <uipath_namespace> | grep dapr

# Delete each Dapr deployment
oc delete deployment <deployment_name> -n <uipath_namespace>

Verification

After completing all the uninstallation steps, verify that all Dapr components have been removed: 

# Check for any remaining Dapr resources
oc get pods -n <uipath_namespace> | grep dapr
oc get svc -n <uipath_namespace> | grep dapr
oc get deployments -n <uipath_namespace> | grep dapr
oc get crd | grep dapr# Check for any remaining Dapr resources
oc get pods -n <uipath_namespace> | grep dapr
oc get svc -n <uipath_namespace> | grep dapr
oc get deployments -n <uipath_namespace> | grep dapr
oc get crd | grep dapr

Troubleshooting

If 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.

Notes

  • Replace <uipath_namespace> with your actual UiPath namespace.
  • Replace <argocd_namespace> with your actual ArgoCD namespace.

  • Be cautious when deleting shared resources that might affect other applications.

Was this page helpful?

Support and Services
Get The Help You Need
UiPath Academy
Learning RPA - Automation Courses
UiPath Forum
UiPath Community Forum
Uipath Logo
Trust and Security
Terms of Use
Privacy Policy
Cookies Policy
© 2005-2025 UiPath. All rights reserved.