- Overview
- Requirements
- Installation
- Post-installation
- Cluster administration
- Monitoring and alerting
- Migration and upgrade
- 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 disable TLS 1.0 and 1.1
- 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 debug failed Automation Suite installations
- How to disable TX checksum offloading
- 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
- SQL connection string validation error
- Failure After Certificate Update
- Automation Suite Requires Backlog_wait_time to Be Set 1
- Cannot Log in After Migration
- Setting a timeout interval for the management portals
- Update the underlying directory connections
- 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 With Error: An Invalid Status Code Was Supplied (Client's Credentials Have Been Revoked).
- Login Failed for User <ADDOMAIN><aduser>. Reason: The Account Is Disabled.
- Alarm Received for Failed Kerberos-tgt-update Job
- SSPI Provider: Server Not Found in Kerberos Database
- 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
- Missing Self-heal-operator and Sf-k8-utils Repo
- Degraded MongoDB or Business Applications After Cluster Restore
- Unhealthy Services After Cluster Restore or Rollback
- Using the Automation Suite Diagnostics Tool
- Using the Automation Suite support bundle
- Exploring Logs
High Availability – three availability zones
kubernetes and uipath product services, in High Availability (HA) mode.
HA mode requires at least three server nodes deployed in three distinct availability zones.
To ensure HA with three availability zones, the following requirements must be met:
- Three availability zones that are geographically separate but within close proximity;
- Round Trip Time (RTT) among the availability zones must be minimal (<10 ms RTT);
- All availability zones must provide a consistent set of resources with HA and redundancy;
- Single virtual network span across all the availability zones.
High Availability Add-On (HAA) is required for deploying Orchestrator in a three active availability zone topology on Automation Suite.
The architecture of a configuration with HA with three availability zones has the following characteristics:
- All three zones are linked in the same virtual network;
- Each of the zones must host at least one server node so that there are at least three server nodes installed in Automation Suite to maintain the quorum requirement;
- Each of the zones should host additional balanced
number of agent nodes to meet the overall hardware requirements for running
Automation Suite.
Note:
- SQL server must be configured as failover group spanning across two zones to ensure the entire deployment is resilient to the failure of one zone.
- A minimum of three nodes are required for Elasticsearch in any of the two zones, configured in different clusters and synchronized.
- A minimum of two load balancers in any of the two zones, to ensure High Availability at load balancer level.
To ensure both HA and Disaster Recovery, you can employ the deployment model illustrated in the following image. In this example, all three zones are active, and the traffic manager is employed to use a specific algorithm, such as Round Robin or one of its variants to direct traffic to any of the load balancers. Similarly to the traffic manager, the load balancer will direct traffic to any of the availability zones.
