- Overview
- Requirements
- Installation
- Post-installation
- Migration and upgrade
- Upgrading Automation Suite on EKS/AKS
- 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 Orchestrator
- Step 7: Migrating standalone Insights
- Step 8: Migrating standalone Test Manager
- Step 9: Deleting the default tenant
- Performing a single tenant migration
- Migrating from Automation Suite on Linux to Automation Suite on EKS/AKS
- 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
- Pods cannot communicate with FQDN in a proxy environment
- Test Automation SQL connection string is ignored
- EKS backup failure due to Velero version
- Velero backup fails with FailedValidation error
- Accessing FQDN returns RBAC access denied error
- Manual ArgoCD NetworkPolicy mitigation (GHSA-47m3-95c7-g2g8)
Apply a patch update to an existing Automation Suite version on EKS/AKS to address bugs or security vulnerabilities.
An Automation Suite patch is an update to an existing version, which addresses bugs or security vulnerabilities. For instance, patch 2023.10.2+patch3 addresses issues impacting version 2023.10.2.
Instead of applying the patch, we recommend upgrading to the Cumulative Update (CU) that contains the same fix. All fixes provided in patches will also be available in the CU mentioned in the release notes for the patch.
To apply a patch to an existing Automation Suite version, take the following steps:
-
Offline only. Update the registry with the latest images.
- Download the following patch artifacts from Patch artifact download links. Choose the set of artifacts applicable to your patch and registry configuration type.
- To mirror the OCI-compliant registry with the UiPath® registry, download the following artifacts:
as-images.txtas-helm-charts.txtmirror-registry.sh
- To hydrate the OCI-compliant registry with the offline bundle, download the following artifacts:
hydrate-registry.shas-cmk.tar.gz
- To mirror the OCI-compliant registry with the UiPath® registry, download the following artifacts:
- Configure the OCI-compliant registry.
Important:
Do not download the artifacts from the links referenced in the instructions on configuring the OCI-compliant registry. Instead, use the download links provided on the Patch artifact download links page.
- Download the following patch artifacts from Patch artifact download links. Choose the set of artifacts applicable to your patch and registry configuration type.
-
Download
versions.json. For instructions, refer to Patch artifact download links. -
Apply the patch by running the following command:
uipathctl cluster patch <path_to_input.json> --versions <path_to_versions.json> --skip-helm --skip-oss-prereq --only <PRODUCTS(comma separated)>uipathctl cluster patch <path_to_input.json> --versions <path_to_versions.json> --skip-helm --skip-oss-prereq --only <PRODUCTS(comma separated)>The following configuration sample shows how to apply a patch to Orchestrator and Action Center:
uipathctl cluster patch <path_to_input.json> --versions <path_to_versions.json> --skip-helm --skip-oss-prereq --only orchestrator,actioncenteruipathctl cluster patch <path_to_input.json> --versions <path_to_versions.json> --skip-helm --skip-oss-prereq --only orchestrator,actioncenter -
Check if the patch operation was successful by taking the following steps:
- Run the following command to list the versions of all services:
kubectl -n argocd get application -o widekubectl -n argocd get application -o wide - Verify that the versions of the patched services are updated.
- Run the following command to list the versions of all services: