Helm Chart Configuration Options

The Helm Chart includes components that make up your Immuta infrastructure, and you can change these values to tailor your Immuta infrastructure to suit your needs. The tables below include parameter descriptions and default values for all components in the Helm Chart.

When installing Immuta, download immuta-values.yaml and update the values to your preferred settings.

See the for guidance and best practices.

Global

Backup

AWS S3 Backups

These values are used when backup.type=s3.

Azure Blob Storage

These values are used when backup.type=azblob.

Google Cloud Storage

These values are used when backup.type=gs.

Immuta TLS

Web Service

Fingerprint Service

Metadata Database

The Metadata Database component can be configured to use either the built-in Kubernetes deployment or an external PostgreSQL database.

The following Helm values are shared between both built-in and external databases.

Built-in Database

These values are used when database.enabled=true.

External Database

These values are used when database.enabled=false.

Query Engine

Query Engine Port

If you will only use integrations, port 5432 is optional. Using the built-in Ingress Nginx Controller, you can disable it by setting the value to false.

Chart Hooks

Cleanup

The Cleanup hook is a Helm post-delete hook that is responsible for cleaning up some resources that are not deleted by Helm.

Database Initialize

The database initialize hook is used to initialize the external database when database.enabled=false.

TLS Generation

The TLS generation hook is a Helm pre-install hook that is responsible for generating TLS certificates used for connections between the Immuta pods.

Cache

Deploy Tools

Ingress Controller

Memcached