DIAL platform chart configuration
The dial/dial chart installs a selected set of DIAL services in one Helm release. This reference describes chart 8.1.0, its dependency aliases, and the settings inherited from the child charts. It is for platform engineers preparing an assembly values file.
Dependencies and images
The 8.1.0 Chart.yaml pins Core chart 6.0.0 and Extension chart 3.1.1. The assembly values override their images:
| Alias | Enabled by default | Image tag | Child chart |
|---|---|---|---|
core | true | epam/ai-dial-core:0.49.2 | dial-core |
chat | true | epam/ai-dial-chat:1.2.4 | dial-extension |
themes | true | epam/ai-dial-chat-themes:0.21.0 | dial-extension |
openai | false | epam/ai-dial-adapter-openai:0.45.0 | dial-extension |
bedrock | false | epam/ai-dial-adapter-bedrock:0.45.0 | dial-extension |
vertexai | false | epam/ai-dial-adapter-vertexai:0.41.1 | dial-extension |
dial | false | epam/ai-dial-adapter-dial:0.20.0 | dial-extension |
The last alias is the DIAL-to-DIAL adapter, not the parent chart itself. extraDeploy accepts additional manifests at the assembly level. Bitnami common is a template-library dependency.
Values below an alias
| Value family | Purpose |
|---|---|
<alias>.enabled | Include or omit that dependency. |
<alias>.image | Override registry/repository/tag/digest and pull settings. |
<alias>.env, .secrets, .extraEnvVars, .extraEnvVarsSecret, .extraEnvVarsCM | Supply service-specific configuration. |
<alias>.service, .containerPorts, .ingress, .httpRoute | Configure internal service ports and external routing. |
<alias>.resources, .replicaCount, .autoscaling.hpa, .pdb | Resource allocation, scaling, and disruption controls. |
<alias>.livenessProbe, .readinessProbe, .startupProbe | Workload health checks. The assembly enables liveness/readiness on its services. |
core.configuration, core.valkey, core.persistence, core.logger | Core-specific encryption, cache, file storage, and log shipping. See Core chart. |
An enabled adapter must also receive its provider credentials and have model entries registered in Core. Enabling its pod alone does not create a usable model. See OpenAI, Bedrock, and Vertex AI for runtime settings.
Note
The
openai,bedrock, andvertexaialiases deploy the standalone adapters, which will be deprecated. DIAL Model Provider replaces them, and chart 8.1.0 has no alias for it. Deploy it with the Extension chart.
core:
valkey:
enabled: false
env:
aidial.redis.singleServerConfig.address: redis://<CACHE_HOST>:6379
extraEnvVarsSecret: core-runtime-secrets
chat:
env:
DIAL_CORE_URL: http://dial-core.dial.svc.cluster.local
extraEnvVarsSecret: chat-auth-secrets
openai:
enabled: true
env:
DIAL_URL: http://dial-core.dial.svc.cluster.local
This fragment illustrates alias scope in a Helm release named dial in namespace dial; it assumes existing configuration and authentication Secrets. The generated Service name can change with naming overrides. Complete installation examples are linked below.
Application build and execution services
The chart 8.1.0 dependency list has no alias for App Controller, App Builder Python, Code Interpreter, or Quick Apps; see the released Chart.yaml.
- App Controller needs a separate deployment with Kubernetes access, a registry, and Knative for Code Apps.
- App Builder Python is the preparation image selected by the controller's build Job, rather than a long-running chart dependency.
- Code Interpreter is a session image selected in Core settings. Core and the controller create its workloads on demand.
Core runtime settings can be supplied through the Core chart. The controller configuration and interpreter configuration describe the required connections and deployment boundaries.
Provider examples
The release includes example values for AWS, Azure, GCP, and generic Kubernetes. Cloud examples distinguish simple and complete deployments. The generic complete directory is a placeholder; use its simple example and the generic Kubernetes guide.
Simple examples are starting points for evaluation; configure sign-in, encryption, durable storage, cache access, and provider credentials for the target environment. The guide for each cloud remains under Operating DIAL.
Further reading
- Core chart — values below
core - Extension chart — values below Chat, themes, and adapter aliases
- Deploy DIAL on a generic Kubernetes cluster — deploy DIAL to any Kubernetes cluster
- DIAL App Controller configuration — App Controller settings for Kubernetes, registries, and timeouts
- DIAL Code Interpreter configuration — settings that enable Python calculations for agents