Managed Public Cloud
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)
Prerequisites
The following cloud-managed services must be provisioned before proceeding:
Validation
PostgreSQL
Elasticsearch
Authenticate with OCI registry
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:
Setup
Create a Kubernetes namespace named
immuta
for Immuta.Switch to namespace
immuta
.Create a container registry pull secret. Contact your Immuta representative to obtain credentials to authenticate with ocir.immuta.com.
PostgreSQL
Connecting to the database
There are numerous ways to connect to a PostgreSQL database. This step demonstrates how to connect by creating an ephemeral Kubernetes pod.
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 necessary databases and role.
Revoke privileges from
CURRENT_USER
as they're no longer required.Enable the
pgcrypto
extension.Type
\q
, and then pressEnter
to exit.
Install Immuta
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.
Validation
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 namedhttp
.
Next steps
Last updated