> For the complete documentation index, see [llms.txt](https://documentation.immuta.com/latest/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.immuta.com/latest/configuration/self-managed-deployment/configure/private-container-registries.md).

# Private Container Registries

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

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

This guide assumes the Immuta container images are already in your private registry. To copy them there with their digests intact, see the [Air-gapped environments guide](/latest/configuration/self-managed-deployment/configure/immuta-in-an-air-gapped-environment.md). The same download/push process applies even when the environment is not air-gapped.
{% endhint %}

## Registry with preserved repository paths

If the images keep their original repository paths (for example, `stable/immuta-service` stays `stable/immuta-service`), the only value required is the registry itself:

```yaml
global:
  imageRegistry: <private-registry-fqdn>
```

## Registry with a path prefix

If your registry imposes a path prefix (common with Artifactory or Harbor project layouts), map each repository with `global.imageRepositoryMap`. Do not override each component's `image.repository` individually:

```yaml
global:
  imageRegistry: <private-registry-fqdn>
  imageRepositoryMap:
    stable/immuta-service: <prefix>/stable/immuta-service
    stable/audit-service: <prefix>/stable/audit-service
    # ...one entry per repository
```

List every repository the chart references:

```bash
helm show values oci://ocir.immuta.com/stable/immuta-enterprise --version 2026.2.2 | grep 'repository:' | sort -u
```

## Pull secret

If your private registry requires authentication, create a pull secret and reference it globally:

```bash
kubectl create secret docker-registry immuta-private-registry \
    --docker-server=<private-registry-fqdn> \
    --docker-username=<username> \
    --docker-password=<password>
```

```yaml
global:
  imagePullSecrets:
    - name: immuta-private-registry
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://documentation.immuta.com/latest/configuration/self-managed-deployment/configure/private-container-registries.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.