automation-suite
2024.10
true
- Overview
- Requirements
- Pre-installation
- Installation
- Post-installation
- Migration and upgrade
- Upgrading Automation Suite
- Migrating standalone products to Automation Suite
- Step 1: Restoring the standalone product database
- Step 2: Updating the schema of the restored product database
- Step 3: Moving the Identity organization data from standalone to Automation Suite
- Step 4: Backing up the platform database in Automation Suite
- Step 5: Merging organizations in Automation Suite
- Step 6: Updating the migrated product connection strings
- Step 7: Migrating standalone Orchestrator
- Step 8: Migrating standalone Insights
- Step 9: Deleting the default tenant
- Performing a single tenant migration
- Migrating between Automation Suite clusters
- Migrating from Automation Suite on EKS/AKS to Automation Suite on OpenShift
- Monitoring and alerting
- Cluster administration
- Product-specific configuration
- Troubleshooting
- The backup setup does not work due to a failure to connect to Azure Government
- Pods in the uipath namespace stuck when enabling custom node taints
- Unable to launch Automation Hub and Apps with proxy setup
- Robot cannot connect to an Automation Suite Orchestrator instance
- Log streaming does not work in proxy setups
- Velero backup fails with FailedValidation error
- Accessing FQDN returns RBAC: access denied error
Automation Suite on EKS/AKS installation guide
Last updated Oct 24, 2025
Accessing an FQDN may return the following error:
RBAC: access deniedRBAC: access denied
This issue occurs because the FQDN and its relevant URL access are routed via Istio. Istio relies on a WASM plugin to route the request to the appropriate destination pod.
If the WASM plugin image is missing in the registry, internal or external, Istio blocks the URL access and returns a
RBAC: access denied error.
To address this issue, you must ensure that the registry is hydrated and the WASM plugin image exists in registry.
To check the WASM plugin image, run teh folowing command:
kubectl get wasmplugin -A -o yaml | grep urlkubectl get wasmplugin -A -o yaml | grep url
url: oci://testing.azurecr.io/istio-wasm-plugin:2024.10.3url: oci://testing.azurecr.io/istio-wasm-plugin:2024.10.3
istio-wasm-plugin:2024.10.3. You must check if this image is present in your registry or not.
