- Overview
- Requirements
- Installation
- Prerequisite checks
- Downloading the installation packages
- uipathctl cluster
- uipathctl cluster maintenance
- uipathctl cluster maintenance disable
- uipathctl cluster maintenance enable
- uipathctl cluster maintenance is-enabled
- uipathctl cluster migration
- uipathctl cluster migration export
- uipathctl cluster migration import
- uipathctl cluster migration run
- uipathctl cluster upgrade
- uipathctl config
- uipathctl config add-host-admin
- uipathctl config additional-ca-certificates
- uipathctl config additional-ca-certificates get
- uipathctl config additional-ca-certificates update
- uipathctl config alerts
- uipathctl config alerts add-email
- uipathctl config alerts remove-email
- uipathctl config alerts update-email
- uipathctl config argocd
- uipathctl config argocd ca-certificates
- uipathctl config argocd ca-certificates get
- uipathctl config argocd ca-certificates update
- uipathctl config argocd generate-dex-config
- uipathctl config argocd generate-rbac
- uipathctl config argocd registry
- uipathctl config argocd registry get
- uipathctl config argocd registry update
- uipathctl config enable-basic-auth
- uipathctl config orchestrator
- uipathctl config orchestrator get-config
- uipathctl config orchestrator update-config
- uipathctl config saml-certificates get
- uipathctl config saml-certificates rotate
- uipathctl config saml-certificates update
- uipathctl config tls-certificates
- uipathctl config tls-certificates get
- uipathctl config tls-certificates update
- uipathctl config token-signing-certificates
- uipathctl config token-signing-certificates get
- uipathctl config token-signing-certificates rotate
- uipathctl config token-signing-certificates update
- uipathctl health
- uipathctl health bundle
- uipathctl health check
- uipathctl health diagnose
- uipathctl health test
- uipathctl manifest
- uipathctl manifest apply
- uipathctl manifest diff
- uipathctl manifest get
- uipathctl manifest get-revision
- uipathctl manifest list-applications
- uipathctl manifest list-revisions
- uipathctl manifest render
- uipathctl prereq
- uipathctl prereq create
- uipathctl prereq run
- uipathctl resource
- uipathctl resource report
- uipathctl snapshot
- uipathctl snapshot backup
- uipathctl snapshot backup create
- uipathctl snapshot backup disable
- uipathctl snapshot backup enable
- uipathctl snapshot delete
- uipathctl snapshot list
- uipathctl snapshot restore
- uipathctl snapshot restore create
- uipathctl snapshot restore delete
- uipathctl snapshot restore history
- uipathctl snapshot restore logs
- uipathctl version
- Post-installation
- Migration and upgrade
- Upgrading Automation Suite on EKS/AKS
- 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 Orchestrator
- Step 7: Migrating standalone Insights
- Step 8: Deleting the default tenant
- B) Single tenant migration
- Migrating from Automation Suite on Linux to Automation Suite on EKS/AKS
- Monitoring and alerting
- Cluster administration
- Product-specific configuration
- Troubleshooting
Prerequisite checks
input.json
before starting the Automation Suite installation.
uipathctl prereq
command. By default, this command verifies all the prerequisites. If you want to exclude components from the execution, use
the --excluded
flag.
uipath-check
namespace. You must either allow the creation of the uipath-check
namespace or create it yourself before running the checks/tests. In addition to this, some checks/tests require that you
allow the communication between the uipath-check
and uipath
namespaces, or that you enable the use of hostNetwork
.
The checks in the following table are run on each node:
Check |
Description |
---|---|
SQL Connection |
Validates that Automation Suite can successfully connect to SQL server for UiPath® products and shared services (such as Identity,
Portal, Org Mamagement, etc.) using the SQL connection strings provided in
input.json . This is mandatory for a successful installation.
|
SQL DB roles |
Validates the necessary roles and permissions required by UiPath® products. This is mandatory for a successful installation. |
SQL DB compatibility |
Validates SQL DB compatibility requirements. |
FQDN resolution |
Validates that the FQDN and the sub-domains are successfully resolvable. |
Object Storage API |
Validates that Object store APIs are accessible based on access information provided in
input.json . This is mandatory for a successful installation of UiPath® Services.
|
Cache / Redis |
Validates the connection to Cloud Redis or ElastiCache. This is mandatory for a successful installation. |
Capacity |
Validates you have minimum worker nodes' CPU and RAM capacity based on products enabled in
input.json .
|
Storage Class |
Validates the storage classes for File Storage are configured as required for Automation Suite Robots. |
Optional Components |
Validates that your cluster has components that you chose to exclude from the Automation Suite installation. |
Ingress |
Validates that the cluster ingress is configured correctly and the FQDN URL requests can reach UiPath® products. |
Network Policies |
Checks if network policies configured in Automation Suite are compatible with the cluster. |
Registry |
Validates that Automation Suite can access the UiPath® docker registry. This is mandatory for a successful installation. |
Cluster Connectivity |
Validates whether the cluster communication is configured properly:
|