Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Immuta v2023.4.12 was released May 7, 2024.
The Unity Catalog integration configuration could not be saved if OAuth token passthrough was used as the authentication method.
Immuta v2023.4.11 was released April 24, 2024.
After adding an external catalog to Immuta, users could not edit it and retest the connection on the Immuta app settings page.
Users could not create or update integration configurations if they used Snowflake External OAuth.
Users encountered an error when modifying an existing Unity Catalog integration that used Oauth token passthrough if the integrations API was not enabled on their tenant.
Long subscription policies caused out of memory errors.
Fixes to address performance issues with Databricks in the Unity Catalog integration.
Immuta v2023.4.10 was released March 19, 2024.
When users tried to modify a policy that predated support for write policies, they received the following error message: Unable to update the policy, the access grant type cannot be changed.
Immuta v2023.4.9 was released February 28, 2024.
Vulnerabilities addressed:
CVE-2023-42282
CVE-2023-5869
CVE-2024-0985
Immuta v2023.4.8 was released February 21, 2024.
Faster query performance with Snowflake memoizable functions: When a policy is applied to a column, Immuta now uses Snowflake memoizable functions to cache the result of common lookups in the policy encapsulated in the called function.
Subsequently, when users query a column with the applied policy, Immuta leverages the cached result, resulting in significant enhancements to query performance.
To enable support for memoizable functions, please contact your Immuta customer success representative.
Deleting a project in Redshift Spectrum did not drop the Immuta created views for the corresponding data sources.
Immuta v2023.4.7 was released February 7, 2024.
Performance improvements when masking policies are applied to data sources with over 500 columns tagged.
Performance improvements of automatic subscription policy background jobs.
Immuta v2023.4.6 was released February 2, 2024.
Any attempt to stage or remove automatic subscription policies resulted in revokes not going through to Databricks if there was a casing mismatch between the principal user from Databricks and the external username mapped to Immuta.
Immuta v2023.4.5 was released January 12, 2024.
When attempting to create a Databricks Unity Catalog data source using OAuth authentication, users received a 500 Internal Server Error
.
Immuta v2023.4.4 was released January 5, 2024.
Snowflake user impersonation roles were being removed incorrectly.
Snowflake low row access policy mode was re-enabled after users disabled the feature and saved their configuration changes.
Fixes to address a race condition that sometimes prevented Snowflake table grants from properly granting and revoking access.
After a Redshift integration connection test was successful in the Immuta UI, users encountered an Internal server error
when attempting to save the integration settings.
Immuta was not granting access to data sources with a hasTagAs
policy applied correctly. If users did not initially have the attribute specified when the policy was created, they were not granted access to the data source if they were later given the specified attribute.
Immuta v2023.4.3 was released December 5, 2023.
The Databricks Unity Catalog OAuth certificate field was broken when users attempted to add certificates on the integrations page.
Immuta v2023.4.2 was released November 28, 2023.
Schema monitoring did not create or delete views in Redshift Spectrum if data sources were registered through the Immuta V2 API /data
endpoint.
When users attempted to register data sources from two different Starburst (Trino) catalogs, they encountered a remote table validation error if the table and schema names were the same.
Immuta v2023.4.1 was released November 7, 2023.
Snowflake table grants fix to address a caching issue that may have led to revokes not properly being granted.
Fixes related to Databricks Unity Catalog custom certificate authority configuration. This feature is currently in preview and only available to select accounts.
Immuta v2023.4.0 was released November 1, 2023.
Snowflake low row access policy mode is generally available. This mode improves query performance in Immuta's Snowflake integration by decreasing the number of Snowflake row access policies Immuta creates.
The /detectRemoteChanges
endpoint's schemaEvolutionId
parameter runs schema monitoring jobs on all tables associated with the specified ID. To boost performance when registering new data sources, users with a large number of data sources can use the new skipColumnDetection
optional parameter to skip running column detection jobs on existing data sources.
Users can configure their Databricks Unity Catalog integration to support their proxy server.
The Databricks Unity Catalog integration supports OAuth token passthrough. This feature is currently in preview and only available to select accounts.
All users must be on Immuta version 2022.5 or newer to migrate directly to 2023.4.
General availability date: The date the software version is available to all customers.
Support period: The period of time between the general availability date and the end of support date. During this period, Immuta will keep the version up-to-date with important bug fixes and security updates.
End of support date: The date when Immuta will stop backporting critical bug fixes to the release. For LTS releases, this is one year after the general availability date. For all other major releases, this is typically one month after the next release (four months after the general availability date).
Extended support period: The period of time between the end of support date and the extended support date. During this period, Immuta will no longer provide bug fix updates to the version, but will investigate and troubleshoot issues. Immuta recommends to upgrade before this period.
End of extended support date: The date when Immuta is no longer obligated to investigate issues raised against the release. The end of extended support date will occur three months after the next major release.
Immuta releases one long-term support (LTS) version each year that is kept up-to-date with important bug fixes and security updates for one year. Our customers who prefer to remain on an Immuta version for an extended period of time can install the LTS versions and be confident that their implementation is stable and supported.
Major releases that are not designated “LTS” will be updated with important bug fixes until one month after the next major release.
Why should I choose the LTS version?
Immuta recognizes that frequent upgrades are not feasible for many of our customers and wants to ensure that customers can remain on versions of the product that are well-supported. The LTS model ensures that customers who choose to stay on an Immuta version for a longer time will benefit from stability and security updates without being exposed to the risk of functionality changes.
I am on an older version today. Do I have to upgrade to an LTS version?
Immuta recommends that customers on older versions start planning an upgrade to the LTS or a more recent quarterly version.
Can I still use older versions?
The Customer Success team will continue to answer questions and help you troubleshoot older versions as much as possible. However, Immuta will not provide code updates to versions that have reached their end of support date.
What if I want the latest version of Immuta?
Great! Staying up-to-date with the latest Immuta release is the best way to get the latest features and improvements. The LTS model does not impact you. You will always be supported with critical bug fixes and security updates when you are using one of the two most recent major releases of Immuta. Immuta recommends to plan for quarterly upgrades to stay on a supported version when not on the LTS.
How are the non-LTS versions supported?
Major releases that are not designated LTS are supported with critical bug fixes through the next two major release dates, which is typically a four-month period, giving time for an upgrade each quarter.
What are considered critical bug fixes?
Cybersecurity vulnerabilities (CVEs) that are categorized as critical or high and have a possible impact within the Immuta solution.
Bugs that cause a severe and ongoing disruption to our customers' ability to conduct business in production, including critical performance impacts.
Version | General availability date | End of support date | End of extended support date |
---|---|---|---|
2024.2 LTS
April 2024
April 2025
June 2025
2024.1
January 2024
May 2024
October 2024
2023.4
November 2023
May 2024
October 2024
2023.3
September 2023
December 2023
September 2024
2023.2
July 2023
December 2023
June 2024
2023.1
March 2023
September 2023
March 2024
2022.5 LTS
December 2022
April 2024
July 2024
Immuta supports the following databases.
Amazon Redshift
Amazon Redshift Serverless
Amazon Redshift Spectrum
Amazon S3
Azure Synapse Analytics (Immuta only supports Dedicated SQL pools, not Serverless SQL pools.)
Google BigQuery
Databricks Unity Catalog:
Databricks clusters (See the Databricks Installation guide for supported Databricks runtimes.)
Databricks SQL
Snowflake
Starburst (Trino)
The following legacy databases are currently supported for existing customers.
Apache Impala
Amazon Athena
Amazon EMR Hive - Deprecated in 2023.2
Amazon EMR Spark - Deprecated in 2023.2
Amazon S3 proxy - Deprecated in 2023.3
Azure Data Lake Storage - Deprecated in 2023.3
Azure SQL - Deprecated in 2023.3
CDH Spark
Elasticsearch
Greenplum
MySQL
Netezza
Oracle
PostgreSQL
SQL Server
Immuta supports the following Kubernetes distributions. Click a link below for details.
Immuta supports these external catalogs. Click a link below for configuration instructions.
For details about the IAM protocols and providers in this section, see the support matrix in the Identity Managers Overview.
Immuta fully supports these IAM protocols:
AD/LDAP
SAML 2.0
OpenID Connect 1.0
These are common providers that support the protocols listed above. However, this list may not be all-inclusive, and if a provider stops supporting one of those protocols, Immuta may not fully support that provider.
Active Directory
ADFS
Amazon Cognito
Centrify
JumpCloud
Keycloak
Microsoft Entra ID
Okta
OneLogin
OpenLDAP and other LDAP servers
Oracle Access Manager
Ping Identity
Immuta supports the following web browsers.
Firefox
Google Chrome
Microsoft Edge
Immuta CLI v1.3.0 was released April 4, 2024. It allows you to export universal audit model (UAM) events to ADLS Gen2.
Linux x86_64 (amd64):
Linux ARMv8 (arm64):
Darwin x86_64 (amd64):
Darwin ARMv8 (arm64):
Download and add the binary to a directory in your system's $PATH as immuta.exe
:
The SHA 256 checksum is available to verify the file at https://immuta-platform-artifacts.s3.amazonaws.com/cli/v1.3.0/immuta_cli_SHA256SUMS.
Immuta CLI v1.2.1 was released November 20, 2023. It fixes a bug with the integrations API.
Linux x86_64 (amd64):
Linux ARMv8 (arm64):
Darwin x86_64 (amd64):
Darwin ARMv8 (arm64):
Download and add the binary to a directory in your system's $PATH as immuta.exe
:
The SHA 256 checksum is available to verify the file at https://immuta-platform-artifacts.s3.amazonaws.com/cli/v1.2.1/immuta_cli_SHA256SUMS.
Immuta CLI v1.2.0 was released October 2, 2023. It fixes a bug with the audit export.
Linux x86_64 (amd64):
Linux ARMv8 (arm64):
Darwin x86_64 (amd64):
Darwin ARMv8 (arm64):
Download and add the binary to a directory in your system's $PATH as immuta.exe
:
The SHA 256 checksum is available to verify the file at https://immuta-platform-artifacts.s3.amazonaws.com/cli/v1.2.0/immuta_cli_SHA256SUMS.
Immuta CLI v1.2.0-1 was released August 19, 2022. It allows you to export universal audit model (UAM) events to S3.
Linux x86_64 (amd64):
Linux ARMv8 (arm64):
Darwin x86_64 (amd64):
Darwin ARMv8 (arm64):
Download and add the binary to a directory in your system's $PATH as immuta.exe
:
The SHA 256 checksum is available to verify the file at https://immuta-platform-artifacts.s3.amazonaws.com/cli/v1.2.0-1/immuta_cli_SHA256SUMS.
Immuta CLI v1.1.0 was released August 19, 2022. It allows you to overwrite existing files in output directory targets when you specify the --force
flag to clone your Immuta tenant or policies. If this --force
flag is omitted, you will receive an error when the output directory exists and is not empty.
Linux x86_64 (amd64):
Linux ARMv8 (arm64):
Darwin x86_64 (amd64):
Darwin ARMv8 (arm64):
Download and add the binary to a directory in your system's $PATH as immuta.exe
:
The SHA 256 checksum is available to verify the file at https://immuta-platform-artifacts.s3.amazonaws.com/cli/v1.1.0/immuta_cli_SHA256SUMS.
The Immuta CLI v1.0.0 was released April, 26, 2022. It includes new commands that allow users to manage sensitive data discovery.
Linux x86_64 (amd64):
Linux ARMv8 (arm64):
Darwin x86_64 (amd64):
Darwin ARMv8 (arm64):
Download and add the binary to a directory in your system's $PATH as immuta.exe
:
The SHA 256 checksum is available to verify the file at https://immuta-platform-artifacts.s3.amazonaws.com/cli/v1.0.0/immuta_cli_SHA256SUMS.
Run sensitive data discovery (SDD): The immuta sdd run
command allows you to run SDD using the CLI instead of the API or UI. You can specify data sources on which to run SDD, or you can run SDD on all data sources.
Manage patterns: The immuta sdd classifier
command and its sub commands allow you to create, search for, update, and delete sensitive data discovery rules.
Manage identification frameworks: The immuta sdd template
command and its sub commands allow you to create, search for, update, and delete sensitive data discovery frameworks. Global frameworks must be managed through the Immuta UI.
--output
or -o
flag allows you to specify yaml or json for the output.
--template
option for the immuta api
command has been changed to --outputTemplate
. Additionally, this option is now available for all commands so that users can customize the output.
version
is now a flag instead of a command.
Running immuta policy clone
when there were no policies available to clone did not indicate that a target directory was not created or updated. The CLI now prints the message No global policies available to clone
.
The verbose
option is deprecated (in favor of the --output
option).
The version
command is deprecated.
The design partner level is for SaaS customers only.
In this preview level, Immuta launches an initial limited-functionality feature with a select group of customers to solve a specific challenge. The goal of this preview level is to validate that the solution solves the challenge in a way that is valuable, usable, and feasible.
Throughout the feature development and launch processes, Product Management and Engineering meet regularly with the customer to gather feedback and help implement the feature. When the process starts, entire portions of the feature may be missing from the product, but the customer receives regular (potentially weekly) updates of the feature from the Engineering team.
Design partner level features do not have support SLAs or Immuta customer support engagement; the customer solely works with the Immuta Product team. Design partner feature functionality is subject to change, discontinuation, and discontinuation of support at Immuta’s sole discretion. Immuta makes no delivery date commitments.
Private preview features approximately match the product offered to the general public. Immuta only makes changes to the feature after gathering feedback or discovering unexpected implications of the feature.
Immuta invites customers to the private preview, and they are required to engage with Immuta Product Management to provide feedback about the feature.
Immuta makes commercially reasonable efforts to support private preview functionality; however, such support is not subject to SLA targets or processes. Immuta immediately closes support tickets that are filed and redirects customers to the Product Manager in charge of the feature. Private preview functionality is subject to change, discontinuation, and discontinuation of support at Immuta’s sole discretion.
Public preview features match the product offered to the general public. Immuta only changes the feature to address bugs.
Public preview features are fully documented on the Immuta website, but customers are expected (not required) to engage with Product Management and Customer Success to enable the feature.
Immuta makes commercially reasonable efforts to support public preview functionality; however, such support is not subject to the normal SLA targets and will not be considered priority level 1 or 2. If public preview functionality impacts or is believed to reasonably impact other fully supported functionality, the customer must disable the public preview functionality; SLA targets and processes only apply once the public preview functionality is disabled. Issues discovered (even at priority levels 3 and 4) with public preview functionality will be resolved at Immuta’s sole discretion.
GA features are complete and available to all customers. Full SLA targets and processes apply.
Use the image digests below to verify the integrity of Immuta images that you pull.
Image digests may be different than the digests shown below if you are using a registry proxy, such as JFrog Artifactory or Sonatype Nexus, to proxy requests to the Immuta container registry. Registry proxies modify the image manifest resulting in a new image digest.
Changes:
Update to immuta-deploy-tools
v2.4.6
Optimized memory usage when restoring database backups
Optimized disk usage when creating database backups
Added extraEnv
and extraVolumeMounts
to web service init containers
Added support for custom annotations for ConfigMaps and Secrets
Changes:
Web Service port is now configurable
Update to immuta-deploy-tools
v2.4.4
Only allow privileged users to drop and create database during restore
Only connect to Postgres database during restore when running as a superuser
Fix:
Fixed bug where Google Cloud credentials were not properly mounted during restore process
Changes:
Added support for <component>.image.digest
to allow image digests to be used instead of image tags.
Added endpointslices
to built-in Ingress Controller Role.
Fix:
No longer deploy database-initialize resources when restore is disabled.
Google Cloud Secret Key is no longer referenced when restore is disabled.
Changes:
Update to immuta-deploy-tools
v2.4.3
Fix:
Fix malformed YAML error during generation of database-initialize hook manifest when backup.restore.enabled
is true
Fix:
Update to immuta-deploy-tools
v2.4.2
Adds support for Azure managed identities.
Support non-superuser restore from backup taken by a superuser.
Changes:
Support for Query Engine rehydration.
Use queryEngine.rehydration.enabled
Deprecate openSSLConfig
in favor of openSSLConfigMapName
.
Where openSSLConfigMapName
is an existing Configmap that's managed outside of Helm, but located in the same namespace.
Do not manage external database backup/restore process when a superuser is not set.
Deprecate externalDatabase.backup.enabled
and externalDatabase.restore.enabled
Use backup.enabled
and backup.restore.enabled
.
Fix:
Update immuta-deploy-tools
to v2.3.1
Vulnerability fixes
Fix:
Update to immuta-deploy-tools
v2.3.0
Fixed bug where backup files would be cleaned up based on Last Modified Date instead of the timestamp in the filename.
Vulnerability fixes
Changes:
All replica counts default to 1
Database Migrations execute as init-container for internal and external metadata
Enabled Patroni Failsafe mode by default
Persistence is enabled by default
Deprecate HA Redis Cache feature
Deprecate hooks.databaseMigration
and hooks.databaseInitialize.initVars
Deprecate ingressClass
Use web.ingress.ingressClassName
or web.ingress.annotation
instead
Immuta Helm 4.11.1 includes bug fixes and stability improvements.
Fix:
Update to immuta-deploy-tools
v2.2.0.
Fixed bug where database migrations failed to execute on databases not named bometadata
.
Only set automountServiceAccountToken
on Pods when rbac.create
is enabled.
Immuta Helm 4.11.0 includes bug-fixes for database backups.
Update:
Update immuta-deploy-tools image to v2.1.9.
Immuta Helm Chart 4.10.0 contains bug fixes and stability improvements.
Fix:
Update immuta-deploy-tools
to v2.1.8.
Default to Immuta 2022.4.1.
Backups failed when tls.enabled
was set to false.
extraEnv
processing returned null if valueFrom
was used instead of value.
Use tls-secret.type
of kubernetes.io/tls
when nginxIngress.enabled
is set to false.
Base Web Ingress annotations couldn't be removed or overridden.
Couldn't disable external TLS while leaving internal TLS enabled.
Couldn't restore from a specific backup file in Helm Chart.
Immuta Helm backup failed when storageClass
did not support ReadWriteMany
.
Couldn't enable database restores by default on new Helm deployments.
Fix regression when using max-backup-count
for database backups.
Update:
Kubernetes 1.24 support.
Increase default Patroni log level to INFO
instead of WARNING
.
Immuta Helm 4.9.7 includes bug-fixes for external metadata database migrations.
Update:
Update immuta-deploy-tools image to v2.1.7.
Default to Immuta 2022.3.1.
Immuta Helm 4.9.6 includes bug-fixes for external metadata database migrations.
Update:
Update immuta-deploy-tools image to v2.1.6.
Support Immuta 2022.3.0.
Immuta Helm 4.9.5 includes bug-fixes for external metadata db and backups.
Update:
Update immuta-deploy-tools image to v2.1.5.
Default to Immuta 2022.1.1.
Fix:
Fix TLS behavior when external is disabled.
Fix restore when specifying backup file.
Fix backup.maxBackupCount
behavior. A previous version introduced a regression that ignored the value.
Immuta Helm 4.9.3 includes bug-fixes and small database initialization configuration updates.
Update:
Support passing database initialization variables to immuta-deploy-tools
.
Fix:
Fix backup.restore.allowMissingArchive
value reference typo.
Fix validation logic for external database passwords when existingSecret
is specified.
Helm 4.9.2 adds functionality to improve security context granularity.
Update:
Default to Immuta 2022.1.0.
Remove service token auto mounting.
Deprecate <component>.securityContext
in favor of <component>.podSecurityContext
.
Granular security context support.
Immuta Helm 4.9.0 includes bug-fixes and updates to various components.
Update:
Update immuta-deploy-tools image to v2.1.4
Fix:
Do not create or mount volume to /var/lib/immuta
for older versions of Immuta (<2022.1.0)
Immuta Helm 4.8.1 includes bug-fixes and enables some use-cases that were previously blocked.
Update:
Add volume to support uploading Immuta plugins for restricted OpenShift security contexts.
Add support for custom Azure blob domain for backups.
Fix:
Use credentials from existing secret when creating backups.
Remove validation requirement for external database passwords when an existing secret is provided.
Set Patroni config environment variable for interactive shell sessions.
Don't create an ODBC volume (/var/lib/immuta/odbc
) for older versions of Immuta (< 2021.4.0).
This release includes changes to support deploying Immuta on OpenShift and updates the built-in Ingress-Nginx controller to support Kubernetes 1.22+.
The Ingress-Nginx controller has been updated from v0.x to v1.x in order to support Kubernetes 1.22+. Due to breaking changes, the v1 release of Ingress-Nginx does not support Kubernetes versions older than 1.19. Users who have existing deployments on older Kubernetes clusters can set nginxIngress.controller.image.tag=v0.49.3
in the Immuta Helm values.
Update:
Upgrade Ingress-Nginx controller to v1.1.0.
Creation of Ingress resources can now be disabled.
Support configuring Patroni to use ConfigMaps for leader election (required for deployment on OpenShift).
Added pod anti-affinity rules for Redis cache Pods.
Allow annotations to be set on the Query Engine client Service.
Add Helm value cache.updateStrategy
to allow update strategy to be set for cache workloads.
Fix:
Fix for database restores from blob storage into an external database.
Fix for backup SecurityContext overrides not taking effect.
This release includes new features and other changes intended to improve the usability of the Immuta Helm Chart.
New features include the ability to use an external PostgreSQL database for Immuta metadata and the option to use Redis as a cache. Other notable improvements are the ability to set a global image registry override, support for the PodSecurityPolicy RunAsUser
rule MustRunAsNonRoot
, configurable SecurityContext runAsUser
settings for most components, and support for Kubernetes API resources that have moved out of beta.
It is now possible to use an external PostgreSQL instance as the Immuta Metadata Database when running Immuta in Kubernetes. When enabled, this functionality replaces the built-in PostgreSQL metadata database that runs in Kubernetes. This functionality is enabled by setting database.enabled=false
and passing the connection information for the PostgreSQL instance under the key externalDatabase
.
For existing deployments it is possible to migrate from the built-in database to an external database. In order to migrate, backups must be configured, and a backup should be taken immediately prior to migrating. The process of migrating can be done by running helm upgrade
with the external database Helm values and backup.restore.enabled=true
.
This functionality is compatible with Immuta 2021.3+.
There is now the option to use Redis as the cache implementation for Immuta. The primary motivation for offering this option is to enable the use of TLS for network traffic between the Immuta web service and cache pods.
In order to select Redis as the cache implementation for Immuta, set the Helm value cache.type=redis
when installing the Immuta Helm Chart.
TLS is enabled for internal network traffic by default when Redis is used, so unless tls.enabledInternal=false
is set, TLS will be used for network traffic between Immuta and Redis.
It is now possible to configure the container image registry globally for all images referenced by the Immuta Helm Chart.
The default value for global.imageRegistry
is registry.immuta.com
.
Immuta images are referenced relative to the configured image registry by adding the repository prefix immuta/
, for example registry.mycorp.com/immuta/immuta-service
.
Third-party images are referenced without the immuta/
prefix. The images that this applies to are
ingress-ngnix-controller
memcached
redis
envoyproxy-envoy-alpine
If these images are not available in the custom registry under the root prefix, it is possible to configure the image repository. This may be the case if you have pulled these images and pushed them to your registry under the immuta/
prefix.
MustRunAsNonRoot
PoliciesInit containers for initializing database and Query Engine persistent volumes no longer run as root. In addition to increasing overall security by running init containers as an unprivileged user, this also means that Immuta is now compatible with the PodSecurityPolicy RunAsUser
rule MustRunAsNonRoot
or other similar policies.
runAsUser
for Most ComponentsThe Pod SecurityContext is now configurable for all components except for Nginx Ingress. This means that the user ID that the Pods run as can now be customized by setting securityContext.runAsUser
for the components that support it. The following table shows which components are configurable for various Immuta versions.
The resources created by the Immuta Helm Chart will now use stable versions of the following resources when they are available on the Kubernetes cluster.
networking.k8s.io/v1
for Ingress resources.
batch/v1
for CronJob resources.
policy/v1
for PodDisruptionBudget resources.
Upgrading to 4.7.0 from 4.6 should be possible with minimal or no changes to the Helm values. The following section identifies any caveats or recommendations that should be taken into account when upgrading.
helm upgrade --reuse-values
not supported for upgrade from 4.6 to 4.7Due to changes in the Chart's default values.yaml
file, helm upgrade --reuse-values
does not work. If you have a saved values file, use that when calling helm upgrade
. If you don't have a saved values file, you can use helm get values
to save the Helm values locally before calling helm upgrade
.
Some values have been deprecated in this release. The following table indicates the deprecated values and the migration path for each one. Update any custom Helm values referencing the deprecated values at the earliest convenience to avoid any issues when the deprecated values are removed.
Update Kubernetes Batch API versions.
Update Kubernetes Networking API versions.
Update Kubernetes Policy API versions.
Startup init container checks now have a time out.
Support for disabling built-in database and using an external database.
Database and Query Engine initContainers
no longer run as root.
Runtime user ID is now configurable for all Pods except Nginx Ingress.
Added shared memory volume for Database and Query Engine by default.
It is now possible to set a Docker image registry globally in Helm values.
The environment variable noproxy
will now be configured such that internal network connections do not use the proxy if extraEnv
values are used to set HTTP_PROXY
or HTTPS_PROXY
.
Added option to deploy Redis with TLS instead of Memcached for the cache.
Fix:
Database and Query Engine Pods now crash and restart when the backup restore process fails.
The TLS generation hook will now regenerate TLS certs if the externalHostname
value changes.
Update:
Add support for memory-backed volumes to increase the size of /dev/shm
.
Update Helm Chart appVersion
to 2021.3.5.
This release includes an update to the default image tag for the bundled Nginx Ingress Controller.
To upgrade the Nginx Ingress Controller without upgrading the Immuta Helm Chart, you can set the following Helm values.
Update:
Update Helm Chart appVersion
to 2021.3.4.
Update ingress-nginx controller to v0.49.3
.
This release updates the Immuta Helm Chart appVersion
to 2021.2.2 and adds support for using an S3-compatible server for backup and restore. It also contains a fix for the metrics export CronJob in Immuta 2021.2+.
In order to use a custom S3 endpoint for backup and restore, new Helm values have been added. The example below shows how to configure an S3 compatible endpoint.
Update:
Update Helm Chart appVersion
to 2021.2.2.
Add blob storage endpoint support for backup storage.
Fix:
Fix Metrics CronJob errors for Immuta 2021.2+
This release includes usability and stability improvements and an update to the bundled Nginx Ingress Controller. Usability improvements include the option to use an existing Kubernetes Secret for Immuta database passwords. Stability improvements include a change in configuration for the Immuta database and Query Engine StatefulSets.
This release adds the option to use an existing Kubernetes Secret for Immuta database passwords used in the Helm installation. Using an existing Secret can be useful when you want more control over the creation of the Secret or do not want to include the sensitive values in the Immuta Helm values file.
To use an existing Kubernetes Secret, you must first create a Secret containing the required data keys.
Reference the Secret by name in the Immuta Helm values.
If you have an existing release, you can migrate to an existing Kubernetes Secret by creating the Secret with the values previously defined in your Helm values by using the following mappings.
Set the existingSecret
value and removing the password values from your Immuta Helm values file. Apply the change by running helm upgrade
for your release, referencing the values file.
This release includes a change in the default settings for Patroni, which is used in the database and Query Engine StatefulSets. This setting has been shown to improve the stability of the StatefulSets when the pods are restarted frequently due to cluster operations, such as node upgrades.
For new installations, no action is necessary to make use of this configuration change. For existing installations, the change must be applied manually to the StatefulSet pods.
Note: Replace "RELEASE_NAME" with the name of your Immuta Helm release.
Update:
Add support for using an existing Kubernetes Secret for passwords.
Enable use_pg_rewind
for Patroni by default.
Update ingress-nginx controller to v0.47.0 to mitigate CVE-2021-23017.
This release updates versions for various components.
Update:
Update Helm Chart app version to 2021.2.0.
Update immuta-deploy-tools image to 1.1.2.
Update default ingress-nginx controller image to v0.46.0.
This release adds support for Immuta 2021.2 and to allow scaling Immuta web service pods to zero.
Update:
Update container uid and gid in securityContext
for 2021.2.
Remove dependency on pgrep
and getopt
from scripts.
Allow web pod replicas to be set to zero.
This release updates the default Immuta version to 2021.1.3 and the default memcached image tag to 1.6-alpine.
Update:
Update memcached image to 1.6-alpine.
This release contains a fix for an issue where setting resource requests and limits was not possible for some containers created by the Immuta Helm Chart.
Fix:
Set configurable resource limits for all containers and init containers
This release contains updates that enable the configuration of options that were previously not exposed in the Helm Chart.
The Immuta Fingerprint service configuration can now be set in Helm values. For example, to set the worker_timeout
option to a value of 300, set the following values.
The log level for the Immuta Fingerprint service can also be configured. Valid values include DEBUG
, INFO
, WARNING
, ERROR
, and CRITICAL
.
Feature:
Add ability to pass in configuration for Immuta Fingerprint service
Fix:
Add port 8008 to Database and Query Engine Endpoints
When upgrading to 4.6.2 with nginxIngress.enabled
set to true
, a new ConfigMap was introduced to be used by the NGINX Ingress Controller for leader election. This will cause the old ConfigMap, named ingress-controller-leader-immuta-<RELEASE>-ingress
, to be orphaned. This will not affect the operation of Immuta and may be removed by running
Fix:
When using --reuse-values
coming from 4.5.x charts, extraEnv
value throws a templating error.
Use Immuta config item publicPostgres.useSSL
instead of publicPostgres.ssl
starting with Immuta Version 2020.3.
Adopt nginx-ingress leader election ConfigMap into the chart when using Optional Ingress Controller component.
Feature:
Set log_error_verbosity = TERSE
in Postgres configuration.
Update default version to 2020.4.0.
Add port 8008 to primary database and query-engine services.
Add ability to set annotations on all service accounts.
Set .spec.terminationGracePeriodSeconds
for all Immuta pods.
Update Query Engine readiness and liveness probes to use Patroni REST API endpoints.
Update Database readiness and liveness probes to use Patroni REST API endpoints.
Fix:
Database password is no longer used in Query Engine init-container.
Feature:
Add support for LDAPS-backed Query Engine Authentication.
Fix:
Web Service pods now wait for database migrations to execute before startup.
This release contains a fix for a race condition introduced in 4.5.3 when performing a new install.
Fix:
Removed Endpoint resource for Database and Query Engine components to prevent race condition with Service. Endpoints are now created by Database and Query Engine Service resource.
This release contains a few fixes and updates the default Immuta application version to 2020.2.8.
Feature:
Update appVersion
to 2020.2.8.
Fix:
Support EndpointSlices for Database and Immuta Query Engine in Kubernetes 1.17+.
This release contains a few fixes and updates the default Immuta application version to 2020.2.7.
Feature:
Update appVersion
to 2020.2.7.
Update default values for Immuta Query Engine to support Elastic.
Fix:
Helm hooks fail to run with helm older than 3.2.0.
TLS Ciphers used in NGINX Ingress Controller incompatibility with default TLS cipher suites set in Databricks.
This release contains a fix for a bug introduced with the last release that caused helm install
to timeout and fail when used with the --wait
flag.
If you are using Argo CD to deploy the Immuta Helm Chart, then you may notice that the TLS secret will be marked OutOfSync (requires pruning). The TLS secret (which is used for the encryption of inter-pod network traffic) should not be pruned. Update the Helm values with the following so that the TLS secret can be monitored as a resource without the risk of unwanted pruning.
Fixes:
Fix issue with TLS generation and the helm install --wait
flag.
The Immuta Helm Chart now supports deployment using Argo CD. Prior to this, the TLS generation hook would create a Secret that was not tracked by Helm. In Argo CD this resource would appear to need pruning. There was also an issue with the database and Query Engine endpoints, in which they would appear to be out of sync, but syncing them would remove the runtime changes that were being applied by Patroni. These issues have been resolved, and Argo CD is now supported.
For Argo CD versions older than 1.7.0 you must use the following Helm values in order for the TLS generation hook to run successfully.
Starting with Argo CD version 1.7.0 the default Immuta Helm Chart values can be used.
Setting the Helm value nginxIngress.controller.service.isInternal
will now cause an internal Azure load balancer to be created for nginx ingress.
externalTrafficPolicy
When upgrading an existing Helm release from chart version <=4.4
that was using the default values tls.enabled=true
and tls.create=true
, you must first annotate and label the Immuta TLS Secret so that it can be adopted by Helm.
You will need to complete these steps if you encounter either of the following errors when running the helm upgrade
command.
To resolve these upgrade errors, run the following commands, being sure to substitute the proper Helm release name and namespace.
After this, you can proceed to run helm upgrade
.
Feature:
Refactored Helm Chart hooks to work with Argo CD.
Updated Helm Chart description.
Update web pod annotations so that password changes cause a rolling restart.
Upgrade ingress-nginx to 0.34.1.
Support setting externalTrafficPolicy
on the nginx ingress Service.
Update nginx ingress Service to include Azure annotations.
Bug:
Fix issue with release names that contain periods.
Bug:
Fix fingerprint configuration when TLS is disabled.
It is now possible to set pod annotations and labels at a global level. When set, these labels and annotations will be used for all pods that the Immuta Helm Chart creates. Pod labels and annotations can be set using the Helm values global.podAnnotations
and global.podLabels
to a map of string to string.
Labels and annotations can also be set individually for each component in the Immuta Helm Chart. To set labels and annotations for an individual component, set the Helm values <componentName>.podAnnotations
and <componentName>.podLabels
to a map of string to string.
Feature:
Support labels/annotations on all pods.
Bug:
Fix for Query Engine pod referencing image repository from database values.
Cleanup:
Remove the option to configure Data Source CA certificates using a ConfigMap.
nodeSelector
and tolerations
It is now possible to set custom nodeSelector
and tolerations
for each component in the Immuta Helm Chart.
Feature:
Support setting nodeSelector
and tolerations
on all pods.
Preview level | Access | Support | Documentation | Contact |
---|
Image | Digest |
---|
New Setting | Description |
---|
New Setting | Description |
---|
It is now possible to deploy the Immuta Helm Chart on OpenShift Kubernetes clusters. For more details see .
When Redis is selected as the cache for Immuta, the Immuta Web Service pods will contain an additional container that runs as an ambassador sidecar; the envoy container is named "cache-proxy-sidecar." In this configuration, kubectl logs
commands must include the flag --container=service
in order to access logs for the Immuta Web Service.
Immuta Version | Components |
---|
Deprecated Value | Replacement Value |
---|
This release makes it possible to increase the size of /dev/shm
in the Database and Query Engine Pods. This functionality makes use of memory-backed .
The project has released a few updates since v0.47.0
. This release updates the default version to v0.49.3
, which includes an update to Alpine Linux v3.14.2
. This update addresses CVE-2021-3711, which v0.47.0
was vulnerable to.
Note: This is an example showing the required data keys and some sample values. For more details on creating Secrets in Kubernetes, see the .
Helm Value | Secret Data Key |
---|
The project released an update to mitigate a vulnerability in Nginx. We've updated the bundled ingress controller to this new release. More details are available in this .
The bundled version of has been upgraded to 0.34.1. In addition to upgrading the default version, the cluster scoped resources that used to be created (ClusterRole and ClusterRoleBinding) are no longer required and have been removed.
A new value was added to set the externalTrafficPolicy
on the nginx ingress Service. Setting this value to "Local" can be useful for preserving client IP addresses. See the for more information on preserving the client source IP.
To set a custom nodeSelector
, set the Helm value for <componentName>.nodeSelector
to a valid nodeSelector
. See the for more details.
To set a custom tolerations
, set the Helm value for <componentName>.tolerations
to a valid tolerations
. See the for more details.
registry.immuta.com/immuta/immuta-service:2023.4.0 |
|
registry.immuta.com/immuta/immuta-service:2023.4.1 |
|
registry.immuta.com/immuta/immuta-service:2023.4.2 |
|
registry.immuta.com/immuta/immuta-service:2023.4.3 |
|
registry.immuta.com/immuta/immuta-service:2023.4.4 |
|
registry.immuta.com/immuta/immuta-service:2023.4.5 |
|
registry.immuta.com/immuta/immuta-service:2023.4.6 |
|
registry.immuta.com/immuta/immuta-service:2023.4.7 |
|
registry.immuta.com/immuta/immuta-service:2023.4.8 |
|
registry.immuta.com/immuta/immuta-db:2023.4.0 |
|
registry.immuta.com/immuta/immuta-db:2023.4.1 |
|
registry.immuta.com/immuta/immuta-db:2023.4.2 |
|
registry.immuta.com/immuta/immuta-db:2023.4.3 |
|
registry.immuta.com/immuta/immuta-db:2023.4.4 |
|
registry.immuta.com/immuta/immuta-db:2023.4.5 |
|
registry.immuta.com/immuta/immuta-db:2023.4.6 |
|
registry.immuta.com/immuta/immuta-db:2023.4.7 |
|
registry.immuta.com/immuta/immuta-db:2023.4.8 |
|
registry.immuta.com/immuta/immuta-fingerprint:2023.4.0 |
|
registry.immuta.com/immuta/immuta-fingerprint:2023.4.1 |
|
registry.immuta.com/immuta/immuta-fingerprint:2023.4.2 |
|
registry.immuta.com/immuta/immuta-fingerprint:2023.4.3 |
|
registry.immuta.com/immuta/immuta-fingerprint:2023.4.4 |
|
registry.immuta.com/immuta/immuta-fingerprint:2023.4.5 |
|
registry.immuta.com/immuta/immuta-fingerprint:2023.4.6 |
|
registry.immuta.com/immuta/immuta-fingerprint:2023.4.7 |
|
registry.immuta.com/immuta/immuta-fingerprint:2023.4.8 |
|
registry.immuta.com/immuta/immuta-deploy-tools:2.3.1 |
|
registry.immuta.com/immuta/immuta-deploy-tools:2.4.0 |
|
registry.immuta.com/immuta/immuta-deploy-tools:2.4.2 |
|
registry.immuta.com/immuta/immuta-deploy-tools:2.4.3 |
|
| Key/value dictionary of variables passed to database initialization process. |
| Pod level security features on all pods. |
| Container level security features on all containers. |
| Pod level security features for individual component. |
| Container level security features for individual component. |
Any |
|
2021.2+ |
|
2021.4+ |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Invitation only | None | None | Product Management (required) |
Invitation only | Best effort | Yes | Product Management (required) |
Customer request | Limited SLAs | Yes | Customer Success and Sales Engineering |
No action required | Full SLAs | Yes | Customer Success and Sales Engineering |
The table below outlines the available features currently in preview for this release and when they were introduced.
Feature | Availability | Introduced |
---|---|---|
Allow masked columns as input for row-level policies in the Snowflake and Databricks Unity Catalog integrations
Public preview
September 2023 (v2023.3)
Private preview
September 2022 (v2022.3)
Public preview
July 2022 (v2022.2)
Private preview
October 2022 (v2022.3)
Public preview
2021
Public preview
November 2021 (v2021.4)
Private preview
October 2022 (v2022.4)
Public preview
2021
Private preview
December 2022 (v2022.5)