# Private Container Registries

This guide demonstrates how to configure a private container registry with the Immuta Enterprise Helm chart (IEHC).

{% hint style="info" %}
**Image availability**

This guide assumes that you have already copied all Immuta container images to your private registry. The process of copying images to a private registry can vary significantly depending on your specific environment and tools and is therefore outside the scope of this document.
{% endhint %}

## Helm values

{% hint style="info" %}
**Image repository overrides**

Each `image.repository` field defined in the default Helm values must be overridden. For the purposes of this guide, only the configuration for Secure is shown.
{% endhint %}

1. Examine the default Helm values in the chart; this will include all relevant values required to override the registry and images.

   ```bash
   helm show values oci://ocir.immuta.com/stable/immuta-enterprise --version 2025.1.10
   ```
2. Edit the `immuta-values.yaml` to include the following Helm values. Update all [placeholder values](https://documentation.immuta.com/2025.1/configuration/self-managed-deployment/conventions) with your own values.

   ```yaml
   global:
     imageRegistry: <private-registry-fqdn>
   secure:
     backgroundWorker:
       image:
         repository: <prefix>/immuta-service
     web:
       image:
         repository: <prefix>/immuta-service
   ```