Advanced Control Plane Configurations

Use this page to customize the NVIDIA Run:ai control plane beyond the default installation settings.

The settings on this page use NVIDIA Run:ai control plane Helm chart values. You can provide the same values through either installation path:

• Manual Helm - Set the values in a Helm values file or pass them as Helm flags.
• Guided Installation - Set the same values under controlPlane.customHelmValues in config.yaml. See controlPlane.

Helm Chart Values

The following Helm chart values can be used to customize the control plane for your environment. After changing a value, restart the relevant NVIDIA Run:ai pods so they can load the updated configuration.

Email Notifications Configuration

To enable and manage outbound email notifications for the NVIDIA Run:ai platform, configure the following values under the notificationsService.config.sinks.runai-email section in your Helm values. These settings are used both for workload-related notifications and for system messages from NVIDIA Run:ai. All parameters can be set in your values.yaml file during Helm deployment or via Helm upgrade.

Example Configuration

notificationsService:
  config:
    sinks:
      runai-email:
        type: email
        smtp_host: my.smtp.host
        smtp_port: 587
        user: smtp_user
        password: smtp_password
        smtp_tls_enabled: true
        from_display_name: NVIDIA Run:ai
        from: notifications@my.domain
        direct_notifications: true
        logo_url: https://s3.amazonaws.com/www.run.ai/nvidia_runai_logo_new.png
        auth_type: auth_login

Third-Party Services

The NVIDIA Run:ai control plane bundles third-party services it depends on - Keycloak for authentication, PostgreSQL as its database, and Thanos for metrics storage - and deploys them for you by default. This section covers tuning those built-in deployments and rotating their credentials. For what each service does, supported versions, and replacing one with an externally managed instance instead, see Third-Party Services.

Keycloak

Keycloak provides authentication and identity management for the NVIDIA Run:ai control plane. The Helm chart uses Keycloakx (keycloakx).

Changing the Keycloak Admin Password

1. Open the Keycloak UI at: https://<runai-domain>/auth
2. Sign in with your existing admin credentials
3. Go to Users and select admin (or your admin username)
4. Open Credentials and select Reset password
5. Set the new password and click Save
6. Run helm upgrade and set keycloakx.adminPassword to the new password

PostgreSQL

PostgreSQL is the centralized database for the NVIDIA Run:ai control plane, deployed as part of the control plane Helm chart using Bitnami PostgreSQL (postgresql).

The following values tune the built-in PostgreSQL deployment:

Changing PostgreSQL Passwords

1. Connect to the PostgreSQL pod:

   kubectl exec -it runai-backend-postgresql-0 -n runai-backend -- bash
   psql -U postgres

2. Update the passwords:

   ALTER USER "postgres" WITH PASSWORD '<new-postgres-password>';
   ALTER USER "user" WITH PASSWORD '<new-user-password>';

3. Find the Kubernetes secret (default name: runai-backend-gen-postgresql) and update it with the new base64-encoded passwords. The keys are typically postgres-password and password.

4. Restart all deployments to apply the changes:

   kubectl rollout restart deployment -n runai-backend

Thanos

Thanos provides long-term metrics storage for the NVIDIA Run:ai control plane, deployed using Bitnami Thanos (thanos).