Merge branch 'main' into feat-ros-8.2

Author: dwdougherty

assets/css/index.css

@@ -23,16 +23,28 @@ section.prose {
   @apply font-geist
 }
 
-.prose h1,
-.prose h3,
-.prose h4,
-.prose h5,
-.prose h6 {
-  @apply font-normal;
+.prose h1 {
+  @apply text-4xl font-normal break-words;
 }
 
 .prose h2 {
-  @apply text-lg font-medium pb-3 border-b border-b-redis-pen-700 border-opacity-50;
+  @apply text-2xl font-medium pb-3 border-b border-b-redis-pen-700 border-opacity-50;
+}
+
+.prose h3 {
+  @apply text-xl font-semibold;
+}
+
+.prose h4 {
+  @apply text-lg font-medium;
+}
+
+.prose h5 {
+  @apply text-base font-medium;
+}
+
+.prose h6 {
+  @apply text-sm font-medium;
 }
 
 .prose p, .prose ol, .prose ul {
@@ -47,10 +59,6 @@ section.prose {
   @apply bg-none font-monogeist;
 }
 
-.prose h1 {
-  @apply text-4xl break-words;
-}
-
 .prose h1[id],
 .prose h2[id],
 .prose h3[id],

config.toml

@@ -55,7 +55,7 @@ rdi_redis_gears_version = "1.2.6"
 rdi_debezium_server_version = "2.3.0.Final"
 rdi_db_types = "cassandra|mysql|oracle|postgresql|sqlserver"
 rdi_cli_latest = "latest"
-rdi_current_version = "1.12.1"
+rdi_current_version = "1.12.2"
 
 [params.clientsConfig]
 "Python"={quickstartSlug="redis-py"}

content/glossary/_index.md

@@ -82,6 +82,26 @@ If there is an active pipeline, upgrade RDI on the active VM first.
 This will cause a short pipeline downtime of up to two minutes. 
 Afterwards, upgrade RDI on the passive VM. This will not cause any downtime.
 
+{{< warning >}}
+When upgrading from RDI < 1.8.0 to RDI >= 1.8.0 in a VM HA setup, both RDI instances may incorrectly consider themselves active after the upgrade. This occurs because the upgrade process doesn't change the cluster id value from its default `cluster-1`, causing both clusters to assume they are the active cluster.
+
+**Symptoms:**
+
+- The upgraded passive node will start collector and processor components
+- Collector may enter a crash loop as it fails to connect to the source
+- Both clusters will restart in a loop
+
+**Workaround:**
+
+After upgrading, manually set a unique cluster ID for one of the installations (preferably on the passive instance):
+
+1. Locate the RDI configuration file on the VM host. The file is typically located at `/etc/rdi/rdi-sys-config.yaml`.
+2. Open the configuration file in a text editor. For example:
+
+   ```bash
+   sudo nano /etc/rdi/rdi-sys-config.yaml
+{{< /warning >}}
+
 ## Upgrading a Kubernetes installation
 
 Follow the steps below to upgrade an existing

content/integrate/redis-data-integration/installation/upgrade.md

@@ -0,0 +1,34 @@
+---
+Title: Redis Data Integration release notes 1.12.2 (July 2025)
+alwaysopen: false
+categories:
+- docs
+- operate
+- rs
+description: |
+    RDI Collector API now properly supports MariaDB.
+    Extend adding custom labels and annotations to all resources in the RDI Helm chart.
+linkTitle: 1.12.2 (July 2025)
+toc: 'true'
+weight: 980
+---
+
+{{< note >}}This maintenance release replaces the 1.12.1 release.{{< /note >}}
+
+RDI’s mission is to help Redis customers sync Redis Enterprise with live data from their slow disk-based databases to:
+
+- Meet the required speed and scale of read queries and provide an excellent and predictable user experience.
+- Save resources and time when building pipelines and coding data transformations.
+- Reduce the total cost of ownership by saving money on expensive database read replicas.
+
+RDI 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.
+It 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.
+
+## Headlines
+
+-   RDI Collector API now properly supports MariaDB.
+-   Extend adding custom labels and annotations to all resources in the RDI Helm chart. Includes the webhook certificate management jobs.
+
+## Limitations
+
+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.

content/integrate/redis-data-integration/release-notes/rdi-1-12-2.md

@@ -87,3 +87,29 @@ The RDI operator has been significantly enhanced in the following areas:
 ## Limitations
 
 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.
+
+## Known Issues
+
+### High Availability upgrade issue
+
+When upgrading from RDI < 1.8.0 to RDI >= 1.8.0 in an HA setup, both RDI instances may incorrectly consider themselves active after the upgrade. This occurs because the upgrade process doesn't update the `rdi:ha:lock` value from the legacy `cluster-1` identifier, causing both clusters to assume they are the active cluster.
+
+**Symptoms:**
+
+- The upgraded passive node will start collector and processor components
+- Collector may enter a crash loop as it fails to connect to the source
+- Both clusters will restart in a loop
+
+**Workaround:**
+
+After upgrading, manually set a unique cluster ID for one of the installations by editing the configmap:
+
+```bash
+kubectl edit cm -n rdi rdi-sys-config
+```
+
+Then add the following line to distinguish between the clusters:
+
+```bash
+RDI_CLUSTER_ID: cluster-2
+```

content/integrate/redis-data-integration/release-notes/rdi-1-8-0.md

@@ -89,6 +89,15 @@ roleRef:
   apiGroup: rbac.authorization.k8s.io
 ```
 
+{{<note>}}
+**Alternative approach**: Instead of creating individual `Role` objects for each namespace, you can create a single `ClusterRole` and bind it with multiple `RoleBinding` objects. This reduces the number of objects and simplifies role management.
+
+To use this approach:
+1. Change `kind: Role` to `kind: ClusterRole` in the role definition above
+2. Change `roleRef.kind: Role` to `roleRef.kind: ClusterRole` in the role binding definition above
+3. Apply the ClusterRole once globally, then apply a RoleBinding in each managed namespace
+{{</note>}}
+
 Apply the files, replacing `<managed-namespace>` with your own values:
 
 ```sh

content/operate/kubernetes/re-clusters/multi-namespace.md

@@ -35,7 +35,17 @@ For each database, you can choose from these data eviction policies:
 
 ## Prevent data eviction
 
-Redis Cloud supports [Auto Tiering]({{< relref "/operate/rs/databases/auto-tiering/" >}}) 
+Redis Cloud supports [Auto Tiering]({{< relref "/operate/rs/databases/auto-tiering/" >}})
 to prevent data eviction but maintain high performance.
 
 Auto Tiering can extend your database across RAM and Flash Memory and intelligently manage "hot" (active) data in RAM and "cold" (less active) data in Flash memory (SSD).
+
+## Active-Passive replication considerations
+
+When using [Active-Passive replication]({{< relref "/operate/rc/databases/migrate-databases#sync-using-active-passive" >}}), eviction and expiration only operate on the source (active) database. The target database does not evict or expire data while Active-Passive is enabled. 
+
+Do not write to the target database while Active-Passive is enabled. Doing so can cause the following issues:
+
+- The target database cannot rely on eviction or expiration to manage local writes, requiring sufficient memory to handle both replicated data and local writes.
+- Local writes create differences between the source and target databases, causing replicated commands to behave differently on each database.
+- Inconsistent data can cause replicated commands to fail with errors, which will cause the synchronization process to exit and break replication.

content/operate/rc/databases/configuration/data-eviction-policies.md

@@ -56,7 +56,7 @@ Before you use Active-Passive, be aware of the following limitations:
 
 - An error will appear when syncing the two databases if the source and target databases are hosted on different Redis Cloud accounts. [Contact support](https://redis.io/support/) if you want to migrate a database between accounts using Active-Passive.
 
-- As long as Active-Passive is enabled, data in the target database will not expire and will not be evicted regardless of the set [data eviction policy]({{< relref "/operate/rc/databases/configuration/data-eviction-policies.md" >}}). We recommend that you turn off Active-Passive after the databases are synced. 
+- As long as Active-Passive is enabled, data in the target database will not expire and will not be evicted regardless of the set [data eviction policy]({{< relref "/operate/rc/databases/configuration/data-eviction-policies.md" >}}). **Do not write to the target database while Active-Passive is enabled.** We recommend that you turn off Active-Passive after the databases are synced. 
 
 - Turning on Active-Passive will flush the target database. Make sure that your target database has no important data before you turn on Active-Passive.
 {{< /note >}}
@@ -135,7 +135,11 @@ Follow these detailed steps to migrate data using Active-Passive syncing:
 
     {{<image filename="images/rc/migrate-data-status-synced.png" alt="When the data is migrated, the target database status displays `Synced`." width=100px >}}
 
-Active-Passive sync lets you migrate data while apps and other connections are using the source database.  Once the data is migrated, you should migrate active connections to the target database.  
+Active-Passive sync lets you migrate data while apps and other connections are using the source database.  Once the data is migrated, you should migrate active connections to the target database.
+
+{{< warning >}}
+Do not write to the target database until turning off Active-Passive. Writing to the target database of an Active-Passive setup can cause data consistency issues and replication failures. See [Active-Passive replication considerations]({{< relref "/operate/rc/databases/configuration/data-eviction-policies.md#active-passive-replication-considerations" >}}) for more information.
+{{< /warning >}}
 
 ## Active-Passive memory requirements