- 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
Orchestrator advanced configuration
Advanced configuration options for Orchestrator in Automation Suite on EKS/AKS.
Advanced configuration allows support engineers to override specific service configuration parameters used during Automation Suite installation and deployment.
Using advanced configuration, you can:
- Override resource requests and limits for deployments, stateful sets, and daemon sets.
- Modify Horizontal Pod Autoscaler (HPA) settings.
- Override specific Helm chart parameters used by services during installation.
All advanced configuration changes must be defined in the input.json file to ensure configuration consistency across environments.
Any configuration changes performed directly in ArgoCD must also be replicated in input.json.
If the installer is re-run, changes made only in ArgoCD may be overwritten.
Using advanced configuration
-
Identify the parameters you want to override.
You can locate these parameters in one of the following places:
- The
values.yamlfile in the service Helm chart within the service-fabric-packaging repository. - The Parameters section of the corresponding application in ArgoCD.
Example
If the following parameter appears in the ArgoCD Parameters section:
requests.cpu=10requests.cpu=10This corresponds to the following JSON configuration:
"requests": { "cpu": "10" }"requests": { "cpu": "10" } - The
-
Modify the
input.jsonfile.Add an
advanced_configurationsection under the corresponding service ininput.json. Convert the parameter format from YAML to JSON before adding it to the file.The following example overrides resource parameters for the Orchestrator service:
{ "orchestrator": { "advanced_configuration": { "requests": { "cpu": "100m", "memory": "100Mi", "storage": "1Gi", "gpu": 1 }, "limits": { "cpu": "200m", "memory": "200Mi", "storage": "2Gi", "gpu": 1 } } } }{ "orchestrator": { "advanced_configuration": { "requests": { "cpu": "100m", "memory": "100Mi", "storage": "1Gi", "gpu": 1 }, "limits": { "cpu": "200m", "memory": "200Mi", "storage": "2Gi", "gpu": 1 } } } } -
Update autoscaling parameters (optional).
You can also override Horizontal Pod Autoscaler (HPA) parameters using the
autoscalingconfiguration block.{ "orchestrator": { "advanced_configuration": { "autoscaling": { "minReplicas": 1, "maxReplicas": 3, "targetCPUUtilizationPercentage": 70, "targetMemoryUtilizationPercentage": 70, "scaleUpStabilizationWindowSeconds": 60, "scaleUp": { "policy": { "type": "Pods", "value": 1, "periodSeconds": 60 } }, "scaleDownStabilizationWindowSeconds": 60, "scaleDown": { "policy": { "type": "Pods", "value": 1, "periodSeconds": 60 } } } } } }{ "orchestrator": { "advanced_configuration": { "autoscaling": { "minReplicas": 1, "maxReplicas": 3, "targetCPUUtilizationPercentage": 70, "targetMemoryUtilizationPercentage": 70, "scaleUpStabilizationWindowSeconds": 60, "scaleUp": { "policy": { "type": "Pods", "value": 1, "periodSeconds": 60 } }, "scaleDownStabilizationWindowSeconds": 60, "scaleDown": { "policy": { "type": "Pods", "value": 1, "periodSeconds": 60 } } } } } } -
Validate the changes.
Before applying the configuration through the installer, you can optionally validate the parameters. To do this:
- Modify the parameters directly in the ArgoCD application under the Parameters section.
- Confirm the configuration behaves as expected.
- Copy the validated configuration into the
input.jsonfile.