automation-suite
2023.4
false
- Overview
- Requirements
- Installation
- Post-installation
- Migration and upgrade
- Upgrading Automation Suite on EKS/AKS
- Migration options
- 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 Insights
- Step 7: Deleting the default tenant
- B) Single tenant migration
- 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 cannot communicate with FQDN in a proxy environment
- Health check of Automation Suite Robots fails
OUT OF SUPPORT
Automation Suite on EKS/AKS Installation Guide
Last updated Nov 21, 2024
The backup setup does not work due to a failure to connect to Azure Government
Following an Automation Suite on AKS installation or upgrade, the backup setup does not work because of a failure to connect to Azure Government.
You can fix the issue by taking the following steps:
- Create a file named
velerosecrets.txt, with the following contents:AZURE_CLIENT_SECRET=<secretforserviceprincipal> AZURE_CLIENT_ID=<clientidforserviceprincipal> AZURE_TENANT_ID=<tenantidforserviceprincipal> AZURE_SUBSCRIPTION_ID=<subscriptionidforserviceprincipal> AZURE_CLOUD_NAME=AzureUSGovernmentCloud AZURE_RESOURCE_GROUP=<infraresourcegroupoftheakscluster>AZURE_CLIENT_SECRET=<secretforserviceprincipal> AZURE_CLIENT_ID=<clientidforserviceprincipal> AZURE_TENANT_ID=<tenantidforserviceprincipal> AZURE_SUBSCRIPTION_ID=<subscriptionidforserviceprincipal> AZURE_CLOUD_NAME=AzureUSGovernmentCloud AZURE_RESOURCE_GROUP=<infraresourcegroupoftheakscluster> - Encode the data in the
velerosecrets.txtfile as Base64:export b64velerodata=$(cat velerosecrets.txt | base64)export b64velerodata=$(cat velerosecrets.txt | base64) - Update the
velero-azuresecret in theveleronamespace, as shown in the following example:apiVersion: v1 kind: Secret metadata: name: velero-azure namespace: velero data: cloud: <insert the $b64velerodata value here>apiVersion: v1 kind: Secret metadata: name: velero-azure namespace: velero data: cloud: <insert the $b64velerodata value here> - Restart the
velerodeployment:kubectl rollout restart deploy -n velerokubectl rollout restart deploy -n velero
