- Overview
- Requirements
- Installation
- Q&A: Deployment templates
- Downloading the installation packages
- Install-uipath.sh Parameters
- Enabling Redis High Availability Add-On for the cluster
- Document Understanding configuration file
- Adding a dedicated agent node with GPU support
- Connecting Task Mining application
- Adding a dedicated agent Node for Task Mining
- Adding a Dedicated Agent Node for Automation Suite Robots
- Post-installation
- Cluster administration
- Monitoring and alerting
- Migration and upgrade
- Migration options
- 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 Insights
- Step 7: Deleting the default tenant
- Performing a single tenant migration
- Product-specific configuration
- Best practices and maintenance
- Troubleshooting
- How to troubleshoot services during installation
- How to uninstall the cluster
- How to clean up offline artifacts to improve disk space
- How to clear Redis data
- How to enable Istio logging
- How to manually clean up logs
- How to clean up old logs stored in the sf-logs bucket
- How to disable streaming logs for AI Center
- How to debug failed Automation Suite installations
- How to delete images from the old installer after upgrade
- How to automatically clean up Longhorn snapshots
- How to disable TX checksum offloading
- How to address weak ciphers in TLS 1.2
- Unable to run an offline installation on RHEL 8.4 OS
- Error in Downloading the Bundle
- Offline installation fails because of missing binary
- Certificate issue in offline installation
- First installation fails during Longhorn setup
- SQL connection string validation error
- Prerequisite check for selinux iscsid module fails
- Azure disk not marked as SSD
- Failure after certificate update
- Antivirus causes installation issues
- Automation Suite not working after OS upgrade
- Automation Suite requires backlog_wait_time to be set to 0
- Volume unable to mount due to not being ready for workloads
- Unable to launch Automation Hub and Apps with proxy setup
- Failure to upload or download data in objectstore
- PVC resize does not heal Ceph
- Failure to resize PVC
- Failure to resize objectstore PVC
- Rook Ceph or Looker pod stuck in Init state
- StatefulSet volume attachment error
- Failure to create persistent volumes
- Storage reclamation patch
- Backup failed due to TooManySnapshots error
- All Longhorn replicas are faulted
- Setting a timeout interval for the management portals
- Update the underlying directory connections
- Authentication not working after migration
- Kinit: Cannot find KDC for realm <AD Domain> while getting initial credentials
- Kinit: Keytab contains no suitable keys for *** while getting initial credentials
- GSSAPI operation failed due to invalid status code
- Alarm received for failed Kerberos-tgt-update job
- SSPI provider: Server not found in Kerberos database
- Login failed for AD user due to disabled account
- ArgoCD login failed
- Failure to get the sandbox image
- Pods not showing in ArgoCD UI
- Redis probe failure
- RKE2 server fails to start
- Secret not found in UiPath namespace
- ArgoCD goes into progressing state after first installation
- Unexpected inconsistency; run fsck manually
- MongoDB pods in CrashLoopBackOff or pending PVC provisioning after deletion
- MongoDB Pod Fails to Upgrade From 4.4.4-ent to 5.0.7-ent
- Unhealthy services after cluster restore or rollback
- Pods stuck in Init:0/X
- Prometheus in CrashloopBackoff state with out-of-memory (OOM) error
- Missing Ceph-rook metrics from monitoring dashboards
- Pods cannot communicate with FQDN in a proxy environment
- Using the Automation Suite Diagnostics Tool
- Using the Automation Suite support bundle
- Exploring Logs
Performing node maintenance
There are scenarios where you may want to perform a node maintenance activity, such as the following:
- When applying security patches;
- When performing an operating system upgrade;
- When changing any network configuration;
- When performing any other activity that your organization mandates.
While performing node maintenance operations, it is possible that you may accidentally break the cluster. To avoid any adverse situation, follow the guidance provided here.
- UiPath® does not provide guidance on how to perform node maintenance activities. You must contact your IT team for this.
- The following guidelines only provide instructions on the steps you must take before and after the node maintenance operation, to ensure the cluster is healthy.
- It is good practice to perform node maintenance activities on one node at a time.
Pre-node maintenance
-
To ensure that the cluster is healthy while you are performing node maintenance activity, you must drain the workloads running on that node to other nodes. To drain the node, run the following command:
systemctl stop node-drainsystemctl stop node-drain -
Stop the Kubernetes process running on the node. Run either of the following commands:
-
Server node:
systemctl stop rke2-serversystemctl stop rke2-server -
Agent node:
systemctl stop rke2-agentsystemctl stop rke2-agent
-
-
If your maintenance activity includes upgrading the RPM packages on the machine, you must skip upgrading the
rke2package to avoid any compatibility issues.-
It is recommended to add the
rke2package to the exclusion list of the RPM upgrade. To modify the/etc/yum.conffile, addrke2in exclusion. For details, see these instructions. -
Alternatively, you can temporarily exclude
rke2duringyum upgradeusing the following command:yum upgrade --exclude "rke2-*"yum upgrade --exclude "rke2-*"Important:If not excluded,
rke2-packages might get upgraded to the latest version, causing issues in the Automation Suite cluster.rke2-*package upgrade will be handled via the Automation Suite upgrade.
-
-
Proceed with your node maintenance activity. Once the upgrade is complete, continue with the post-node maintenance activity.
Post-node maintenance
-
Reboot the node either by running
sudo rebootor by using any other safe reboot mechanism you may prefer. -
The RKE2 service should start automatically. To check the status of the RKE2 service, run the following commands:
-
Server node:
systemctl is-active rke2-server.service || systemctl start rke2-server.servicesystemctl is-active rke2-server.service || systemctl start rke2-server.service -
Agent node:
systemctl is-active rke2-agent.service || systemctl start rke2-agent.servicesystemctl is-active rke2-agent.service || systemctl start rke2-agent.service
-
-
If the RKE2 service did not start automatically, start it manually by running the following commands:
-
Server node:
systemctl start rke2-serversystemctl start rke2-server -
Agent node:
systemctl start rke2-agentsystemctl start rke2-agent
-
-
Once the RKE2 service is started, you must uncordon the node to ensure Kubernetes can now schedule workloads on this node. To uncordon, run the following command:
systemctl start node-uncordonsystemctl start node-uncordon