{
  "schema_version": 2,
  "id": "integrate/redis-data-integration/release-notes/rdi-1-4-3",
  "title": "Redis Data Integration release notes 1.4.3 (December 2024)",
  "url": "https://redis.io/docs/latest/integrate/redis-data-integration/release-notes/rdi-1-4-3/",
  "summary": "Installation on Kubernetes with a Helm chart. Improvements for installation on VMs.",
  "tags": [
    "docs",
    "operate",
    "rs"
  ],
  "last_updated": "2026-09-18T16:47:10+01:00",
  "page_type": "content",
  "content_hash": "f7937bfb9840568946fe6f2e5c939ed5cbdf6af60c3fc397f142a2ee962c9403",
  "sections": [
    {
      "id": "overview",
      "title": "Overview",
      "role": "overview",
      "text": "> This maintenance release replaces the 1.4.2 release.\n\nRDI’s mission is to help Redis customers sync Redis Enterprise with live data from their slow disk-based databases to:\n\n- Meet the required speed and scale of read queries and provide an excellent and predictable user experience.\n- Save resources and time when building pipelines and coding data transformations.\n- Reduce the total cost of ownership by saving money on expensive database read replicas.\n\nRDI keeps the Redis cache up to date with changes in the primary database, using a [_Change Data Capture (CDC)_](https://en.wikipedia.org/wiki/Change_data_capture) mechanism.\nIt also lets you _transform_ the data from relational tables into convenient and fast data structures that match your app's requirements. You specify the transformations using a configuration system, so no coding is required."
    },
    {
      "id": "headlines",
      "title": "Headlines",
      "role": "content",
      "text": "-   Installation on [Kubernetes](https://redis.io/docs/latest/integrate/redis-data-integration/installation/install-k8s) using a [Helm chart](https://helm.sh/docs/). You can install on [OpenShift](https://docs.openshift.com/) or other flavours of K8s using Helm.\n\n- Improvements for installation on VMs:\n\t- Installer checks if the OS firewall is enabled on Ubuntu and RHEL.\n\t- Installer verifies DNS resolution from RDI components.\n\t- Installer provides log lines from components that failed during RDI deployment if a problem occurs.\n\t- Improved verification of RDI installation.\n\t- Installer verifies if the RDI database is in use by another instance of RDI.\n\t- Installer checks and warns if any [`iptables`](https://www.netfilter.org/projects/iptables/index.html) rules are set.\n\t- Improved message when RDI tries to connect to its Redis database with invalid TLS keys."
    },
    {
      "id": "issues-fixed",
      "title": "Issues fixed",
      "role": "content",
      "text": "- **RDSC-2963**: Helm chart `rdiSysSecret` does not create an empty secret if you are not using a password.\n- **RDSC-2729**: Use Debezium Server 2.7.3 and remove Prometheus.\n- **RDSC-2333**: Ensure the installer creates the context file correctly.\n- **RDSC-2806**: Remove incorrectly created deployment.\n- **RDSC-2729**: Fix `processors` `null` instead of `{}`.\n- **RDSC-2905**: Fix DNS check with multiple IP addresses.\n- **RDSC-2845**: RDI Helm chart release is set with `tag: 0.0.0`, but this should be the current release."
    },
    {
      "id": "limitations",
      "title": "Limitations",
      "role": "limits",
      "text": "RDI can write data to a Redis Active-Active database. However, it doesn't support writing data to two or more Active-Active replicas. Writing data from RDI to several Active-Active replicas could easily harm data integrity as RDI is not synchronous with the source database commits."
    }
  ],
  "examples": []
}