DIAL Admin chart configuration

The dial/dial-admin chart deploys Admin Frontend, the optional Admin Backend and database, and optional Deployment Manager. This reference describes chart 0.20.0 for platform engineers choosing the chart components and their configuration scopes. For sign-in and runtime settings, use DIAL Admin configuration.

The release's Chart.yaml, values.yaml, and parameter reference define the chart. Frontend and manager use Extension chart 3.1.1; the bundled PostgreSQL dependency is 16.7.12.

Components and defaults

Value	Default	Purpose
`frontend.enabled`	`true`	Deploy Admin Frontend.
`frontend.image.repository`, `.tag`	`epam/ai-dial-admin-frontend`, `0.22.0`	Frontend image.
`frontend.containerPorts.http`	`3000`	Frontend container port.
`frontend.resourcesPreset`	`micro`	Frontend resource preset.
`frontend.containerSecurityContext.readOnlyRootFilesystem`	`false`	Override the Extension chart's filesystem default.
`backend.enabled`	`true`	Deploy the optional Admin Backend. Disable for a Core-direct frontend-only setup.
`backend.image.repository`, `.tag`	`epam/ai-dial-admin-backend`, `0.22.1`	Backend image.
`backend.containerPorts.http`, `.metrics`	`8080`, `9464`	Backend ports.
`backend.replicaCount`	`1`	Backend replicas.
`backend.livenessProbe.enabled`, `.readinessProbe.enabled`, `.startupProbe.enabled`	`true`, `true`, `false`	Backend probes, using `/api/v1/health`.
`manager.enabled`	`false`	Deploy Deployment Manager.
`manager.image.repository`, `.tag`	`epam/ai-dial-admin-deployment-manager-backend`, `0.22.0`	Manager image.
`manager.containerPorts.http`, `manager.resourcesPreset`	`8080`, `small`	Manager port and resource preset.
`postgresql.enabled`	`true`	Deploy bundled PostgreSQL.

Other frontend/manager values follow the Extension chart; the backend has its own equivalent workload fields in the Admin chart, including resources, probes, scheduling, persistence, network policy, metrics, service account, and rbac.create. The root exposes the same global/naming/metadata values described in Configuration overview.

Core-direct frontend

For a deployment that connects Admin directly to Core, disable unused backend/database components and leave DIAL_ADMIN_API_URL unset:

backend:
  enabled: false
postgresql:
  enabled: false
manager:
  enabled: false
frontend:
  env:
    DIAL_CORE_API_URL: http://dial-core.dial.svc.cluster.local
    NEXTAUTH_URL: https://admin.example.com
    NEXTAUTH_COOKIE_PREFIX: admin
  extraEnvVarsSecret: admin-frontend-auth
  livenessProbe:
    enabled: true
    httpGet:
      path: /api/health
      port: http
  readinessProbe:
    enabled: true
    httpGet:
      path: /api/health
      port: http

The existing admin-frontend-auth Secret supplies NEXTAUTH_SECRET and the selected provider's credentials. Core must accept that provider's tokens and administrator claims. The Admin installation guide adds ingress, TLS, and the complete sign-in settings. THEMES_CONFIG_URL is the frontend's themes setting, even where older chart examples use another name.

Admin Backend and database

Value family	Purpose
`backend.env`, `.secrets`, `.extraEnvVars`, `.extraEnvVarsCM`, `.extraEnvVarsSecret`	Backend runtime configuration and credentials.
`backend.configuration.datasourceVendor`	Chart database selection: `postgresql` by default, also `mssql` or `h2`.
`backend.configuration.export.create`	`true`; grant permission to create export destinations.
`backend.configuration.export.type`	`secret`; alternative `configmap`.
`backend.configuration.export.namespace`, `.names`, `.key`	Export destination namespace, resource names, and data key.
`postgresql.auth`	Bundled database name, user, passwords, and password-file handling. Default user/database are `dial_admin`; passwords are empty in the values file.
`postgresql.primary`	PostgreSQL primary settings, including initialization scripts and service port.
`externalDatabase.host`, `.port`, `.database`, `.user`	External PostgreSQL connection when not using the bundled database; default port `5432`, database/user `dial_admin`.
`externalDatabase.password`, `.existingSecret`, `.existingSecretPasswordKey`	External database password or Secret reference; default password key `password`.

The backend's configuration export and Core's configuration loading must refer to the same destination. Chart RBAC and export-resource settings do not themselves configure Core to read that resource. See Admin Backend for application settings and Core config loading for the receiving side.

Deployment Manager

Value family	Default / purpose
`manager.configuration.build.namespace`	Empty; set the build-job namespace.
`manager.configuration.deploy.knative.enabled`, `.namespace`	`true`, empty; Knative workload support and namespace.
`manager.configuration.deploy.kserve.enabled`, `.namespace`	`false`, empty; KServe support and namespace.
`manager.configuration.deploy.nim.enabled`, `.namespace`	`false`, empty; NIM support in the bundled backend release.
`manager.configuration.database.name`, `.user`, `.password`	`deployment_manager`, `deployment_manager`, empty; manager database settings when bundled PostgreSQL is enabled.
`manager.env`, `.secrets`, `.extraEnvVarsSecret`	Backend runtime values and credentials. The default Secret name is `<release>-manager-db`.
`manager.rbac.create`, `manager.serviceAccount.create`	`true`, `true`; create the chart's RBAC and service account.

The chart maps manager namespace/enablement settings to backend environment variables. Admin Frontend still needs DEPLOYMENTS_ENABLED and DIAL_DEPLOYMENTS_API_URL. Cluster operators, kubeconfig/token credentials, provider validation, and the stdio MCP proxy settings are covered by DIAL Deployment Manager.

Warning

While postgresql.enabled and manager.enabled are both true, the chart generates the Secret named in manager.extraEnvVarsSecret, by default <release>-manager-db, with the bundled PostgreSQL credentials. A Secret of that name supplied for another database is overwritten. When the manager uses another database, set postgresql.enabled: false.

Warning

PostgreSQL initialization scripts run on first database initialization. Enabling manager on an installation with an existing PostgreSQL volume may require creating its database/user explicitly; a Helm upgrade does not rerun first-start initialization. See the chart's upgrade guidance.

Evaluation and Analytics API URLs connect Admin to separately deployed services. The chart does not install the evaluation services; see DIAL Evaluations.

Components and defaults​

Core-direct frontend​

Admin Backend and database​

Deployment Manager​

Further reading​

Components and defaults

Core-direct frontend

Admin Backend and database

Deployment Manager

Further reading