Skip to content

Helm Chart Values

When installing Precept into a Kubernetes cluster using Helm, server behaviour may be adjusted by overriding the Values specified in the Chart. The following table details the most commonly used, Precept-specific parameters:

Valuetyperequireddefaultnotes
postgresql.enabledbooleannofalseWhether to enable the built-in PostgreSQL deployment for persistent storage.

IMPORTANT: If not set, an appropriate connection string must specified for Server and Migration services through server.env.PRECEPT_STORAGE_CONNECTION and migrate.env.DATABASE_URL.
image.tagstringno""Overrides the image tag; when empty, defaults to the chart appVersion.

IMPORTANT: Do not rely on the default appVersion specified in the Chart; instead use an explicit version number as advised by the Precept team.
server.envobjectno{}Key/value map of Environment Variables to set on the server container.
migrate.envobjectno{}Key/value map of environment variables for the migration Job container.
migrate.annotationsobjectno{}Annotations to add to the migration Job.
imagePullSecretsarrayno[]List of image pull secrets for private registries.

IMPORTANT: At least one ImagePullSecret must be specified; it should reference the Docker Registry Token that was issued to your Organization by the Precept team.
nameOverridestringno""Override the chart name used in Kubernetes resource names.
fullnameOverridestringno""Override the fully qualified name for Kubernetes resources.
podAnnotationsobjectno{}Additional annotations to add to Pods.
podLabelsobjectno{}Additional labels to add to Pods.
ingress.enabledbooleannofalseEnable creation of an Ingress resource.

For an exhaustive list of all Values supported by the Chart, use the following Helm command to print the Chart's default values.yaml file:

helm show values oci://ghcr.io/precept-sh/helm/precept-server