A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://run-ai-docs.nvidia.com/self-hosted/infrastructure-setup/advanced-setup/control-plane-config below:

Advanced Control Plane Configurations | Run:ai Documentation

Advanced Control Plane Configurations | Run:ai Documentation
  1. Infrastructure setup
  2. Advanced Setup
Advanced Control Plane Configurations

The NVIDIA Run:ai control plane installation can be customized to support your environment via Helm values files or Helm install flags. Make sure to restart the relevant NVIDIA Run:ai pods so they can fetch the new configurations.

global.ingress.ingressClass

NVIDIA Run:ai default is using NGINX. If your cluster has a different ingress controller, you can configure the ingress class to be created by NVIDIA Run:ai

global.ingress.tlsSecretName

NVIDIA Run:ai requires the creation of a secret with domain certificate. If the runai-backend namespace already had such a secret, you can set the secret name here

Set NVIDIA Run:ai and 3rd party services' Pod Labels in a format of key/value pairs.

<service-name>resources:limits:     cpu: 500m     memory: 512Mirequests:     cpu: 250m     memory: 256Mi

Set NVIDIA Run:ai and 3rd party services' resources

disableIstioSidecarInjection.enabled

Disable Istio sidecar injection

Disable the automatic injection of Istio sidecars across the entire NVIDIA Run:ai Control Plane services.

Enables the use of a custom Certificate Authority (CA) in your deployment. When set to true, the system is configured to trust a user-provided CA certificate for secure communication.

Additional Third-Party Configurations

The NVIDIA Run:ai control plane chart includes multiple sub-charts of third-party components:

Note

Click on any component to view its chart values and configurations.

If you have opted to connect to an external PostgreSQL database, refer to the additional configurations table below. Adjust the following parameters based on your connection details:

  1. Disable PostgreSQL deployment - postgresql.enabled

  2. NVIDIA Run:ai connection details - global.postgresql.auth

  3. Grafana connection details - grafana.dbUser, grafana.dbPassword

If set to false, PostgreSQL will not be installed.

global.postgresql.auth.host

Hostname or IP address of the PostgreSQL server.

global.postgresql.auth.port

Port number on which PostgreSQL is running.

global.postgresql.auth.username

Username for connecting to PostgreSQL.

global.postgresql.auth.password

Password for the PostgreSQL user specified by global.postgresql.auth.username.

global.postgresql.auth.postgresPassword

PostgreSQL default admin password

Password for the built-in PostgreSQL superuser (postgres).

global.postgresql.auth.existingSecret

Postgres Credentials (secret)

Existing secret name with authentication credentials.

global.postgresql.auth.dbSslMode

Postgres connection SSL mode

postgresql.primary.initdb.password

PostgreSQL default admin password

Set the same password as in global.postgresql.auth.postgresPassword (if changed).

postgresql.primary.persistence.storageClass

The installation is configured to work with a specific storage class instead of the default one.

Note

This section applies to Kubernetes only.

thanos.receive.persistence.storageClass

The installation is configured to work with a specific storage class instead of the default one.

The keycloakx.adminUser can only be set during the initial installation. The admin password can be changed later through the Keycloak UI, but you must also update the keycloakx.adminPassword value in the Helm chart using helm upgrade. Failing to update the Helm values after changing the password can lead to control plane services encountering errors.

User name of the internal identity provider administrator

This user is the administrator of Keycloak.

Password of the internal identity provider administrator

This password is for the administrator of Keycloak.

Keycloakx Credentials (secret)

Existing secret name with authentication credentials.

KeyCloak (NVIDIA Run:ai internal identity provider) host path

Override the DNS for Keycloak. This can be used to access access Keycloack externally to the cluster.

grafana.db.existingSecret

Grafana database connection credentials (secret)

Existing secret name with authentication credentials.

Grafana database username

Username for accessing the Grafana database.

Grafana database password

Password for the Grafana database user.

grafana.admin.existingSecret

Grafana admin default credentials (secret)

Existing secret name with authentication credentials.

Override the NVIDIA Run:ai default user name for accessing Grafana.

Override the NVIDIA Run:ai default password for accessing Grafana.


RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4