- Overview
- Requirements
- Installation
- Post-installation
- Migration and upgrade
- Upgrading Automation Suite on EKS/AKS
- Step 1: Moving the Identity organization data from standalone to Automation Suite
- Step 2: Restoring the standalone product database
- Step 3: Backing up the platform database in Automation Suite
- Step 4: Merging organizations in Automation Suite
- Step 5: Updating the migrated product connection strings
- Step 6: Migrating standalone Orchestrator
- Step 7: Migrating standalone Insights
- Step 8: Migrating standalone Test Manager
- Step 9: Deleting the default tenant
- Performing a single tenant migration
- Migrating from Automation Suite on Linux to Automation Suite on EKS/AKS
- 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
- Pods cannot communicate with FQDN in a proxy environment
- Test Automation SQL connection string is ignored
- EKS backup failure due to Velero version
- Velero backup fails with FailedValidation error
- Accessing FQDN returns RBAC access denied error
- Manual ArgoCD NetworkPolicy mitigation (GHSA-47m3-95c7-g2g8)
Accessing FQDN returns RBAC access denied error
Cause and resolution for RBAC access denied errors when accessing an FQDN via Istio in Automation Suite on EKS/AKS.
Description
Accessing an FQDN may return the following error:
RBAC: access denied
RBAC: 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.
Solution
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 url
kubectl get wasmplugin -A -o yaml | grep url
The output will be similar to the one from the following example:
url: oci://testing.azurecr.io/istio-wasm-plugin:2024.10.3
url: oci://testing.azurecr.io/istio-wasm-plugin:2024.10.3
In the example above, the WASM plugin image is istio-wasm-plugin:2024.10.3. You must check if this image is present in your registry or not.