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
- Performing database maintenance
- Configuring the FQDN post-installation
- Forwarding logs to external tools
- Switching to the secondary cluster manually in an Active/Passive setup
- Disaster Recovery: Performing post-installation operations
- Converting an existing installation to multi-site setup
- Guidelines on upgrading an Active/Passive deployment
- Guidelines on backing up and restoring an Active/Passive deployment
- Product-specific configuration
- Troubleshooting
Automation Suite on EKS/AKS installation guide
Last updated May 8, 2025
Disaster Recovery: Performing post-installation operations
The generated kubeconfig file must have only limited permissions to access another cluster's correct set of Kube objects.
To generate the base64-encoded kubeconfig file, run the following command:
uipathctl config kubeconfig get --multisiteuipathctl config kubeconfig get --multisite|
Parameter |
Description |
--multisite | Generates the kubeconfig file with limited permissions. |
To update the kubeconfig file of another cluster and link both of them, run the following command:
uipathctl config kubeconfig set --secret "fgad8GDH9dbks" --multisiteuipathctl config kubeconfig set --secret "fgad8GDH9dbks" --multisite|
Parameter |
Description |
--secret | Accepts the base64-encoded kubeconfig file. |
--multisite | Links the two clusters. |
