2.2510.2

Release date: April 15, 2026

cgroup v2 requirement for upgrade

Automation Suite now requires host nodes to run cgroup v2. If your environment uses cgroup v1 (the default on RHEL 8.x), you must migrate to cgroup v2 before upgrading. The RKE2 1.35 runtime used by Automation Suite deprecates cgroup v1, and the Kubelet will fail to start if cgroup v1 is detected.

Although the failCgroupV1 kubelet parameter can temporarily bypass this check, it may be deprecated in future Rancher releases. It is strongly recommended to migrate to cgroup v2 before performing the upgrade.

For details, refer to RHEL compatibility matrix and How to migrate to cgroup v2.

TLS certificate chain validation

Automation Suite now requires a complete TLS certificate chain - a leaf certificate, all intermediate certificates, and the root CA. Previously, you could supply a partial chain (leaf certificate and root CA only). You must update your Certificate Authority Bundle to include all intermediate certificates. If you do not, TLS validation will fail.

For details, refer to Certificate requirements.

New mandatory field for disaster recovery deployments

We have introduced a new mandatory type field in the multisite section of cluster_config.json. This field is required when configuring disaster recovery deployments and specifies the deployment type. You must set it to either active-active or active-passive. This field is required for both the primary and secondary cluster configurations.

For details, refer to Disaster recovery: Active/Passive and Active/Active configurations.

Enhanced registry hydration process

We have improved the registry hydration process to retrieve credentials more reliably. Registry credentials are now first retrieved from the cluster_config.json file, with a fallback to Kubernetes secrets if credentials are not found there. Previously, the process relied solely on the Docker registry secret within the Kubernetes cluster, which could fail if the uipath namespace was not present or the expected secret was unavailable.

Enhanced support bundle generation for RKE2

The support bundle tool can now collect the RKE2 bundle even when RKE2 is down. Previously, support bundle generation would fail if RKE2 was unavailable. For more details, refer to Using the Automation Suite support bundle.

Improved prerequisite check messages for Object Store API validation

Object Store API prerequisite checks now provide clearer error messages, making it easier to diagnose and resolve configuration issues before installation.

Support for new RHEL versions

We have expanded our OS support to include RHEL versions 9.7 and 10.0. For details on the supported RHEL versions, refer to RHEL compatibility matrix.

Integration Service support for FIPS 140-2

Integration Service is now supported on Automation Suite deployments that run on FIPS 140-2-enabled machines. For details, refer to Security and compliance.

New Integration Service configuration for sovereign cloud deployments

A new optional queue_config.fqdn_suffix field is now available under integrationservices in cluster_config.json. This field is intended for sovereign or national cloud deployments where queue endpoints use a non-standard FQDN suffix, such as China AWS (amazonaws.com.cn), China Azure (core.chinacloudapi.cn), or Azure US Government (core.usgovcloudapi.net). If the field is left empty or omitted, default suffixes apply.

For details, refer to Configuring the queue FQDN suffix for sovereign cloud deployments.

New OOM alerts for container memory monitoring

Automation Suite now includes two new custom Prometheus alerts in the monitoring-oom-alerts rule group to help you detect and respond to container memory issues:

• KubeContainerOOMKilled - triggers immediately when a container is terminated due to exceeding its memory limit (OOM).
• ContainerMemoryUsageHigh - triggers when a container uses more than 90% of its memory limit for over 15 minutes, serving as an early warning that the container may be terminated due to insufficient memory.

For details, refer to Kubernetes resources alerts.

Extended product support for Active/Passive and Active/Active deployments

Solutions now supports Active/Passive and Active/Active deployments. For details, refer to Disaster recovery - Active/Passive and Active/Active.

Admin

User management role

Organization administrators can now delegate identity management tasks to non-admin users through a new custom organization-level role. When assigned, this role lets users manage user accounts, robot accounts, and local groups at the organization level without granting full organization administrator rights. The role supports granular CRUD permissions per resource type and includes built-in elevation-of-rights protections: users with this role cannot modify the Administrators group or interact with existing organization administrator accounts.

For details, see User management role.

Bug fixes

• We fixed an issue that prevented FQDN updates from completing successfully in IPv6 and dual-stack environments. The issue affected both the infrastructure level and the service level.
• We have fixed an issue that caused some AI Center and Document Understanding pods to fail to start when database TLS certificate verification was enabled.
• We fixed an issue that caused Alertmanager to fail syncing in ArgoCD due to an invalid character in the alertmanager image tag.
• We fixed an issue where Orchestrator and platform services on the secondary cluster in an Active/Active deployment did not push Insights real-time monitoring data due to configuration issues with call redirection from the secondary cluster to the primary cluster.
• We have fixed an issue that prevented the use of custom database names for Solutions. Previously, when you specified a custom database name, the prerequisite checks failed.
• We fixed an issue where the prerequisite check incorrectly validated monitoring and logging components. Since these components are installed after the prerequisite phase, we have removed this validation as it is not necessary.
• This release includes the fixes delivered in Automation Suite 2.2510.0+patch2.

Known issues

Fluentd does not export logs in IPv6 environments

In IPv6 environments, Fluentbit fails to forward logs to Fluentd because the Fluentd forward input plugin binds to an IPv4 address by default.

To address this issue, you must patch the logging ArgoCD Application and set logging-operator.logging.fluentd.forwardInputConfig.bind to ::. For details, refer to the Troubleshooting section.

Kerberos authentication limitations

Kerberos-based authentication is currently not supported for Integration Service.

We are working on bringing Kerberos support to upcoming Automation Suite releases.

Meanwhile, you can use alternative authentication mechanisms such as basic authentication or workload identity-based authentication.

FIPS 140-2 support limitations

Insights does not currently support FIPS. To remain compliant with FIPS 140-2 requirements, you must disable Insights. If you need to use Insights, you can deploy it on a dedicated non-FIPS node.

For details, refer to Security and compliance and How to deploy Insights in a FIPS-enabled cluster.

Deprecation timeline

We recommend that you regularly check the deprecation timeline for any updates regarding features that will be deprecated and removed.

Bundling details

Product versions

The following table outlines the release status, version, and release notes for all UiPath products deployed under Automation Suite 2.2510.2.

Legend:

✅ - This Automation Suite version bundles a new version of the product. New release notes are available.

❌ - This Automation Suite version bundles a previously released version of the product. No new release notes are available.

Product	Product version	Release status	Release notes
Action Center	2.2510.2	✅	Action Center release notes
AI Center	2.2510.2	✅	AI Center release notes
AI Computer Vision	2.2510.2	✅	AI Computer Vision release notes
Apps	2.2510.2	✅	Apps release notes
Automation Hub	2.2510.2	✅	Automation Hub release notes
Automation Ops	2.2510.2	✅	Automation Ops release notes
Data Service	2.2510.2	✅	Data Service release notes
Document Understanding	2.2510.2	✅	Document Understanding AI Center-based projects release notes Document Understanding modern projects release notes
Insights	2.2510.2	✅	Insights release notes
Integration Service	2.2510.2	✅	Integration Service release notes
Orchestrator	2.2510.3	✅	Orchestrator release notes
Solutions	2.2510.2	✅	Solutions release notes
Process Mining	2.2510.2	✅	Process Mining release notes
Test Manager	2.2510.2	✅	Test Manager release notes

Internal third-party component versions

This Automation Suite release bundles the following internal components:

Component	Version
RKE2	1.35.0+rke2r1
ArgoCD	v3.2.6
gatekeeper	v3.21.0
rook	1.18.7
ceph	19.2.3
prometheus-pushgateway	v3.6.0
cert-manager	v1.19.3
kube-logging/logging-operator	6.4.0
kube-logging/config-reloader	6.4.0
istio	1.28.3
velero	1.16.2
reloader	v2.2.7
Prometheus	v3.9.1
Grafana	12.3.1
redis-operator	8.0.10-23
redis-cluster	v8.0.10-81
oauth2-proxy	v7.13.0