Configuring the FQDN post-installation

Update FQDN of Automation Suite post-installation on OpenShift with certificate validation and maintenance mode.

To update the FQDN of Automation Suite, you must update the input.json file and run the uipathctl installer.

Note:

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 the Automation Suite installer is not granted admin privileges, you must follow the instructions in the note at the end of Configuring Istio and installing the WASM plugin for routing before proceeding with the following steps.

Updating the config file with the new FQDN value

Note:

We support only lowercase FQDNs. Do not use uppercase characters in your FQDN.

In the input.json file, update the fqdn parameter with the new FQDN used to access the cluster.

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
   
}

Updating FQDN at the components and services level

Step 1: Enabling maintenance mode

Before triggering the FQDN update, you must enable maintenance mode. This shuts down the ingress controller and all the UiPath® services, blocking all the incoming traffic to the Automation Suite cluster.

To put the cluster in maintenance mode, run:

uipathctl cluster maintenance enable

To verify that the cluster is in maintenance mode, run:

uipathctl cluster maintenance is-enabled

Step 2: Updating FQDN at the components and services level

To update the FQDN, run the following command:

uipathctl manifest apply input.json --versions versions.json

Note:

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.

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.

Note:

Make sure to clear all the data from your Redis database. You can do this by running the FLUSHALL command.

Step 3: Disabling maintenance mode

After updating the FQDN, disable maintenance mode to restore traffic to the Automation Suite cluster.

To disable maintenance mode, run:

uipathctl cluster maintenance disable

For details, refer to uipathctl cluster maintenance disable.