Deploy Immuta without Elasticsearch
Last updated
Was this helpful?
Last updated
Was this helpful?
Feature availability
If you deploy Immuta without Elasticsearch, several core services and features will be unavailable. See the for details.
The guides below outline how to deploy Immuta without Elasticsearch.
This is a guide on how to deploy Immuta on Kubernetes in the following managed public cloud providers:
Amazon Web Services (AWS)
Microsoft Azure
Google Cloud Platform (GCP)
The following cloud-managed services must be provisioned before proceeding:
Amazon Web Services (AWS):
Microsoft Azure:
Google Cloud Platform (GCP):
The PostgreSQL instance's hostname/FQDN is .
The PostgreSQL instance is .
Helm chart availability
The deprecated Immuta Helm chart (IHC) is not available from ocir.immuta.com.
Copy the snippet below and replace the placeholder text with the credentials provided to you by your customer success manager:
Create a Kubernetes namespace named immuta
for Immuta.
Switch to namespace immuta
.
Connect to the database as superuser (postgres) by creating an ephemeral container inside the Kubernetes cluster. A shell prompt will not be displayed after executing the kubectl run
command outlined below. Wait 5 seconds, and then proceed by entering a password.
Create an immuta
role and database.
Revoke privileges from CURRENT_USER
as they're no longer required.
Enable the pgcrypto
extension.
Type \q
, and then press Enter
to exit.
This section demonstrates how to deploy Immuta using the Immuta Enterprise Helm chart once the prerequisite cloud-managed services are configured.
Create a Helm values file named immuta-values.yaml
with the following content:
Deploy Immuta.
Wait for all pods in the namespace to become ready.
Determine the name of the Secure service.
Listen on local port 8080
, forwarding TCP traffic to the Secure service's port named http
.
Amazon Web Services (AWS)
Microsoft Azure
Google Cloud Platform (GCP)
Create a container registry pull secret. Your credentials to authenticate with ocir.immuta.com can be viewed in your user profile at .
Update all in the immuta-values.yaml
file.
to complete your installation and access your Immuta application.
to secure your Ingress by specifying a Secret that contains a TLS private key and certificate.
.
to complete your installation and access your Immuta application.
to secure your Ingress by specifying a Secret that contains a TLS private key and certificate.
.
to complete your installation and access your Immuta application.
to secure your Ingress by specifying a Secret that contains a TLS private key and certificate.
.
The PostgreSQL instance's hostname/FQDN is .
The PostgreSQL instance is .
The Redis instance's hostname/FQDN is .
The Redis instance is .
Create a container registry pull secret. Your credentials to authenticate with ocir.immuta.com can be viewed in your user profile at .
Create a Helm values file named immuta-values.yaml
with the content below. Because the Ingress resource will be managed by an OpenShift route you will create when and not the Immuta Enterprise Helm chart, ingress
is set to false
below. TLS comes pre-configured with OpenShift, so tls
is also set to false
.
Update all in the immuta-values.yaml
file.
to complete your installation and access your Immuta application.
.
For the purposes of this guide, the state stores are deployed in Kubernetes using third-party Helm charts maintained by .
Create a container registry pull secret. Your credentials to authenticate with ocir.immuta.com can be viewed in your user profile at .
Update all in the pg-values.yaml
file.
Update all in the immuta-values.yaml
file.
to complete your installation and access your Immuta application.
to secure your Ingress by specifying a Secret that contains a TLS private key and certificate.
.