automation-suite
2023.10
true
- 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: Deleting the default tenant
- Step 1: Removing old cache keys
- Step 2: Updating AD integration and authentication
- Step 3: Validating the Insights migration
- B) Single tenant migration
- Migrating from Automation Suite on Linux to Automation Suite on EKS/AKS
- Monitoring and alerting
- Cluster administration
- Product-specific configuration
- Using the Orchestrator Configurator Tool
- Configuring Orchestrator parameters
- Orchestrator appSettings
- Configuring appSettings
- Configuring the maximum request size
- Overriding cluster-level storage configuration
- Configuring credential stores
- Configuring encryption key per tenant
- Cleaning up the Orchestrator database
- 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
Step 1: Removing old cache keys
Automation Suite on EKS/AKS Installation Guide
Last updated Nov 11, 2024
Step 1: Removing old cache keys
To clean up the Redis keys for Orchestrator and Identity, take the following steps:
-
For Orchestrator, navigate to the cloud-based Redis console and run the following command:
FLUSHDB
FLUSHDB -
For Identity, navigate to the cloud-based Redis console and run the following command:
SELECT 1 FLUSHDB
SELECT 1 FLUSHDB