Configuring dedicated runtime pods

You configure the dedicated runtime pods in your Kubernetes deployment YAML file. You use the dedicated tag in the decisionServerRuntime section of the file.

The following example shows the configuration for dedicated runtime pods in Helm values:

decisionServerRuntime:
  replicaCount: 2  # Number of pods replicas for the default Decision Server Runtime. 
  # Other runtime configurations...
  dedicated:
    - name: miniloan  # Required - Name of the dedicated runtime
      paths:  # Required - Ruleset paths that are deployed in this runtime
        - /miniloan/1.0
        - /miniloan/2.0
      resources:  # Optional - Kubernetes resources
        requests:
          cpu: 1000m
          memory: 2048Mi
        limits:
          cpu: 2000m
          memory: 4096Mi
      replicaCount: 3  # Optional - Number of pod replicas (default: 1)
      webConfigRef: "MiniloanConfigMap"  # Optional - Custom Decision Server Runtime configuration
      xuConfigRef: "MiniloanXUConfig"    # Optional - Custom XU optimization configuration
    
    - name: loan-validation
      paths:
        - /loan-validation  # execute all the rulesets (in all versions) of the ruleapp loan-validation
      resources:
        requests:
          cpu: 500m
          memory: 1024Mi
        limits:
          cpu: 1000m
          memory: 2048Mi
      replicaCount: 2  # Optional - Number of pod replicas

Configuration parameters

Use the following parameters to configure your dedicated runtime pods:

Table 1. . The table shows the parameters for the dedicated runtime pods:
Parameter	Description	Required	Default
decisionServerRuntime.dedicated	List of dedicated runtime pod configurations	Yes	[ ]
decisionServerRuntime.dedicated[].name	Name identifier for the dedicated runtime pod configuration	Yes	N/A
decisionServerRuntime.dedicated[].paths	List of ruleset paths that are executed in this dedicated runtime	Yes	Should be the ruleset path format
decisionServerRuntime.dedicated[].replicaCount	Number of pod replicas for this dedicated runtime	No	1
decisionServerRuntime.dedicated[].resources.requests.cpu	CPU resource requests for the pod	No	500 m
decisionServerRuntime.dedicated[].resources.requests.ephemeral-storage	Ephemeral storage resource requests for the pod	No	200 Mi
decisionServerRuntime.dedicated[].resources.requests.memory	Memory resource requests for the pod	No	512 Mi
decisionServerRuntime.dedicated[].resources.limits.cpu	CPU resource limits for the pod	No	2
decisionServerRuntime.dedicated[].resources.limits.ephemeral-storage	Ephemeral storage resource requests for the pod	No	1 Gi
decisionServerRuntime.dedicated[].resources.limits.memory	Memory resource limits for the pod	No	4,096 Mi
decisionServerRuntime.dedicated[].webConfigRef	ConfigMap reference for customizing Decision Server Runtime behavior	No	If not specified in the dedicated runtime pod configuration, the value from the parent decisionServerRuntime level is used if present.
decisionServerRuntime.dedicated[].xuConfigRef	ConfigMap reference for optimizing the execution unit (XU)	No	If not specified in the dedicated runtime pod configuration, the value from the parent decisionServerRuntime level is used if present.