Audience: System Administrators
Content Summary: This page outlines the supported deployment methods for installing Immuta.
We recommended installing Immuta with Kubernetes because of the minimal administration needed to achieve scale and availability, but Immuta can also be installed on a single Docker node. This chapter illustrates how to install Immuta using both of these methods.
Immuta Query Engine Port
The required firewall rules depend on whether you will use the Immuta Query Engine or exclusively use integrations. If you only use integrations, port 5432 is optional.
The following firewall rules are required to be opened to any host or network that need access to the Immuta service. Navigate to the tab of the technology you plan to use:
Immuta has a Helm chart available for installation on Kubernetes:
Specific guides are available for the following Kubernetes cloud providers:
Supported Software Versions
Immuta supports the following versions of Kubernetes:
Note: Immuta only supports the open source version of Kubernetes; the version should not be modified nor wrapped in a different deployment model.
Immuta depends on the Helm functionality outlined below.
- templates and functions
- Helm hooks:
- post-delete: This hook is not strictly necessary and is only used to clean up some resources that are not deleted
by Helm itself. If the post-delete hook is not supported, some resources may be left on the cluster after
Immuta support ends at our Helm implementation; wrapping Helm in another orchestration tool falls outside the Immuta support window.
Single Node Docker
Single Node Docker Support
Single Node Docker can be used in production environments after a sizing review by the Immuta Customer Success team.
Immuta has a shell script based installation that can be used on a single Docker node:
Single Node Docker Limitations
The following features are unavailable in the Single Node Docker deployment method and are only supported in Kubernetes deployments:
- automatic backups
- external metadata database