Generic Installation

This is a generic guide that demonstrates how to deploy Immuta into any Kubernetes cluster without dependencies on any particular cloud provider.

Considerations

For the purposes of this guide, the following state stores are deployed in Kubernetes using third-party Helm charts maintained by Bitnami:

• Elasticsearch

• PostgreSQL

• Operational overhead: Managing PostgreSQL and Elasticsearch on Kubernetes requires expertise in deploying, maintaining, and scaling these databases and search engines effectively. This involves tasks like setting up monitoring, configuring backups, managing updates, and ensuring high availability. Cloud-managed services abstract much of this operational burden away, allowing teams to focus on application development rather than infrastructure management.

• Resource allocation and scaling: Kubernetes requires careful resource allocation and scaling decisions to ensure that PostgreSQL and Elasticsearch have sufficient CPU, memory, and storage. Properly sizing these resources can be challenging and may require continuous adjustments as workload patterns change. Managed services typically handle this scaling transparently and can automatically adjust based on demand.

• Data integrity and high availability: PostgreSQL and Elasticsearch deployments need robust strategies for data integrity and high availability. Kubernetes can facilitate high availability through pod replicas and distributed deployments, but ensuring data consistency and durability across database instances and search indexes requires careful consideration and often additional tooling.

• Performance: Kubernetes networking and storage configurations can introduce performance overhead compared to native cloud services. For latency-sensitive applications or high-throughput workloads, these factors become critical in maintaining optimal performance.

• Observability: Troubleshooting issues in a Kubernetes environment, especially related to database and search engine performance, can be complex. Managed services typically come with built-in monitoring, logging, and alerting capabilities tailored to the specific service, making it easier to identify and resolve issues.

• Security and compliance: Kubernetes environments require careful attention to security best practices, including network policies, access controls, and encryption. Managed services often come pre-configured with security features and compliance certifications, reducing the burden on teams to implement and maintain these measures.

Copy the snippet below and replace the placeholder text with the credentials provided to you by your customer success manager:

1. Create a Kubernetes namespace named immuta for Immuta and its third-party dependencies.

2. Switch to namespace immuta.

3. Create a container registry pull secret. Your credentials to authenticate with ocir.immuta.com can be viewed in your user profile at .

1. Create a Helm values file named es-values.yaml with the following content:

2. Deploy Elasticsearch.

1. Create a Helm values file named pg-values.yaml with the following content:

2. Update all in the pg-values.yaml file.

3. Deploy PostgreSQL.

This section demonstrates how to deploy Immuta using the Immuta Enterprise Helm chart once the prerequisite local services are configured.

1. Create a Helm values file named immuta-values.yaml with the following content:

2. Update all in the immuta-values.yaml file.

1. Deploy Immuta.

1. Wait for all pods in the namespace to become ready.

2. Determine the name of the Secure service.

3. Listen on local port 8080, forwarding TCP traffic to the Secure service's port named http.

• 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.

• .