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.
Copy ---
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
Copy extraEnvVars:
- name: FeatureFlag_AuditService
value: "false"
- name: FeatureFlag_detect
value: "false"
- name: FeatureFlag_auditLegacyViewHide
value: "false"