- Overview
- Requirements
- Pre-installation
- Preparing the installation
- Downloading the installation packages
- Configuring the OCI-compliant registry
- Granting installation permissions
- Installing and configuring the service mesh
- Installing and configuring the GitOps tool
- Installing the External Secrets Operator in Kubernetes
- Applying miscellaneous configurations
- Running uipathctl
- Installation
- Post-installation
- Migration and upgrade
- Monitoring and alerting
- Cluster administration
- Product-specific configuration
- Orchestrator advanced configuration
- Configuring Orchestrator parameters
- Configuring appSettings
- Configuring the maximum request size
- Overriding cluster-level storage configuration
- Configuring NLog
- Saving robot logs to Elasticsearch
- Configuring credential stores
- Configuring encryption key per tenant
- Cleaning up the Orchestrator database
- Skipping host library installation
- AI Trust Layer
- Troubleshooting
- AI Center provisioning failure after upgrading to 2023.10 or later
- Insights volumes created in two different zones following migration
- Upgrade fails due to overridden Insights PVC sizes
- Velero backup components remain after upgrading on AKS from Automation Suite 2024.10.x
- 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
- Velero backup fails with FailedValidation error
- External Secrets troubleshooting
- Temporal as a Service troubleshooting
- AI Center and Document Understanding pods fail to start with TLS certificate verification enabled
- TLS certificate validation errors
- Fluentd does not export logs in IPv6 environments
- Studio Desktop cannot load Integration Service connectors and activities
- Manual ArgoCD NetworkPolicy mitigation (GHSA-47m3-95c7-g2g8)
- Configuring resource requests and limits for uipathctl-created workloads
Velero backup components remain after upgrading on AKS from Automation Suite 2024.10.x
Solutions for leftover Velero backup components and a failing backup schedule after upgrading Automation Suite on AKS from 2024.10.x.
Description
Starting with Automation Suite 2.2510.0, AKS and EKS use the cloud provider's native backup instead, and Velero is no longer a managed component on these distributions. As a result, upgrading Automation Suite on AKS from version 2024.10.x does not remove Velero: its components and the pre-existing backup schedule remain in the cluster and continue to trigger, failing due to storage access errors. uipathctl snapshot commands return an error stating that snapshot commands are not supported for the AKS distribution.
If backup was never enabled before the upgrade, no action is required.
Solution
To remove the leftover Velero components, take the following steps:
Stop the schedule
- List the existing backup schedules:
kubectl -n velero get scheduleskubectl -n velero get schedules - Delete the schedule:
kubectl -n velero delete schedule <schedule-name>kubectl -n velero delete schedule <schedule-name>
Remove the components
- Uninstall Velero:
helm -n velero uninstall velerohelm -n velero uninstall velero - Delete the leftover secrets:
kubectl -n velero delete secret velero-azure velero-aws disaster-recovery-config --ignore-not-foundkubectl -n velero delete secret velero-azure velero-aws disaster-recovery-config --ignore-not-found - Delete the leftover config map:
kubectl -n velero delete configmap uipath-policy --ignore-not-foundkubectl -n velero delete configmap uipath-policy --ignore-not-found - Delete the
veleronamespace:kubectl delete namespace velerokubectl delete namespace velero
Decommission cloud resources
Depending on your setup, also review and remove the following cloud resources:
- Disk snapshots - one per backup run, located in the resource group from the volume snapshot location. Delete only Velero-tagged snapshots.
- Backup storage account and container - deleting removes all backup data.
- The service principal or managed identity you supplied for backup, and its role assignment on that storage account. This is not managed by Automation Suite. If it is shared with other workloads, remove only the role assignment.