- Overview
- Requirements
- Pre-installation
- Preparing the installation
- Downloading the installation packages
- Configuring the OCI-compliant registry
- Granting installation permissions
- Installing and configuring the service mesh
- Installing and configuring the GitOps tool
- Installing the External Secrets Operator in Kubernetes
- Applying miscellaneous configurations
- Running uipathctl
- Installation
- Post-installation
- Migration and upgrade
- Monitoring and alerting
- Cluster administration
- 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 installation
- AI Trust Layer
- Troubleshooting
- The backup setup does not work due to a failure to connect to Azure Government
- Pods in the uipath namespace stuck when enabling custom node taints
- Unable to launch Automation Hub and Apps with proxy setup
- Velero backup fails with FailedValidation error
- External Secrets troubleshooting
- Temporal as a Service troubleshooting
- AI Center and Document Understanding pods fail to start with TLS certificate verification enabled
- TLS certificate validation errors
- Fluentd does not export logs in IPv6 environments
- Studio Desktop cannot load Integration Service connectors and activities
- Manual ArgoCD NetworkPolicy mitigation (GHSA-47m3-95c7-g2g8)
- Configuring resource requests and limits for uipathctl-created workloads
Configuring appSettings
Export, edit, and update Orchestrator appSettings configuration in Automation Suite on EKS/AKS.
The Orchestrator configuration consists of an array of Kubernetes config maps and secrets that are loaded in a specific order, and placed in the appSettings section of config maps.
The latest configuration is loaded from the orchestrator-customconfig config map. Any newly loaded configuration overwrites all existing settings that have the same key.
To display the current custom Orchestrator configuration, use the config orchestrator get-config uipathctl command:
uipathctl config orchestrator get-config --app-settings
{
"key":"value"
}
uipathctl config orchestrator get-config --app-settings
{
"key":"value"
}
The uipathctl commands needed for configuring appSettings are:
uipathctl config orchestrator get-config --app-settings- Exports the current configuration in a key-value pair json file, ready for editing. For details, refer to the uipathctl config orchestrator get-config section.uipathctl config orchestrator update-config --app-settings appsettings.json- Updates the configuration with your changes. For details, refer to the uipathctl config orchestrator update-config section.
-
Export the current custom
appSettingsconfiguration to a json file using this command:uipathctl config orchestrator get-config --app-settings > appsettings.jsonuipathctl config orchestrator get-config --app-settings > appsettings.json -
Edit the exported
appsettings.jsonfile as needed. You can add, remove, or change any of its settings, as shown in the following example:{ "Triggers.DisableWhenFailedCount": "20", "Triggers.JobsCountStrategy": "NoLimit" }{ "Triggers.DisableWhenFailedCount": "20", "Triggers.JobsCountStrategy": "NoLimit" }Note:You must export the file again every time you need to make a change, since the update overwrites all settings.
-
Update the
appSettingsconfiguration using this command:uipathctl config orchestrator update-config --app-settings appsettings.json orchestrator config updateduipathctl config orchestrator update-config --app-settings appsettings.json orchestrator config updated