Skip to main content

pharia-ai

Version: 0.3.101

PhariaAI Helm Chart

This document provides an overview of the chart dependencies and configurable Helm chart values for PhariaAI. It covers global configurations, detailed dependency settings, image pull credentials, PostgreSQL settings, and resource management options, offering a comprehensive guide for deploying and customizing PhariaAI.

Requirements

RepositoryNameVersion
oci://alephalpha.jfrog.io/helm/assistantpharia-assistant0.5.56
oci://alephalpha.jfrog.io/helm/assistantpharia-assistant-api0.7.9
oci://alephalpha.jfrog.io/helmdocument-index0.18.0
oci://alephalpha.jfrog.io/helminference-api0.3.4
oci://alephalpha.jfrog.io/helminference-worker0.1.10
oci://alephalpha.jfrog.io/helmpharia-iam0.8.2
oci://alephalpha.jfrog.io/helmpharia-kernel0.1.7
oci://alephalpha.jfrog.io/helm/pharia-studiopharia-studio-api0.10.0
oci://alephalpha.jfrog.io/helm/pharia-studiopharia-studio-ui0.10.0
oci://alephalpha.jfrog.io/helmpharia-translate0.3.3
oci://alephalpha.jfrog.io/helm/phariaosphariaos-manager0.5.9
oci://alephalpha.jfrog.io/helm/phariaosphariaos-ui0.5.0
oci://alephalpha.jfrog.io/pharia-data-helmpharia-data-api0.6.2

Values

Global

KeyTypeDefaultDescription
global.imagePullSecretNamestring"jfrog-docker-registry"Default PhariaAI Secret name to pull images from Aleph Alpha artifactory. Override name for existing image pull secret if required
global.inference.enabledbooltrueActivate deployment of Pharia AA inference stack (inference-api, inference-worker)
global.ingressobject{"additionalAnnotations":{},"ingressClassName":"nginx","ingressDomain":"pharia-ai.local"}Domain for external access / ingress to Pharia AI services via {service}.{domain} e.g. {service}.pharia-ai.example.com Global config for all ingress resources
global.ingress.additionalAnnotationsobject{}Additional annotations globally defined for all ingress-resources. This can be used to add ingress controller specific annotations.
global.ingress.ingressClassNamestring"nginx"The ingressClassName globally defined for all ingress resources. See also: https://kubernetes.io/docs/concepts/services-networking/ingress/#the-ingress-resource
global.ingress.ingressDomainstring"pharia-ai.local"Domain for external access / ingress to Pharia AI services via {service}.{domain} e.g. {service}.pharia-ai.example.com
global.phariaAIConfigMapstring"pharia-ai-config"Default PhariaAI ConfigMap for setting environment variables
global.registryCredentialsSecretNamestring"jfrog-docker-registry-credentials"Default PhariaAI Secret name for accessing Aleph Alpha artifactory. Override name for existing image pull secret if required
global.servicesSecretRefstring"inference-api-services"

General

KeyTypeDefaultDescription
imagePullCredentials.passwordstring""Password to login into artifactory registry
imagePullCredentials.registrystring"alephalpha.jfrog.io"Aleph Alpha artifactory registry
imagePullCredentials.usernamestring""Username to login into artifactory registry

Sub charts

pharia-assistant

KeyTypeDefaultDescription
pharia-assistant-api.databaseConfig.externalobject{"databaseName":"","existingSecret":"","host":"","password":"","port":"","user":""}Provide an existing database if you want to use an external database
pharia-assistant-api.databaseConfig.external.databaseNamestring""The name of the database
pharia-assistant-api.databaseConfig.external.existingSecretstring""Set this value if a k8s Secret with PostgreSQL values already exists. Make sure that the all the keys exists in the secret with a valid value.
pharia-assistant-api.databaseConfig.external.hoststring""The host of the database
pharia-assistant-api.databaseConfig.external.passwordstring""The password of the database
pharia-assistant-api.databaseConfig.external.portstring""The port of the database
pharia-assistant-api.databaseConfig.external.userstring""The user of the database
pharia-assistant-api.databaseConfig.secretKeys.databaseNameKeystring"databaseName"The key in the secret that contains the database name
pharia-assistant-api.databaseConfig.secretKeys.hostKeystring"host"The key in the secret that contains the host of the database
pharia-assistant-api.databaseConfig.secretKeys.passwordKeystring"password"The key in the secret that contains the password of the database
pharia-assistant-api.databaseConfig.secretKeys.portKeystring"port"The key in the secret that contains the port of the database
pharia-assistant-api.databaseConfig.secretKeys.userKeystring"user"The key in the secret that contains the user of the database
pharia-assistant-api.enabledbooltrueSet this to true to install the pharia-assistant-api subchart as a dependency
pharia-assistant-api.env.APPLICATION_NAMEstring"Assistant"The name of the application to be displayed in the top bar
pharia-assistant-api.existingSecretstring""The name of a secret containing the API token used by the pharia-assistant-api for sending requests to the inference. This allows to connect the pharia-assistant-api to an externally running inference. The secret must contain the field apiToken. It can either be pre-existing or the chart creates it for you with the value defined in 'pharia-assistant-api.secret'. This can be left undefined if the pharia-assistant-api is connected to the internal inference (deployed through this helm-chart). In that case define 'global.servicesSecretRef' instead.
pharia-assistant-api.faviconobject{"png":"","svg":"PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIGhlaWdodD0iNzgiIHdpZHRoPSI3OCIgdmlld0JveD0iMjQgMjQgMTAyIDEwMiI+CiAgPHN0eWxlPgogICAgQG1lZGlhIChwcmVmZXJzLWNvbG9yLXNjaGVtZTpkYXJrKXtwYXRoe2ZpbGw6I2ZmZn19CiAgPC9zdHlsZT4KICA8cGF0aCBkPSJtMzQuNjcgMTA2LjQzLTUuNTUtMTMuNTVBMTkuMTQgMTkuMTQgMCAwIDAgMjkgNTcuNDJsNS40Ny0xMy41OWEzMy43OCAzMy43OCAwIDAgMSAuMiA2Mi42Wm0yMi45MyAxNy4xMi04LjY4LTExLjhhNDUuMjggNDUuMjggMCAwIDAgOC42MS04LjI3TDY5IDExMi42MmE1OS44MiA1OS44MiAwIDAgMS0xMS40IDEwLjkzWiIvPgogIDxwYXRoIGQ9Ik04Mi4yMyA3NS4xN2E2MC4zNyA2MC4zNyAwIDAgMC0yNC42NC00OC4zOWwtOC42OCAxMS44MWE0NS42MyA0NS42MyAwIDAgMSAxOC42OCAzNi41OCA2MC4yOCA2MC4yOCAwIDAgMCAyNC40OCA0OC4zOGw4LjY4LTExLjhhNDUuNiA0NS42IDAgMCAxLTE4LjUyLTM2LjU4Wm05Ljg1LTI4LjIzLTExLjQ3LTkuMTJhNjAuMTQgNjAuMTQgMCAwIDEgMTEuOTQtMTEuMzdsOC41NiAxMS44OGE0NS41IDQ1LjUgMCAwIDAtOS4wMyA4LjYxWk0xMTUgMTA2LjUyYTM0LjMyIDM0LjMyIDAgMCAxLS4yOS02Mi41Mmw2LjEgMTMuMzJhMTkuNjggMTkuNjggMCAwIDAgLjE5IDM1LjgzWiIvPgo8L3N2Zz4K"}The favicon used in the assistant can be customized by providing the contents of a logo.svg or logo.png file as a base64 encoded string. This can be created by executing cat favicon.svg | base64 in a terminal. The svg value takes precedence over the png value
pharia-assistant-api.favicon.pngstring""The base64 encoded favicon.png
pharia-assistant-api.favicon.svgstring"PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIGhlaWdodD0iNzgiIHdpZHRoPSI3OCIgdmlld0JveD0iMjQgMjQgMTAyIDEwMiI+CiAgPHN0eWxlPgogICAgQG1lZGlhIChwcmVmZXJzLWNvbG9yLXNjaGVtZTpkYXJrKXtwYXRoe2ZpbGw6I2ZmZn19CiAgPC9zdHlsZT4KICA8cGF0aCBkPSJtMzQuNjcgMTA2LjQzLTUuNTUtMTMuNTVBMTkuMTQgMTkuMTQgMCAwIDAgMjkgNTcuNDJsNS40Ny0xMy41OWEzMy43OCAzMy43OCAwIDAgMSAuMiA2Mi42Wm0yMi45MyAxNy4xMi04LjY4LTExLjhhNDUuMjggNDUuMjggMCAwIDAgOC42MS04LjI3TDY5IDExMi42MmE1OS44MiA1OS44MiAwIDAgMS0xMS40IDEwLjkzWiIvPgogIDxwYXRoIGQ9Ik04Mi4yMyA3NS4xN2E2MC4zNyA2MC4zNyAwIDAgMC0yNC42NC00OC4zOWwtOC42OCAxMS44MWE0NS42MyA0NS42MyAwIDAgMSAxOC42OCAzNi41OCA2MC4yOCA2MC4yOCAwIDAgMCAyNC40OCA0OC4zOGw4LjY4LTExLjhhNDUuNiA0NS42IDAgMCAxLTE4LjUyLTM2LjU4Wm05Ljg1LTI4LjIzLTExLjQ3LTkuMTJhNjAuMTQgNjAuMTQgMCAwIDEgMTEuOTQtMTEuMzdsOC41NiAxMS44OGE0NS41IDQ1LjUgMCAwIDAtOS4wMyA4LjYxWk0xMTUgMTA2LjUyYTM0LjMyIDM0LjMyIDAgMCAxLS4yOS02Mi41Mmw2LjEgMTMuMzJhMTkuNjggMTkuNjggMCAwIDAgLjE5IDM1LjgzWiIvPgo8L3N2Zz4K"The base64 encoded favicon.svg
pharia-assistant-api.featureFlagsobject{"enableQa":true,"enableSummarize":true,"enableTranscribe":true,"enableTranslate":true,"enableUsecases":true}Feature flags for pharia-assistant-api
pharia-assistant-api.featureFlags.enableQabooltrueEnable QA feature
pharia-assistant-api.featureFlags.enableSummarizebooltrueEnable summarize feature
pharia-assistant-api.featureFlags.enableTranscribebooltrueEnable transcribe feature
pharia-assistant-api.featureFlags.enableTranslatebooltrueEnable translate feature
pharia-assistant-api.featureFlags.enableUsecasesbooltrueEnable usecases feature
pharia-assistant-api.fullnameOverridestring"pharia-assistant-api"Override for the full name of pharia-assistant-api
pharia-assistant-api.logoobject{"png":"","svg":"PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIGhlaWdodD0iNzgiIHdpZHRoPSI3OCIgdmlld0JveD0iMjQgMjQgMTAyIDEwMiI+CiAgPHBhdGggZD0ibTM0LjY3IDEwNi40My01LjU1LTEzLjU1QTE5LjE0IDE5LjE0IDAgMCAwIDI5IDU3LjQybDUuNDctMTMuNTlhMzMuNzggMzMuNzggMCAwIDEgLjIgNjIuNlptMjIuOTMgMTcuMTItOC42OC0xMS44YTQ1LjI4IDQ1LjI4IDAgMCAwIDguNjEtOC4yN0w2OSAxMTIuNjJhNTkuODIgNTkuODIgMCAwIDEtMTEuNCAxMC45M1oiIC8+CiAgPHBhdGggZD0iTTgyLjIzIDc1LjE3YTYwLjM3IDYwLjM3IDAgMCAwLTI0LjY0LTQ4LjM5bC04LjY4IDExLjgxYTQ1LjYzIDQ1LjYzIDAgMCAxIDE4LjY4IDM2LjU4IDYwLjI4IDYwLjI4IDAgMCAwIDI0LjQ4IDQ4LjM4bDguNjgtMTEuOGE0NS42IDQ1LjYgMCAwIDEtMTguNTItMzYuNThabTkuODUtMjguMjMtMTEuNDctOS4xMmE2MC4xNCA2MC4xNCAwIDAgMSAxMS45NC0xMS4zN2w4LjU2IDExLjg4YTQ1LjUgNDUuNSAwIDAgMC05LjAzIDguNjFaTTExNSAxMDYuNTJhMzQuMzIgMzQuMzIgMCAwIDEtLjI5LTYyLjUybDYuMSAxMy4zMmExOS42OCAxOS42OCAwIDAgMCAuMTkgMzUuODNaIiAvPgo8L3N2Zz4K"}The logo used in the assistant can be customized by providing the contents of a logo.svg or logo.png file as a base64 encoded string. This can be created by executing cat logo.svg | base64 in a terminal. The svg value takes precedence over the png value
pharia-assistant-api.logo.pngstring""The base64 encoded logo.png
pharia-assistant-api.logo.svgstring"PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIGhlaWdodD0iNzgiIHdpZHRoPSI3OCIgdmlld0JveD0iMjQgMjQgMTAyIDEwMiI+CiAgPHBhdGggZD0ibTM0LjY3IDEwNi40My01LjU1LTEzLjU1QTE5LjE0IDE5LjE0IDAgMCAwIDI5IDU3LjQybDUuNDctMTMuNTlhMzMuNzggMzMuNzggMCAwIDEgLjIgNjIuNlptMjIuOTMgMTcuMTItOC42OC0xMS44YTQ1LjI4IDQ1LjI4IDAgMCAwIDguNjEtOC4yN0w2OSAxMTIuNjJhNTkuODIgNTkuODIgMCAwIDEtMTEuNCAxMC45M1oiIC8+CiAgPHBhdGggZD0iTTgyLjIzIDc1LjE3YTYwLjM3IDYwLjM3IDAgMCAwLTI0LjY0LTQ4LjM5bC04LjY4IDExLjgxYTQ1LjYzIDQ1LjYzIDAgMCAxIDE4LjY4IDM2LjU4IDYwLjI4IDYwLjI4IDAgMCAwIDI0LjQ4IDQ4LjM4bDguNjgtMTEuOGE0NS42IDQ1LjYgMCAwIDEtMTguNTItMzYuNThabTkuODUtMjguMjMtMTEuNDctOS4xMmE2MC4xNCA2MC4xNCAwIDAgMSAxMS45NC0xMS4zN2w4LjU2IDExLjg4YTQ1LjUgNDUuNSAwIDAgMC05LjAzIDguNjFaTTExNSAxMDYuNTJhMzQuMzIgMzQuMzIgMCAwIDEtLjI5LTYyLjUybDYuMSAxMy4zMmExOS42OCAxOS42OCAwIDAgMCAuMTkgMzUuODNaIiAvPgo8L3N2Zz4K"The base64 encoded logo.svg
pharia-assistant-api.postgresql.enabledbooltrueThis is used to indicate whether the internal PostgreSQL should be used or not.
pharia-assistant-api.resources.limits.cpustring"1000m"
pharia-assistant-api.resources.limits.memorystring"8Gi"
pharia-assistant-api.resources.requests.cpustring"500m"
pharia-assistant-api.resources.requests.memorystring"8Gi"
pharia-assistant-api.secretobject{"apiToken":""}Allows to populate the secret identified by 'pharia-assistant-api.existingSecret' through this helm-chart. The secret must contain the field apiToken. See 'pharia-assistant-api.existingSecret' for more information.
enabledbooltrueSet this to true to install the phariaos-assistant subchart as a dependency
fullnameOverridestring"pharia-assistant"Override for the full name of pharia-assistant
ingress.annotationsobject{}Annotations for the ingress-resource. This can be used to add ingress controller specific annotations.
ingress.enabledbooltrueEnabled ingress creation
ingress.hostnamestring"assistant"Hostname for the ingress (without domain). The domain is read from global.ingress.ingressDomain. This needs to be changed, if multiple instances are deployed to the same cluster using the same domain.
ingress.tls.enabledboolfalseEnable TLS configuration for this Ingress
ingress.tls.secretNamestring"pharia-assistant-tls"The name of the secret containing the TLS certificate. See also: https://kubernetes.io/docs/concepts/services-networking/ingress/#tls
resources.limits.cpustring"500m"
resources.limits.memorystring"256Mi"
resources.requests.cpustring"100m"
resources.requests.memorystring"256Mi"

pharia-assistant-api

KeyTypeDefaultDescription
databaseConfig.externalobject{"databaseName":"","existingSecret":"","host":"","password":"","port":"","user":""}Provide an existing database if you want to use an external database
databaseConfig.external.databaseNamestring""The name of the database
databaseConfig.external.existingSecretstring""Set this value if a k8s Secret with PostgreSQL values already exists. Make sure that the all the keys exists in the secret with a valid value.
databaseConfig.external.hoststring""The host of the database
databaseConfig.external.passwordstring""The password of the database
databaseConfig.external.portstring""The port of the database
databaseConfig.external.userstring""The user of the database
databaseConfig.secretKeys.databaseNameKeystring"databaseName"The key in the secret that contains the database name
databaseConfig.secretKeys.hostKeystring"host"The key in the secret that contains the host of the database
databaseConfig.secretKeys.passwordKeystring"password"The key in the secret that contains the password of the database
databaseConfig.secretKeys.portKeystring"port"The key in the secret that contains the port of the database
databaseConfig.secretKeys.userKeystring"user"The key in the secret that contains the user of the database
enabledbooltrueSet this to true to install the pharia-assistant-api subchart as a dependency
env.APPLICATION_NAMEstring"Assistant"The name of the application to be displayed in the top bar
existingSecretstring""The name of a secret containing the API token used by the pharia-assistant-api for sending requests to the inference. This allows to connect the pharia-assistant-api to an externally running inference. The secret must contain the field apiToken. It can either be pre-existing or the chart creates it for you with the value defined in 'pharia-assistant-api.secret'. This can be left undefined if the pharia-assistant-api is connected to the internal inference (deployed through this helm-chart). In that case define 'global.servicesSecretRef' instead.
faviconobject{"png":"","svg":"PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIGhlaWdodD0iNzgiIHdpZHRoPSI3OCIgdmlld0JveD0iMjQgMjQgMTAyIDEwMiI+CiAgPHN0eWxlPgogICAgQG1lZGlhIChwcmVmZXJzLWNvbG9yLXNjaGVtZTpkYXJrKXtwYXRoe2ZpbGw6I2ZmZn19CiAgPC9zdHlsZT4KICA8cGF0aCBkPSJtMzQuNjcgMTA2LjQzLTUuNTUtMTMuNTVBMTkuMTQgMTkuMTQgMCAwIDAgMjkgNTcuNDJsNS40Ny0xMy41OWEzMy43OCAzMy43OCAwIDAgMSAuMiA2Mi42Wm0yMi45MyAxNy4xMi04LjY4LTExLjhhNDUuMjggNDUuMjggMCAwIDAgOC42MS04LjI3TDY5IDExMi42MmE1OS44MiA1OS44MiAwIDAgMS0xMS40IDEwLjkzWiIvPgogIDxwYXRoIGQ9Ik04Mi4yMyA3NS4xN2E2MC4zNyA2MC4zNyAwIDAgMC0yNC42NC00OC4zOWwtOC42OCAxMS44MWE0NS42MyA0NS42MyAwIDAgMSAxOC42OCAzNi41OCA2MC4yOCA2MC4yOCAwIDAgMCAyNC40OCA0OC4zOGw4LjY4LTExLjhhNDUuNiA0NS42IDAgMCAxLTE4LjUyLTM2LjU4Wm05Ljg1LTI4LjIzLTExLjQ3LTkuMTJhNjAuMTQgNjAuMTQgMCAwIDEgMTEuOTQtMTEuMzdsOC41NiAxMS44OGE0NS41IDQ1LjUgMCAwIDAtOS4wMyA4LjYxWk0xMTUgMTA2LjUyYTM0LjMyIDM0LjMyIDAgMCAxLS4yOS02Mi41Mmw2LjEgMTMuMzJhMTkuNjggMTkuNjggMCAwIDAgLjE5IDM1LjgzWiIvPgo8L3N2Zz4K"}The favicon used in the assistant can be customized by providing the contents of a logo.svg or logo.png file as a base64 encoded string. This can be created by executing cat favicon.svg | base64 in a terminal. The svg value takes precedence over the png value
favicon.pngstring""The base64 encoded favicon.png
favicon.svgstring"PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIGhlaWdodD0iNzgiIHdpZHRoPSI3OCIgdmlld0JveD0iMjQgMjQgMTAyIDEwMiI+CiAgPHN0eWxlPgogICAgQG1lZGlhIChwcmVmZXJzLWNvbG9yLXNjaGVtZTpkYXJrKXtwYXRoe2ZpbGw6I2ZmZn19CiAgPC9zdHlsZT4KICA8cGF0aCBkPSJtMzQuNjcgMTA2LjQzLTUuNTUtMTMuNTVBMTkuMTQgMTkuMTQgMCAwIDAgMjkgNTcuNDJsNS40Ny0xMy41OWEzMy43OCAzMy43OCAwIDAgMSAuMiA2Mi42Wm0yMi45MyAxNy4xMi04LjY4LTExLjhhNDUuMjggNDUuMjggMCAwIDAgOC42MS04LjI3TDY5IDExMi42MmE1OS44MiA1OS44MiAwIDAgMS0xMS40IDEwLjkzWiIvPgogIDxwYXRoIGQ9Ik04Mi4yMyA3NS4xN2E2MC4zNyA2MC4zNyAwIDAgMC0yNC42NC00OC4zOWwtOC42OCAxMS44MWE0NS42MyA0NS42MyAwIDAgMSAxOC42OCAzNi41OCA2MC4yOCA2MC4yOCAwIDAgMCAyNC40OCA0OC4zOGw4LjY4LTExLjhhNDUuNiA0NS42IDAgMCAxLTE4LjUyLTM2LjU4Wm05Ljg1LTI4LjIzLTExLjQ3LTkuMTJhNjAuMTQgNjAuMTQgMCAwIDEgMTEuOTQtMTEuMzdsOC41NiAxMS44OGE0NS41IDQ1LjUgMCAwIDAtOS4wMyA4LjYxWk0xMTUgMTA2LjUyYTM0LjMyIDM0LjMyIDAgMCAxLS4yOS02Mi41Mmw2LjEgMTMuMzJhMTkuNjggMTkuNjggMCAwIDAgLjE5IDM1LjgzWiIvPgo8L3N2Zz4K"The base64 encoded favicon.svg
featureFlagsobject{"enableQa":true,"enableSummarize":true,"enableTranscribe":true,"enableTranslate":true,"enableUsecases":true}Feature flags for pharia-assistant-api
featureFlags.enableQabooltrueEnable QA feature
featureFlags.enableSummarizebooltrueEnable summarize feature
featureFlags.enableTranscribebooltrueEnable transcribe feature
featureFlags.enableTranslatebooltrueEnable translate feature
featureFlags.enableUsecasesbooltrueEnable usecases feature
fullnameOverridestring"pharia-assistant-api"Override for the full name of pharia-assistant-api
logoobject{"png":"","svg":"PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIGhlaWdodD0iNzgiIHdpZHRoPSI3OCIgdmlld0JveD0iMjQgMjQgMTAyIDEwMiI+CiAgPHBhdGggZD0ibTM0LjY3IDEwNi40My01LjU1LTEzLjU1QTE5LjE0IDE5LjE0IDAgMCAwIDI5IDU3LjQybDUuNDctMTMuNTlhMzMuNzggMzMuNzggMCAwIDEgLjIgNjIuNlptMjIuOTMgMTcuMTItOC42OC0xMS44YTQ1LjI4IDQ1LjI4IDAgMCAwIDguNjEtOC4yN0w2OSAxMTIuNjJhNTkuODIgNTkuODIgMCAwIDEtMTEuNCAxMC45M1oiIC8+CiAgPHBhdGggZD0iTTgyLjIzIDc1LjE3YTYwLjM3IDYwLjM3IDAgMCAwLTI0LjY0LTQ4LjM5bC04LjY4IDExLjgxYTQ1LjYzIDQ1LjYzIDAgMCAxIDE4LjY4IDM2LjU4IDYwLjI4IDYwLjI4IDAgMCAwIDI0LjQ4IDQ4LjM4bDguNjgtMTEuOGE0NS42IDQ1LjYgMCAwIDEtMTguNTItMzYuNThabTkuODUtMjguMjMtMTEuNDctOS4xMmE2MC4xNCA2MC4xNCAwIDAgMSAxMS45NC0xMS4zN2w4LjU2IDExLjg4YTQ1LjUgNDUuNSAwIDAgMC05LjAzIDguNjFaTTExNSAxMDYuNTJhMzQuMzIgMzQuMzIgMCAwIDEtLjI5LTYyLjUybDYuMSAxMy4zMmExOS42OCAxOS42OCAwIDAgMCAuMTkgMzUuODNaIiAvPgo8L3N2Zz4K"}The logo used in the assistant can be customized by providing the contents of a logo.svg or logo.png file as a base64 encoded string. This can be created by executing cat logo.svg | base64 in a terminal. The svg value takes precedence over the png value
logo.pngstring""The base64 encoded logo.png
logo.svgstring"PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIGhlaWdodD0iNzgiIHdpZHRoPSI3OCIgdmlld0JveD0iMjQgMjQgMTAyIDEwMiI+CiAgPHBhdGggZD0ibTM0LjY3IDEwNi40My01LjU1LTEzLjU1QTE5LjE0IDE5LjE0IDAgMCAwIDI5IDU3LjQybDUuNDctMTMuNTlhMzMuNzggMzMuNzggMCAwIDEgLjIgNjIuNlptMjIuOTMgMTcuMTItOC42OC0xMS44YTQ1LjI4IDQ1LjI4IDAgMCAwIDguNjEtOC4yN0w2OSAxMTIuNjJhNTkuODIgNTkuODIgMCAwIDEtMTEuNCAxMC45M1oiIC8+CiAgPHBhdGggZD0iTTgyLjIzIDc1LjE3YTYwLjM3IDYwLjM3IDAgMCAwLTI0LjY0LTQ4LjM5bC04LjY4IDExLjgxYTQ1LjYzIDQ1LjYzIDAgMCAxIDE4LjY4IDM2LjU4IDYwLjI4IDYwLjI4IDAgMCAwIDI0LjQ4IDQ4LjM4bDguNjgtMTEuOGE0NS42IDQ1LjYgMCAwIDEtMTguNTItMzYuNThabTkuODUtMjguMjMtMTEuNDctOS4xMmE2MC4xNCA2MC4xNCAwIDAgMSAxMS45NC0xMS4zN2w4LjU2IDExLjg4YTQ1LjUgNDUuNSAwIDAgMC05LjAzIDguNjFaTTExNSAxMDYuNTJhMzQuMzIgMzQuMzIgMCAwIDEtLjI5LTYyLjUybDYuMSAxMy4zMmExOS42OCAxOS42OCAwIDAgMCAuMTkgMzUuODNaIiAvPgo8L3N2Zz4K"The base64 encoded logo.svg
postgresql.enabledbooltrueThis is used to indicate whether the internal PostgreSQL should be used or not.
resources.limits.cpustring"1000m"
resources.limits.memorystring"8Gi"
resources.requests.cpustring"500m"
resources.requests.memorystring"8Gi"
secretobject{"apiToken":""}Allows to populate the secret identified by 'pharia-assistant-api.existingSecret' through this helm-chart. The secret must contain the field apiToken. See 'pharia-assistant-api.existingSecret' for more information.

document-index

KeyTypeDefaultDescription
databaseConfig.defaultSecretstring"document-index-postgresql-secret"Default secret name is used to create a secret if external.existingSecret is not provided.
databaseConfig.externalobject{"databaseName":"","existingSecret":"","host":"","password":"","port":"","user":""}Provide an existing database if you want to use an external database
databaseConfig.external.databaseNamestring""The name of the database
databaseConfig.external.existingSecretstring""Set this value if a k8s Secret with PostgreSQL values already exists. Make sure that the all the keys exists in the secret with a valid value.
databaseConfig.external.hoststring""The host of the database
databaseConfig.external.passwordstring""The password of the database
databaseConfig.external.portstring""The port of the database
databaseConfig.external.userstring""The user of the database
databaseConfig.secretKeys.databaseNameKeystring"databaseName"The key in the secret that contains the database name
databaseConfig.secretKeys.hostKeystring"host"The key in the secret that contains the host of the database
databaseConfig.secretKeys.passwordKeystring"password"The key in the secret that contains the password of the database
databaseConfig.secretKeys.portKeystring"port"The key in the secret that contains the port of the database
databaseConfig.secretKeys.userKeystring"user"The key in the secret that contains the user of the database
documentsBatchSizeint50The maximal number of documents that are loaded into memory for a single request. Note that at most two of these batches are kept in memory at the same time. Adjust this value to the size of your documents and the available memory.
enabledbooltrueSet this to true to install the document-index subchart as a dependency
existingSecretstring""The name of a secret containing the API token used by the document-index for sending embedding requests to the inference. This allows to connect the document-index to an externally running inference. The secret must contain the field apiToken. It can either be pre-existing or the chart creates it for you with the value defined in 'document-index.secret'. This can be left undefined if the document-index is connected to the internal inference (deployed through this helm-chart). In that case define 'global.servicesSecretRef' instead.
exitOnInvalidAaApiTokenstring"true"Must be set to "true" at the moment.
fullnameOverridestring"document-index"
hostnamestring"document-index"Hostname for the ingress (without domain). The domain is read from global.ingress.ingressDomain. This needs to be changed, if multiple instances are deployed to the same cluster using the same domain.
ingress.annotationsobject{}Annotations for the ingress-resource. This can be used to add ingress controller specific annotations.
ingress.enabledbooltrueEnabled ingress creation
ingress.tls.enabledboolfalseEnable TLS configuration for this Ingress
ingress.tls.secretNamestring"document-index-tls"The name of the secret containing the TLS certificate. See also: https://kubernetes.io/docs/concepts/services-networking/ingress/#tls
postgresql.enabledbooltrueThis is used to indicate whether the internal PostgreSQL should be used or not.
rustLogstring"info"The log configuration. See https://docs.rs/env_logger/latest/env_logger/#enabling-logging for details.
secretobject{"apiToken":""}Allows to populate the secret identified by 'document-index.existingSecret' through this helm-chart. The secret must contain the field apiToken. See 'document-index.existingSecret' for more information.

inference-api

KeyTypeDefaultDescription
admin.emailstring"tools@aleph-alpha.com"Email of the admin user to create on startup
admin.emailKeystring"email"The email key in the secret
admin.existingSecretstring""Existing secret to use instead of email/password. Leave this empty to auto-generate a secret.
admin.passwordstring""Initial password of the admin user. Leave this empty to generate a random password.
admin.passwordKeystring"password"The password key in the secret
databaseConfig.defaultSecretstring"inference-api-postgresql-secret"Default secret name is used to create a secret if external.existingSecret is not provided.
databaseConfig.externalobject{"databaseName":"","existingSecret":"","host":"","password":"","port":"","user":""}Provide an existing database if you want to use an external database
databaseConfig.external.databaseNamestring""The name of the database
databaseConfig.external.existingSecretstring""Set this value if a k8s Secret with PostgreSQL values already exists. Make sure that the all the keys exists in the secret with a valid value.
databaseConfig.external.hoststring""The host of the database
databaseConfig.external.passwordstring""The password of the database
databaseConfig.external.portstring""The port of the database
databaseConfig.external.userstring""The user of the database
databaseConfig.secretKeys.databaseNameKeystring"databaseName"The key in the secret that contains the database name
databaseConfig.secretKeys.hostKeystring"host"The key in the secret that contains the host of the database
databaseConfig.secretKeys.passwordKeystring"password"The key in the secret that contains the password of the database
databaseConfig.secretKeys.portKeystring"port"The key in the secret that contains the port of the database
databaseConfig.secretKeys.userKeystring"user"The key in the secret that contains the user of the database
enableOIDCbooltrueUse OIDC in addition to built-in tokens
enableUnauthenticatedAccessboolfalseSet this to true to disable all token validation in the inference api
fullnameOverridestring"pharia-ai-inference-api"
ingress.annotationsobject{}Annotations for the ingress-resource. This can be used to add ingress controller specific annotations.
ingress.enabledbooltrueEnabled ingress creation
ingress.hostnamestring"inference-api"Hostname for the ingress (without domain). The domain is read from global.ingress.ingressDomain. This needs to be changed, if multiple instances are deployed to the same cluster using the same domain.
ingress.tls.enabledboolfalseEnable TLS configuration for this Ingress
ingress.tls.secretNamestring"inference-api-tls"The name of the secret containing the TLS certificate. See also: https://kubernetes.io/docs/concepts/services-networking/ingress/#tls
postgresql.enabledbooltrueControls whether internal PostgreSQL should be used or not
resources.limits.cpustring"1"
resources.limits.memorystring"8Gi"
resources.requests.cpustring"1"
resources.requests.memorystring"1Gi"
servicesSecretNamestring"inference-api-services"Name of the services secret to generate. The secret actually used by the api is global.servicesSecretRef. If you want to provide your own secret, set this to a name different from your secret. The secret is expected to have a key-value-pair with key secret.

inference-worker

KeyTypeDefaultDescription
checkpointslist[]
fullnameOverridestring"pharia-ai-inference-worker"
image.pullPolicystring"Always"
resources.limits.cpustring"2"
resources.limits.memorystring"8Gi"
resources.requests.cpustring"1"
resources.requests.memorystring"4Gi"
tolerationslist[]

pharia-iam

KeyTypeDefaultDescription
apiobject{"ingress":{"annotations":{},"enabled":false,"tls":{"enabled":false,"secretName":"pharia-iam-api-tls"}}}Internal API configuration
api.ingress.annotationsobject{}Annotations for the ingress-resource. This can be used to add ingress controller specific annotations.
api.ingress.enabledboolfalseEnabled ingress creation
api.ingress.tls.enabledboolfalseEnable TLS configuration for this Ingress
api.ingress.tls.secretNamestring"pharia-iam-api-tls"The name of the secret containing the TLS certificate. See also: https://kubernetes.io/docs/concepts/services-networking/ingress/#tls
configobject{"adminEmail":"admin@localhost","adminEnableDirectUserManagement":false,"adminPassword":null,"adminUserName":"admin"}IAM configuration
config.adminEmailstring"admin@localhost"Email of initial user
config.adminEnableDirectUserManagementboolfalseEnable direct access to user management console for initial admin account. Enable if PhariaOs console is not used, but user management is needed.
config.adminPasswordstringnilInit password of initial user. To be valid it requires to have 10-70 characters, including at least one uppercase letter, one lowercase letter, and one digit. User will need to change this password on the first login.
config.adminUserNamestring"admin"initial user name
databaseConfig.externalobject{"databaseName":"","existingSecret":"","host":"","password":"","port":"","user":""}Provide an existing database if you want to use an external database
databaseConfig.external.databaseNamestring""The name of the database
databaseConfig.external.existingSecretstring""Set this value if a k8s Secret with PostgreSQL values already exists. Make sure that the all the keys exists in the secret with a valid value.
databaseConfig.external.hoststring""The host of the database
databaseConfig.external.passwordstring""The password of the database
databaseConfig.external.portstring""The port of the database
databaseConfig.external.userstring""The user of the database
databaseConfig.secretKeys.databaseNameKeystring"databaseName"The key in the secret that contains the database name
databaseConfig.secretKeys.hostKeystring"host"The key in the secret that contains the host of the database
databaseConfig.secretKeys.passwordKeystring"password"The key in the secret that contains the password of the database
databaseConfig.secretKeys.portKeystring"port"The key in the secret that contains the port of the database
databaseConfig.secretKeys.userKeystring"user"The key in the secret that contains the user of the database
enabledbooltrueSet this to true to install the pharia-iam subchart as a dependency
imageobject{"repository":"alephalpha.jfrog.io/pharia-iam/pharia-iam","tag":""}Image of API and configuration job
ingressobject{"annotations":{},"enabled":true,"tls":{"enabled":false,"secretName":"pharia-iam-tls"}}Ingress configuration (including login endpoints)
ingress.annotationsobject{}Annotations for the ingress-resource. This can be used to add ingress controller specific annotations.
ingress.enabledbooltrueEnabled ingress creation
ingress.tls.enabledboolfalseEnable TLS configuration for this Ingress
ingress.tls.secretNamestring"pharia-iam-tls"The name of the secret containing the TLS certificate. See also: https://kubernetes.io/docs/concepts/services-networking/ingress/#tls
postgresql.enabledbooltrueThis is used to indicate whether the internal PostgreSQL should be used or not.

pharia-kernel

KeyTypeDefaultDescription
enabledboolfalseSet this to true to install the pharia-kernel subchart as a dependency. Pharia Kernel is currently in preview and disabled by default.
envlist[]Define additional environment variables. This is required for config_access_token_env_var when namespace is added in pharia-kernel.namespaces. Both env and envFrom fields are supported. Schema: https://github.com/yannh/kubernetes-json-schema/blob/master/master-standalone-strict/envvar.json See also: https://kubernetes.io/docs/tasks/inject-data-application/define-environment-variable-container/
fullnameOverridestring"pharia-kernel"Set this to override the fully qualified name for Pharia Kernel
ingressobject{"annotations":{},"enabled":true,"hostname":"pharia-kernel","ingressClassName":"nginx","tls":{"enabled":false,"secretName":"pharia-kernel-tls"}}Configure external access to Pharia Kernel
ingress.annotationsobject{}Annotations for the Ingress resource. This can be used to add ingress controller specific annotations
ingress.enabledbooltrueSet this to true to set up an Ingress for Pharia Kernel
ingress.hostnamestring"pharia-kernel"Hostname for the Ingress (without domain). The domain is read from global.ingressDomain. This needs to be changed, if multiple instances are deployed to the same cluster using the same domain
ingress.ingressClassNamestring"nginx"Name of the IngressClass resource. See also: https://kubernetes.io/docs/concepts/services-networking/ingress/#the-ingress-resource
ingress.tlsobject{"enabled":false,"secretName":"pharia-kernel-tls"}Configure TLS for this Ingress
ingress.tls.enabledboolfalseEnable TLS configuration for this Ingress
ingress.tls.secretNamestring"pharia-kernel-tls"The name of the secret containing the TLS certificate. See also: https://kubernetes.io/docs/concepts/services-networking/ingress/#tls
logLevelstring"trace"Set the log level for Pharia Kernel. This does not affect other targets, where errors are always logged. The options are: - error - warn - info - debug - trace - off
namespacesobject{}Configure the namespaces for Pharia Kernel. Each namespace needs to be explicitly defined. Example: # The Namespace name playground: # The URL to the corresponding namespace configuration TOML file config_url: "https://gitlab.aleph-alpha.de/api/v4/projects/123/repository/files/namespace.toml/raw?ref=main" # The access token for config_url config_access_token_env_var: "GITLAB_CONFIG_ACCESS_TOKEN" # The Container Registry that backs the skill registry for this namespace registry: "registry.gitlab.aleph-alpha.de" # The repository in registry that backs the skill registry for this namespace repository: "engineering/pharia-kernel-playground/skills"
openTelemetryEndpointstring""Set the address of the OpenTelemetry protocol (OTLP) collector. No OpenTelemetry tracing subscriber is created if this is not set. Example: "https://tracing.aleph-alpha.com"
resourcesobject{}Specify how much of each resource Pharia Kernel needs. Schema: https://github.com/yannh/kubernetes-json-schema/blob/master/master-standalone-strict/resourcerequirements.json See also: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/
secretRefstring"pharia-kernel-secrets"The name of a secret containing the credentials for Pharia Kernel to access skill registries. The secret must contain the fields referenced by skillRegistryUserRef and skillRegistryPasswordRef
skillRegistryPasswordRefstring"skillRegistryPassword"The key to get password for accessing skill registries. See 'pharia-kernel.secretRef' for more information
skillRegistryUserRefstring"skillRegistryUser"The key to get user name for accessing skill registries. See 'pharia-kernel.secretRef' for more information

pharia-studio-api

KeyTypeDefaultDescription
databaseConfigurationobject{"external":{"databaseName":"","databseUrl":"","existingSecret":"","host":"","password":"","port":"","user":""},"secretKeys":{"databaseNameKey":"databaseName","databaseUrlKey":"databaseUrl","hostKey":"host","passwordKey":"password","portKey":"port","userKey":"user"}}Default database configuration for the pharia-studio-api service access postgres database
databaseConfiguration.externalobject{"databaseName":"","databseUrl":"","existingSecret":"","host":"","password":"","port":"","user":""}Provide an existing database if you want to use an external database
databaseConfiguration.external.databaseNamestring""The name of the database
databaseConfiguration.external.databseUrlstring""The URL of the database
databaseConfiguration.external.existingSecretstring""Set this value if a k8s Secret with PostgreSQL values already exists. Make sure that the all the keys exists in the secret with a valid value.
databaseConfiguration.external.hoststring""The host of the database
databaseConfiguration.external.passwordstring""The password of the database
databaseConfiguration.external.portstring""The port of the database
databaseConfiguration.external.userstring""The user of the database
databaseConfiguration.secretKeys.databaseNameKeystring"databaseName"The key in the secret that contains the database name
databaseConfiguration.secretKeys.databaseUrlKeystring"databaseUrl"The key in the secret that contains the database URL
databaseConfiguration.secretKeys.hostKeystring"host"The key in the secret that contains the host of the database
databaseConfiguration.secretKeys.passwordKeystring"password"The key in the secret that contains the password of the database
databaseConfiguration.secretKeys.portKeystring"port"The key in the secret that contains the port of the database
databaseConfiguration.secretKeys.userKeystring"user"The key in the secret that contains the user of the database
enabledbooltrueSet this to true to install the pharia-studio-api subchart as a dependency
fullnameOverridestring"pharia-studio-api"Default nameOverride of the application
ingress.annotationsobject{}Annotations for the ingress-resource. This can be used to add ingress controller specific annotations.
ingress.enabledbooltrueEnabled ingress creation
ingress.hostnamestring"pharia-studio-api"Hostname for the ingress (without domain). The domain is read from global.ingress.ingressDomain. This needs to be changed, if multiple instances are deployed to the same cluster using the same domain.
ingress.tls.enabledboolfalseEnable TLS configuration for this Ingress
ingress.tls.secretNamestring"pharia-studio-api-tls"The name of the secret containing the TLS certificate. See also: https://kubernetes.io/docs/concepts/services-networking/ingress/#tls
postgresql.enabledbooltrue
resources.limits.cpustring"1"
resources.limits.memorystring"1Gi"
resources.requests.cpustring"500m"
resources.requests.memorystring"1Gi"

pharia-studio-ui

KeyTypeDefaultDescription
enabledbooltrue
fullnameOverridestring"pharia-studio-ui"
ingress.annotationsobject{}Annotations for the ingress-resource. This can be used to add ingress controller specific annotations.
ingress.enabledbooltrueEnabled ingress creation
ingress.hostnamestring"pharia-studio-ui"Hostname for the ingress (without domain). The domain is read from global.ingress.ingressDomain. This needs to be changed, if multiple instances are deployed to the same cluster using the same domain.
ingress.tls.enabledboolfalseEnable TLS configuration for this Ingress
ingress.tls.secretNamestring"phariaos-studio-ui-tls"The name of the secret containing the TLS certificate. See also: https://kubernetes.io/docs/concepts/services-networking/ingress/#tls
phariaStudioAPISchemastring"http"Internal cluster communication with pharia-studio-api. This is the default value. https can be set if the internal communication is over https.
resources.limits.cpustring"100m"
resources.limits.memorystring"256Mi"
resources.requests.cpustring"50m"
resources.requests.memorystring"256Mi"

pharia-translate

KeyTypeDefaultDescription
client.resources.limits.cpustring"1"
client.resources.limits.memorystring"1Gi"
client.resources.requests.cpustring"100m"
client.resources.requests.memorystring"1Gi"
deploymentobject{}
enabledbooltrueSet this to true to install the pharia-translate subchart as a dependency
fullnameOverridestring"pharia-translate"
marianServer.resources.limits."nvidia.com/gpu"int1
marianServer.resources.limits.cpustring"1"
marianServer.resources.limits.memorystring"16Gi"
marianServer.resources.requests.cpustring"100m"
marianServer.resources.requests.memorystring"16Gi"
nodeSelectorobject{}
tolerationslist[]

phariaos-manager

KeyTypeDefaultDescription
clusterRole.enabledbooltrueEnable the cluster role for the phariaos-manager to enable for hardware listing.
databaseConfig.externalobject{"databaseName":"","existingSecret":"","host":"","password":"","port":"","user":""}Provide an existing database if you want to use an external database
databaseConfig.external.databaseNamestring""The name of the database
databaseConfig.external.existingSecretstring""Set this value if a k8s Secret with PostgreSQL values already exists. Make sure that the all the keys exists in the secret with a valid value.
databaseConfig.external.hoststring""The host of the database
databaseConfig.external.passwordstring""The password of the database
databaseConfig.external.portstring""The port of the database
databaseConfig.external.userstring""The user of the database
databaseConfig.secretKeys.databaseNameKeystring"databaseName"The key in the secret that contains the database name
databaseConfig.secretKeys.hostKeystring"host"The key in the secret that contains the host of the database
databaseConfig.secretKeys.passwordKeystring"password"The key in the secret that contains the password of the database
databaseConfig.secretKeys.portKeystring"port"The key in the secret that contains the port of the database
databaseConfig.secretKeys.userKeystring"user"The key in the secret that contains the user of the database
enabledbooltrueSet this to true to install the phariaos-manager subchart as a dependency
fullnameOverridestring""Set this to override the full name of the phariaos-manager
ingress.annotationsobject{}Annotations for the ingress-resource. This can be used to add ingress controller specific annotations.
ingress.enabledbooltrueEnabled ingress creation
ingress.hostnamestring"phariaos-manager"Hostname for the ingress (without domain). The domain is read from global.ingress.ingressDomain. This needs to be changed, if multiple instances are deployed to the same cluster using the same domain.
ingress.tls.enabledboolfalseEnable TLS configuration for this Ingress
ingress.tls.secretNamestring"phariaos-manager-tls"The name of the secret containing the TLS certificate. See also: https://kubernetes.io/docs/concepts/services-networking/ingress/#tls
postgresql.enabledbooltrueThis is used to indicate whether the internal PostgreSQL should be used or not.
usecase.enabledbooltrueEnable usecases creation and deployment in phariaos-manager API.
usecase.imagePullSecretNamestring""Secret to authenticate container registry to pull/verify usecase images. Make sure the secret is in the Release namespace!

phariaos-ui

KeyTypeDefaultDescription
enabledbooltrueSet this to true to install the phariaos-ui subchart as a dependency
fullnameOverridestring""Set this to override the full name of the phariaos-ui
ingress.annotationsobject{}Annotations for the ingress-resource. This can be used to add ingress controller specific annotations.
ingress.enabledbooltrueEnabled ingress creation
ingress.hostnamestring"pharia-os"Hostname for the ingress (without domain). The domain is read from global.ingress.ingressDomain. This needs to be changed, if multiple instances are deployed to the same cluster using the same domain.
ingress.tls.enabledboolfalseEnable TLS configuration for this Ingress
ingress.tls.secretNamestring"phariaos-ui-tls"The name of the secret containing the TLS certificate. See also: https://kubernetes.io/docs/concepts/services-networking/ingress/#tls

pharia-data-api

KeyTypeDefaultDescription
databaseConfig.defaultSecretstring"pharia-data-api-postgresql-secret"Default secret name is used to create a secret if external.existingSecret is not provided.
databaseConfig.externalobject{"databaseName":"","existingSecret":"","host":"","password":"","port":"","user":""}Provide an existing database if you want to use an external database
databaseConfig.external.databaseNamestring""The name of the database
databaseConfig.external.existingSecretstring""Set this value if a k8s Secret with PostgreSQL values already exists. Make sure that the all the keys exists in the secret with a valid value.
databaseConfig.external.hoststring""The host of the database
databaseConfig.external.passwordstring""The password of the database
databaseConfig.external.portstring""The port of the database
databaseConfig.external.userstring""The user of the database
databaseConfig.secretKeys.databaseNameKeystring"databaseName"The key in the secret that contains the database name
databaseConfig.secretKeys.hostKeystring"host"The key in the secret that contains the host of the database
databaseConfig.secretKeys.passwordKeystring"password"The key in the secret that contains the password of the database
databaseConfig.secretKeys.portKeystring"port"The key in the secret that contains the port of the database
databaseConfig.secretKeys.userKeystring"user"The key in the secret that contains the user of the database
enabledbooltrueSet this to true to install the pharia-data-api subchart as a dependency
fullnameOverridestring"pharia-data-api"
ingress.annotationsobject{}Annotations for the ingress-resource. This can be used to add ingress controller specific annotations.
ingress.enabledbooltrueEnabled ingress creation
ingress.hostnamestring"pharia-data-api"Hostname for the ingress (without domain). The domain is read from global.ingress.ingressDomain. This needs to be changed, if multiple instances are deployed to the same cluster using the same domain.
ingress.tls.enabledboolfalseEnable TLS configuration for this Ingress
ingress.tls.secretNamestring"pharia-data-api-tls"The name of the secret containing the TLS certificate. See also: https://kubernetes.io/docs/concepts/services-networking/ingress/#tls
minio.enabledbooltrue
minio.fullnameOverridestring"minio-data"
postgresql.enabledbooltrueThis is used to indicate whether the internal PostgreSQL should be used or not.
storageConfig.defaultSecretstring"pharia-data-api-storage-secret"
storageConfig.external.existingSecretstring""
storageConfig.external.externalBucketPasswordstring""
storageConfig.external.externalBucketUserstring""
storageConfig.external.internalBucketPasswordstring""
storageConfig.external.internalBucketUserstring""
storageConfig.external.storageUrlstring""
tasks.enabledbooltrue

Maintainers

NameEmailUrl
PhariaAIphariaai@aleph-alpha.com