- Overview
- Requirements
- Pre-installation
- Preparing the installation
- Installing and configuring the service mesh
- Downloading the installation packages
- Configuring the OCI-compliant registry
- Granting installation permissions
- Installing and configuring the GitOps tool
- Deploying Redis through OperatorHub
- Applying miscellaneous configurations
- Running uipathctl
- Installation
- Post-installation
- Migration and upgrade
- Upgrading Automation Suite
- Migrating standalone products to Automation Suite
- Step 1: Restoring the standalone product database
- Step 2: Updating the schema of the restored product database
- Step 3: Moving the Identity organization data from standalone to Automation Suite
- Step 4: Backing up the platform database in Automation Suite
- Step 5: Merging organizations in Automation Suite
- Step 6: Updating the migrated product connection strings
- Step 7: Migrating standalone Orchestrator
- Step 8: Migrating standalone Insights
- Step 9: Migrating standalone Test Manager
- Step 10: Deleting the default tenant
- Performing a single tenant migration
- Migrating between Automation Suite clusters
- Monitoring and alerting
- Cluster administration
- Performing database maintenance
- Setting up Kerberos authentication
- Configuring the FQDN post-installation
- Product-specific configuration
- Orchestrator advanced configuration
- Configuring Orchestrator parameters
- Configuring appSettings
- Configuring the maximum request size
- Overriding cluster-level storage configuration
- Configuring NLog
- Saving robot logs to Elasticsearch
- Configuring credential stores
- Configuring encryption key per tenant
- Cleaning up the Orchestrator database
- Skipping host library creation
- Troubleshooting
Automation Suite on OpenShift installation guide
Configuring the FQDN post-installation
To update the FQDN of Automation Suite, you must update the input.json file and run the uipathctl installer.
Changing the FQDN requires new server certificates. If a new certificate is not available, you have two options: either continue with the new self-signed certificate configured by the installer automatically, or stop the installation and bring in a new CA-issued certificate.
You can configure the certificate via the server_certificate field in the input.json file.
The installer can configure a new certificate automatically only if it has admin privileges in the <istio-system> namespace.
If you update the FQDN post-installation, you must also take the following steps:
- Follow the instructions in the note at the end of Configuring Istio and installing the WASM plugin for routing.
- Follow the instructions in the note at the end of Installing Dapr.
Updating the config file with the new FQDN value
You must update the following parameter in the input.json file:
-
fqdn- update this field with new FQDN that you need to access the cluster.Note:We support only lowercase FQDNs. Do not use uppercase characters in your FQDN.
The following example shows the input.json configuration required to update the FQDN.
{
"fqdn": "new-automationsuite.mycompany.com" //this is the fqdn for accessing the automation suite cluster
}
{
"fqdn": "new-automationsuite.mycompany.com" //this is the fqdn for accessing the automation suite cluster
}
Updating FQDN at the components and services level
To update the FQDN, run the following command:
uipathctl manifest apply input.json --versions versions.json
uipathctl manifest apply input.json --versions versions.json
If you run the command with the --force flag, it will override the warning prompts and perform the FQDN changes directly.
The installer warns you of the consequences of updating the FQDN. It asks for confirmation before proceeding.
[WARN] You are about to change the FQDN of the Automation Suite Cluster.
Changing the fqdn is a disruptive operation, and it will result in
disconnecting your robots, mobile orchestrator users, ML Activities,
and ML Skills and invalidating any pending user invites.
If you wish to continue type 'yes' and hit enter to continue.
[WARN] You are about to change the FQDN of the Automation Suite Cluster.
Changing the fqdn is a disruptive operation, and it will result in
disconnecting your robots, mobile orchestrator users, ML Activities,
and ML Skills and invalidating any pending user invites.
If you wish to continue type 'yes' and hit enter to continue.
The installer also warns you if there is no new valid certificate related to the FQDN. If the certificate validation fails, the installer requires you to provide the new CA-issued certificate or continue with the new self-signed certificate.
************************************************************************************
[ERROR] Validating certificate... Failed
[ERROR] Certificate doesn't have new-automationsuite.mycompany.com in the SAN
************************************************************************************
Certificate provided is invalid for the new fqdn, would you like us to configure the new self signed certificate?
If you wish to continue type `yes` and hit enter to continue.
************************************************************************************
[ERROR] Validating certificate... Failed
[ERROR] Certificate doesn't have new-automationsuite.mycompany.com in the SAN
************************************************************************************
Certificate provided is invalid for the new fqdn, would you like us to configure the new self signed certificate?
If you wish to continue type `yes` and hit enter to continue.
Make sure to clear all the data from your Redis database. You can do this by running the FLUSHALL command.