automation-suite
2024.10
true
- Overview
- Requirements
- Pre-installation
- Installation
- Post-installation
- Migration and upgrade
- 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
The backup setup does not work due to a failure to connect to Azure Government
Automation Suite on EKS/AKS Installation Guide
Last updated Dec 18, 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.txt
file as Base64:export b64velerodata=$(cat velerosecrets.txt | base64)
export b64velerodata=$(cat velerosecrets.txt | base64) - Update the
velero-azure
secret in thevelero
namespace, 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
velero
deployment:kubectl rollout restart deploy -n velero
kubectl rollout restart deploy -n velero