Step 14: Applying advanced configuration

The cluster_config.json file defines the parameters, settings, and preferences applied to the UiPath® products deployed via Automation Suite. You must update this file to change defaults and use any advanced configuration for your cluster.

To edit cluster_config.json, you can use either:

• a Linux text editor, such as vi or GNU nano, directly on the Linux machine via SSH (e.g., command: vi cluster_config.json);
• your favorite text editor and then copy paste the file on the machine.

The cluster_config.json file allows you to configure the UiPath® products you want to deploy. Be aware that products may have dependencies. For details, see Cross-product dependencies.

To enable or disable a products via the cluster_config.json file, use true or false for the enabled flag.

Cluster_config.json Sample

{
  "fqdn": "PLACEHOLDER",
  "cluster_fqdn": "PLACEHOLDER",
  "fixed_rke_address": "PLACEHOLDER",
  "admin_username": "PLACEHOLDER",
  "admin_password": "PLACEHOLDER",
  "rke_token": "PLACEHOLDER ",
  "zone_resilience": false,
  "registries": {
    "docker": {
      "url": "registry.uipath.com"
    },
    "helm": {
      "url": "registry.uipath.com"
    }
  },
  "sql_connection_string_template": "PLACEHOLDER",
  "sql_connection_string_template_jdbc": "PLACEHOLDER",
  "sql_connection_string_template_odbc": "PLACEHOLDER",
  "sql_connection_string_template_sqlalchemy_pyodbc": "PLACEHOLDER",
  "orchestrator": {
    "testautomation": {
      "enabled": true
    },
    "updateserver": {
      "enabled": true
    },
    "enabled": true
  },
  "infra": {
    "docker_registry": {
      "username": " PLACEHOLDER ",
      "password": " PLACEHOLDER "
    },  
     "pod_log_path": ""
  },
  "platform": {
    "enabled": true
  },
  "automation_hub": {
    "enabled": true
  },
  "automation_ops": {
    "enabled": true
  },
  "action_center": {
    "enabled": true
  },
  "aicenter": {
    "enabled": true
  },
  "documentunderstanding": {
    "enabled": true,
    "datamanager": {}
  },
  "task_mining": {
    "enabled": true
  },
  "apps": {
    "enabled": true
  },
  "test_manager": {
    "enabled": true
  },
  "insights": {
    "enabled": true
  },
  "dataservice": {
    "enabled": true
  },
  "asrobots": {
    "enabled": true,
    "packagecaching": true,
    "packagecachefolder": "/uipath_asrobots_package_cache"
  },
  "processmining": {
    "enabled": true
  },
  "external_object_storage": {
    "enabled": false
  },
  "identity_certificate": {},
  "profile": "ha",
  "telemetry_optout": false,
  "alternative_fqdn": "",
  "server_certificate": {
    "ca_cert_file": "/opt/UiPathAutomationSuite/UiPath_Installer/rootCA.crt",
    "tls_cert_file": "/opt/UiPathAutomationSuite/UiPath_Installer/server.crt",
    "tls_key_file": "/opt/UiPathAutomationSuite/UiPath_Installer/server.key"
  },
  "alternative_certificate": {
    "ca_cert_file": "/opt/UiPathAutomationSuite/UiPath_Installer/alt-rootCA.crt",
    "tls_cert_file": "/opt/UiPathAutomationSuite/UiPath_Installer/alt-server.crt",
    "tls_key_file": "/opt/UiPathAutomationSuite/UiPath_Installer/alt-server.key"
  }
}

General configuration

Mandatory parameters	Description
fqdn	The load balancer (multi-node HA-ready production mode) or machine (single-node evaluation mode) domain name.
fixed_rke_address	Fixed address used to load balance node registration and kube API requests. This should be fqdn if load balancer is configured as recommended. Otherwise FQDN of 1st Server Node. Refer to Configuring the load balancer. Can be the IP/FQDN of the first rke2 server in your setup.
multinode	Set to true when choosing a multi-node HA-ready production profile. The value of this flag is set automatically by the interactive installer. It is used for internal purposes only and should not be modified manually.
admin_username	The username that you would like to set as admin (such as: admin ) for the host organization.
admin_password	The host admin password to be set.
rke_token	Use a newly generated GUID here. This is a pre-shared, cluster-specific secret. It is needed for all the nodes joining the cluster.
profile	Sets the profile of the installation. The available profiles are: default: single-node evaluation profile. ha: multi-node HA-ready production profile. The value of this flag is set automatically by the interactive installer. It is used for internal purposes only and should not be modified manually.
infra.docker_registry.username	The username that you would like to set for the docker registry installation.
infra.docker_registry.password	The password that you would like to set for the docker registry installation.

Optional parameters	Description
telemetry_optout	true or false - used to opt-out of sending telemetry back to UiPath. It is set to false by default. If you wish to opt out, then set to true.
infra.pod_log_path	Enables you to change the /var/log/pods default path of the pod logs to a custom path of your choice. Note: Updating the log path discards the logs of the existing container from /var/log/pods.

ArgoCD configuration

To enable SSO for ArgoCD, update the following parameters in the cluster_config.json file:

Keys	Value
fabric.argocd_dex_config_file	The path to the Dex configuration file.
fabric.argocd_rbac_config_file	The path to the RBAC file.

The following example shows how you can use add these parameters in the cluster_config.json file:

{
  "fabric": {
    "argocd_dex_config_file": "/path/to/file.yaml",
    "argocd_rbac_config_file": "/path/to/file.yaml"
  }
}