- 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 bundle
- 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 NIC 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
- 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
- Using the Automation Suite Diagnostics Tool
- Using the Automation Suite Support Bundle Tool
- Exploring Logs
Install-uipath.sh Parameters
install-uipath.sh
manual installer allows you to customize the installation experience without running the interactive installer (installUiPathAS.sh
).
While the manual installer is suitable for advanced scenario, the deployment templates and the interactive installer are still the recommended options.
install-uipath.sh
installer is available in sf-installer.zip
. For download instructions, see Downloading installation packages.
.json
file.
input.json
refers to the cluster_config.json
that defines the parameters, settings, and preferences applied to the UiPath® services deployed via Automation Suite. You
need to update this file to change the defaults and use any advanced configuration for your cluster. For details, refer to
Manual: Advanced installation experience.
-k
. Determines the type of node to be joined to an existing cluster. Allowed values: <server|agent>
.
–install-all
will be implied.
online
. You cannot set it to online
together with –offline-bundle
.
Specify the path to the offline bundle. Indicates that the installation method is tarball.
--offline-bundle
or --optional-offline-bundle
. Specify the parent directory for the temporary offline installation folder. Defaults to /tmp
.
Used with the tarball installation method, performs the installation of all prerequisites.
Skips the installation of prerequisites during the online installation method. By default, prerequisites are installed.
/etc/rancher/rke2/rke2.yaml
.
Install Cilium CNI (Container Network Interface) to replace the default Canal. Only used during upgrade. You cannot use it with any installation flag.
Specify the targeted machines for installation. Provide comma-separated IP addresses or hostnames of all the machines.
input.json
file with the current cluster configuration.
- Install the Kubernetes cluster components on the VM where it is executed, using the online installation method.
install-uipath.sh -i ./input.json -o ./output.json -k --accept-license-agreement
install-uipath.sh -i ./input.json -o ./output.json -k --accept-license-agreement - Install the Kubernetes components on the VM where it is executed, and join it to the existing cluster as a server, using the
online installation method.
install-uipath.sh -i ./input.json -o ./output.json -k -j server --accept-license-agreement
install-uipath.sh -i ./input.json -o ./output.json -k -j server --accept-license-agreement - Perform the complete installation on the current VM, using the online installation method. Includes the Kubernetes cluster
components, the Fabric, and the Uipath services.
install-uipath.sh -i ./input.json -o ./output.json -a --accept-license-agreement
install-uipath.sh -i ./input.json -o ./output.json -a --accept-license-agreement - Perform the complete installation on the current VM, using the online installation method. This time, skip the prerequisites
installation.
install-uipath.sh -i ./input.json -o ./output.json -a --skip-packages-install --accept-license-agreement
install-uipath.sh -i ./input.json -o ./output.json -a --skip-packages-install --accept-license-agreement - Perform the Kubernetes cluster installation, using the tarball installation method. Also, join the node to the existing cluster
and install all the offline prerequisites.
install-uipath.sh -i ./input.json -o ./output.json -k -j agent --offline-bundle "/tmp/sf-infra.tar.gz" --accept-license-agreement --install-offline-prereqs
install-uipath.sh -i ./input.json -o ./output.json -k -j agent --offline-bundle "/tmp/sf-infra.tar.gz" --accept-license-agreement --install-offline-prereqs - Install the fabric and services components using the offline installation method, without a temporary folder provided.
install-uipath.sh -i ./input.json -o ./output.json -f -s --offline-bundle "/tmp/sf-infra.tar.gz" --accept-license-agreement
install-uipath.sh -i ./input.json -o ./output.json -f -s --offline-bundle "/tmp/sf-infra.tar.gz" --accept-license-agreement - Execute the installer for an offline installation, but without loading the artifacts.
install-uipath.sh -i ./input.json -o ./output.json --install-type offline -s --accept-license-agreement
install-uipath.sh -i ./input.json -o ./output.json --install-type offline -s --accept-license-agreement - Execute the installer skipping the prerequisites check
install-uipath.sh -i ./input.json -o ./output.json -k --accept-license-agreement --skip-pre-reqs
install-uipath.sh -i ./input.json -o ./output.json -k --accept-license-agreement --skip-pre-reqs
- Required parameters
--input -i <string>
--output -o <string>
- Optional Parameters
--install-kubernetes -k
--join-node -j <server|agent>
--install-fabric -f
--install-services -s
--install-all -a
--install-type <online|offline>
--offline-bundle <string>
--offline-tmp-folder <string>
--optional-offline-bundle <string>
--pre-reqs -p
--install-offline-prereqs
--skip-packages-install
--upgrade -u
--kubeconfig <string>
--backup -b
--restore -r
--restore-volume
--disable-backup
-d
-h
--accept-license-agreement
-c
--skip-pre-reqs
--install-standalone-aicenter
--one-time-manual-backup
-m|--machines <comma separated machine's IP>
--compare-config
--skip-compare-config
- Examples