Automation Suite - Orchestrator-specific configuration

automation-suite

2024.10

false

Automation Suite on EKS/AKS installation guide

Orchestrator-specific configuration

Reference for Orchestrator advanced configuration options in Automation Suite, including resource overrides and deployment parameter settings.

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 cluster_config.json file to ensure configuration consistency across environments.

Important:

Any configuration changes performed directly in ArgoCD must also be replicated in cluster_config.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.yaml file 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=10
requests.cpu=10
```
This corresponds to the following JSON configuration:
```
"requests": {
  "cpu": "10"
}
"requests": {
  "cpu": "10"
}
```

Modify the cluster_config.json file.

Add an advanced_configuration section under the corresponding service in cluster_config.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": "100m",
        "storage": "1Gi",
        "gpu": 1
      },
      "limits": {
        "cpu": "200m",
        "memory": "200m",
        "storage": "2Gi",
        "gpu": 1
      }
    }
  }
}
{
  "orchestrator": {
    "advanced_configuration": {
      "requests": {
        "cpu": "100m",
        "memory": "100m",
        "storage": "1Gi",
        "gpu": 1
      },
      "limits": {
        "cpu": "200m",
        "memory": "200m",
        "storage": "2Gi",
        "gpu": 1
      }
    }
  }
}

Update autoscaling parameters (optional).

You can also override Horizontal Pod Autoscaler (HPA) parameters using the autoscaling configuration 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 cluster_config.json file.

On this page

Using advanced configuration

Was this page helpful?

PREVIOUSOrchestrator

NEXTConfiguring Orchestrator parameters

Using advanced configuration​

Was this page helpful?

Using advanced configuration