Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Private Container Registries

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

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. The same download/push process applies even when the environment is not air-gapped.

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:

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:

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:

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

Pull secret

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

Last updated

Was this helpful?