Automation Suite
Performing an in-place upgrade - Automation Suite 2023.10
Banner background image
Automation Suite on Linux Installation Guide
Last updated Feb 13, 2024

Performing an in-place upgrade

The Automation Suite in-place upgrade process allows you to move to a new Automation Suite version while keeping your settings and data intact on the same hardware.

  • In the in-place upgrade process, you first upgrade Kubernetes and other infrastructure components, and then upgrade the shared components and UiPath product services.

  • In case of hard failure beyond recovery during the upgrade process, you need to roll back to the previous version using the backup and restore capability.


To perform an in-place upgrade, make sure you meet the following requirements:
  • You must meet the hardware and software requirements for the new Automation Suite version.

  • Determine the supported versions for each upgrade scenario by checking the upgrade path matrix.

  • Download the required installer and bundle files.

  • If you use an in-cluster object store, you must have your cluster object store directly attached to the nodes' disk using Ceph on raw devices available in 2022.4.7, 2022.10, and 2023.4. For details, see Migrating objectstore from persistent volume to raw disks.

  • If you plan to upgrade from Automation Suite 2022.10 or earlier, and Process Mining is enabled, you must migrate process apps to the new process graph layout before starting the upgrade. For details, see the Process Mining documentation.

  • Since Longhorn is no longer available in Automation Suite versions starting with 2023.10, when performing an upgrade from versions previous to 2023.10, you must perform additional steps to migrate the Longhorn volumes and uninstall Longhorn.

  • An additional disk is required to execute the AI Center training pipeline.

  • Make sure you meet the CPU core requirements. To check the required number of CPU cores, run the following command:

    (alloc=0;for node in $(kubectl get nodes -o,TAINTS:.spec.taints --no-headers  | grep -vE "task.mining|serverless.robot" | awk -F ' ' '{print $1}'); do
            alloc=$((alloc + $(echo $(echo $(echo $(kubectl describe node $node | grep "Allocated resources" -A 8 |grep "%" | grep cpu | awk -F ' ' '{print $2}' | tr -d m)*1.2 | bc)*1.2 | bc)/1 | bc) + 600))
    echo "Required CPU cores $(echo "$(echo $alloc+999 | bc)/1000" | bc) for upgrade")(alloc=0;for node in $(kubectl get nodes -o,TAINTS:.spec.taints --no-headers  | grep -vE "task.mining|serverless.robot" | awk -F ' ' '{print $1}'); do
            alloc=$((alloc + $(echo $(echo $(echo $(kubectl describe node $node | grep "Allocated resources" -A 8 |grep "%" | grep cpu | awk -F ' ' '{print $2}' | tr -d m)*1.2 | bc)*1.2 | bc)/1 | bc) + 600))
    echo "Required CPU cores $(echo "$(echo $alloc+999 | bc)/1000" | bc) for upgrade")

Process overview


Upgrade process steps


Prepare the upgrade:

  1. Download the installer file.

  2. Regenerate the cluster_config.json file.
  3. Perform various service-related configuration updates.

  4. Configure the external registry or create a temporary registry.


Execute the upgrade:

  1. Configure and create the backup.

  2. Put the cluster in maintenance mode.

  3. Upgrade the infrastructure.

  4. Upgrade the fabric and services.


Post-upgrade steps:

  1. Uninstall MongoDB.

  2. Migrate the Longhorn volume.

  3. Uninstall the temporary registry.

  4. Add the disk for the AI Center training pipeline.

  5. Migrate the Longhorn volume to local volumes on the disk.

  6. Enable the backup.

  • Requirements
  • Process overview
Support and Services icon
Get The Help You Need
UiPath Academy icon
Learning RPA - Automation Courses
UiPath Forum icon
UiPath Community Forum
Uipath Logo White
Trust and Security
© 2005-2024 UiPath. All rights reserved.