- Overview
- Requirements
- Installation
- Post-installation
- Cluster administration
- Managing products
- Managing the cluster in ArgoCD
- Setting up the external NFS server
- Automated: Enabling the Backup on the Cluster
- Automated: Disabling the Backup on the Cluster
- Automated, Online: Restoring the Cluster
- Automated, Offline: Restoring the Cluster
- Manual: Enabling the Backup on the Cluster
- Manual: Disabling the Backup on the Cluster
- Manual, Online: Restoring the Cluster
- Manual, Offline: Restoring the Cluster
- Additional configuration
- Migrating objectstore from persistent volume to raw disks
- 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
- B) 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
- Automation Suite not working after OS upgrade
- Automation Suite Requires Backlog_wait_time to Be Set 1
- Volume unable to mount due to not being ready for workloads
- RKE2 fails during installation and upgrade
- Failure to upload or download data in objectstore
- PVC resize does not heal Ceph
- 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
- Cannot Log in 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 With Error: An Invalid Status Code Was Supplied (Client's Credentials Have Been Revoked).
- Alarm Received for Failed Kerberos-tgt-update Job
- SSPI Provider: Server Not Found in Kerberos Database
- Login Failed for User <ADDOMAIN><aduser>. Reason: The Account Is Disabled.
- 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
- After the Initial Install, ArgoCD App Went Into Progressing State
- MongoDB pods in CrashLoopBackOff or pending PVC provisioning after deletion
- Unexpected Inconsistency; Run Fsck Manually
- Degraded MongoDB or Business Applications After Cluster Restore
- Missing Self-heal-operator and Sf-k8-utils Repo
- Unhealthy Services After Cluster Restore or Rollback
- RabbitMQ pod stuck in CrashLoopBackOff
- 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
Configuring the load balancer
A load balancer is mandatory for the multi-node HA-ready production setup.
Automation Suite supports two types of configuration for the load balancer, as shown in the following sections.
You can configure the load balancer to use session persistence or sticky sessions, but it is not a requirement.
Currently, Automation Suite supports only a Layer 4 (network layer) load balancer.
The load balancer does not support TLS encryption and termination. For effective service operation, make sure to configure your load balancer to facilitate traffic pass-through.
If you are using the Azure Internal Load Balancer (LB) for deployments, you can encounter issues with the calls from the backend Virtual Machine (VM) to the LB frontend IP. The issues occur due to source IP and MAC address mismatch of the network packet. This prevents the recipient from working out the correct response path, resulting in the failure of calls from the VM to the LB. For more details, see Azure Load Balancer Components limitations and Backend Traffic Troubleshooting.
This is the recommended configuration for the load balancer.
You need to create two backend pools that meet the following requirements:
-
Server Pool
- Consists of all the server nodes.
- There must not be any agent nodes in the Server Pool.
-
Node Pool
-
Consists of all the server nodes and agent nodes.
-
|
Probe |
Protocol |
Port |
Interval |
Re-entry threshold |
Associate pool |
|---|---|---|---|---|---|
|
|
TCP |
|
15 sec |
2 |
Node Pool |
|
|
TCP |
|
15 sec |
2 |
Server Pool |
Refer to the following illustration for more details on the configuration
Ensure you have the following ports enabled on your firewall for the source of load balancer:
|
Port |
Protocol |
Purpose |
Traffic forwarding |
Health probe |
|---|---|---|---|---|
|
|
TCP |
For HTTPS (accessing Automation Suite) |
Traffic on this port should be forwarded to Node Pool. |
|
|
|
TCP |
For accessing Kube API using HTTPS; required for node joining. |
Traffic on this port should be forwarded to Server Pool. |
|
|
|
TCP |
For accessing Kube API using HTTPS; required for node joining. |
Traffic on this port should be forwarded to Server Pool. |
|
For any ports other than HTTPS, we recommend it is not exposed outside the cluster. Run your nodes behind a firewall / security group.
If you have a firewall setup in the network, make sure that it has these ports open to allow traffic from those ports.
Refer to the following illustration for more details on the configuration.
This configuration does not have resilience to nodes going down during installation.
If the primary server is down or deleted, cluster configuration needs to be updated.
FQDN of the primary server needs to be remapped to a different machine in the cluster that is available.
Ensure that you have the following ports enabled on your firewall for the source of load balancer:
|
Port |
Protocol |
Purpose |
Traffic forwarding |
|---|---|---|---|
|
|
TCP |
For HTTPS (accessing Automation Suite). |
Traffic on this port should be forwarded to the Node Pool. |
