automation-suite
2024.10
true
- Overview
- Requirements
- Pre-installation
- Installation
- Post-installation
- Migration and upgrade
- Monitoring and alerting
- Cluster administration
- Product-specific configuration
- Troubleshooting
- Unable to access Automation Hub following upgrade to Automation Suite 2024.10.0
- AI Center provisioning failure after upgrading to 2023.10 or later
- Insights volumes created in two different zones following migration
Automation Suite on EKS/AKS Installation Guide
Last updated Feb 10, 2025
Insights volumes created in two different zones following migration
When you migrate from Automation Suite on Linux to Automation Suite on EKS/AKS and your target cluster spans multiple zones, Insights-related volumes are occasionally created in two different zones. As a result, you may encounter issues when bringing up the Insights service.
To address the problem, take the following steps:
-
Before migration, cordon the nodes in all zones, with the exception of the zone where you want the volumes to be located. To cordon the nodes, run the following command:
kubectl cordon <node name>kubectl cordon <node name> -
Execute the Automation Suite on Linux to Automation Suite on EKS/AKS migration by running the command in Step 1 of Running the cluster migration.
-
Uncordon all the nodes you cordoned before the migration by running the following command:
kubectl uncordon <node name>kubectl uncordon <node name>
