LogoLogo
Public Knowledge Base
Public Knowledge Base
  • Self-hosted Immuta
    • Official Immuta Self-Managed Deployment Documentation
    • What's new in 2024.2?
    • Deployment Options
      • AWS Immuta Deployment
      • Azure Immuta Deployment
      • K3s Deployment
      • SUSE Rancher Kubernetes Engine (RKE2) Deployment
      • In-cluster PostgreSQL using Crunchydata
      • In-cluster Elasticsearch using Elastic Cloud on Kubernetes (ECK)
      • Production Linkerd with AWS Private CA issuer
      • Deploying Linkerd via Open Source Linkerd
      • Deploying Linkerd Service Mesh via Buoyant Enterprise for Linkerd
      • Uninstalling Linkerd
      • Upgrading to Immuta 2024.2 LTS
      • LTS Upgrade via Legacy Chart
      • Legacy Audit - no Elasticsearch
      • Temporal with RDS
      • Setting Up OpenSearch User Pemissions
    • Air gapped installations
      • Immuta Installation on k3s in Air Gapped environment
      • Air-gapped Installation Artifact Transfer
  • Excessive failed jobs in pgboss impacting system performance
  • Example Trino installation via Open Source Helm Chart
  • Immuta Installation on Self Managed Infrastructure Overview
  • Repeatable k3s stack deployment on AWS EC2
  • Trino OAuth2 and JWT via Okta
  • Copy of Okta Attribute Mapping
Powered by GitBook
On this page
  • Deploy Immuta 2024.1.x
  • Deploy Immuta 2024.2.0
  1. Self-hosted Immuta
  2. Deployment Options

LTS Upgrade via Legacy Chart

It is possible, but not recommended, to upgrade to the 2024.2 LTS release via the legacy Immuta Helm Chart. This document captures that process via an in-place upgrade from 2024.1.9 to 2024.2.0.

This process implies using legacy audit rather than the new audit service and detect and no classify service.

Deploy Immuta 2024.1.x

---
immutaVersion: 2024.1.9
externalHostname: legacy.immuta.us
global:
  imageRegistry: 231431240278.dkr.ecr.us-east-1.amazonaws.com
web:
  ingress:
    ingressClassName: alb
    annotations:
      alb.ingress.kubernetes.io/group.name: immuta-trino
      alb.ingress.kubernetes.io/scheme: internet-facing
      alb.ingress.kubernetes.io/target-type: ip
      alb.ingress.kubernetes.io/listen-ports: '[{"HTTP": 80}, {"HTTPS":443}]'
      alb.ingress.kubernetes.io/ssl-redirect: '443'
      alb.ingress.kubernetes.io/backend-protocol: HTTPS
database:
  enabled: true
  replicas: 1
  persistence:
    enabled: true
    volumeClaimSpec:
      resources:
        requests:
          storage: 20Gi
queryEngine:
  replicas: 1
  persistence:
    enabled: true
    volumeClaimSpec:
      resources:
        requests:
          storage: 20Gi
nginxIngress:
  enabled: false
backup:
  enabled: false
  restore:
    enabled: false

Deploy Immuta 2024.2.0

To deploy using the legacy Helm Chart, update the immutaVersion and add the following variables to web

  extraEnvVars:
    - name: FeatureFlag_AuditService
      value: "false"
    - name: FeatureFlag_detect
      value: "false"
    - name: FeatureFlag_auditLegacyViewHide
      value: "false"
PreviousUpgrading to Immuta 2024.2 LTSNextLegacy Audit - no Elasticsearch