Merge branch 'main' into release-rs-fuya-fuya

Author: rrelledge

.github/workflows/main-staging.yml

@@ -33,23 +33,92 @@ jobs:
             echo "ERROR: Invalid branch name ${{ github.ref_name }}!"
             exit 1
           fi
-    - name: Configure Hugo
+
+    - name: Install dependencies
+      run: make deps
+
+    - name: Build out all versions
       run: |
+        set -x
+
+        function setBaseUrl() {
           if [[ "${{ github.ref_name }}" == "main" ]]
           then
             hugo_root_path=docs/staging/dev
           elif [[ "${{ github.ref_name }}" == "latest" ]]
           then
-            hugo_root_path="docs/latest" 
+            hugo_root_path="docs/latest"
           elif [[ "${{ endsWith(github.ref_name, '-build') }}" == "true" ]]
           then
             hugo_root_path=`echo docs/version/${{ github.ref_name }} | sed 's/-build$//'`
           else
             hugo_root_path=docs/staging/${{ github.ref_name }}
           fi \
           && sed -i "s#baseURL = \"https://redis.io\"#baseURL = \"https://redis.io/$hugo_root_path\"#g" config.toml
-    - name: Install dependencies and run Hugo
-      run: make all
+        }
+
+        setBaseUrl
+        kubernetes_versions=($(find content/operate/kubernetes/ -maxdepth 1 -type d -regex ".*[0-9-]" | awk -F/ '{print $NF}'))
+        rs_versions=($(find content/operate/rs/ -maxdepth 1 -type d -regex ".*[0-9-]" | awk -F/ '{print $NF}'))
+
+        # build latest
+        for version in "${kubernetes_versions[@]}"; do
+          rm -r "content/operate/kubernetes/${version}"
+        done
+        for version in "${rs_versions[@]}"; do
+          rm -r "content/operate/rs/${version}"
+        done
+        make all
+
+        git checkout .
+
+        # build all versions
+        for version in "${kubernetes_versions[@]}"; do
+
+          setBaseUrl
+
+          # for each version, remove all other versions before building
+          versions_to_remove=($(echo "${kubernetes_versions[@]}" "${version}" | tr ' ' '\n' | sort | uniq -u))
+          for version_to_remove in "${versions_to_remove[@]}"; do
+            rm -r "content/operate/kubernetes/${version_to_remove}"
+          done
+
+          cp -r "content/operate/kubernetes/${version}"/* content/operate/kubernetes/
+          rm -r "content/operate/kubernetes/${version}"
+          sed -i 's/id="versionSelectorKubernetesValue" class="version-selector-control">latest/id="versionSelectorKubernetesValue" class="version-selector-control">v'"${version}"'/' layouts/partials/docs-nav.html
+          sed -i 's/linkTitle: '"${version}"'/linkTitle: Redis for Kubernetes/' content/operate/kubernetes/_index.md
+
+          # inject replace command in meta-links to make sure editURL and issuesURL point to right version
+          sed -i "11i \{\{ \$gh_file = replaceRE \`\^operate\/kubernetes\/\` \"operate\/kubernetes\/$version\/\" \$gh_file }}" layouts/partials/meta-links.html
+
+          hugo -d "kubernetes-${version}"
+
+          git checkout .
+        done
+
+        for version in "${rs_versions[@]}"; do
+
+          setBaseUrl
+
+          # for each version, remove all other versions before building
+          versions_to_remove=($(echo "${rs_versions[@]}" "${version}" | tr ' ' '\n' | sort | uniq -u))
+          for version_to_remove in "${versions_to_remove[@]}"; do
+            rm -r "content/operate/rs/${version_to_remove}"
+          done
+
+          cp -r "content/operate/rs/${version}"/* content/operate/rs/
+          rm -r "content/operate/rs/${version}"
+          sed -i 's/id="versionSelectorRsValue" class="version-selector-control">latest/id="versionSelectorRsValue" class="version-selector-control">v'"${version}"'/' layouts/partials/docs-nav.html
+          sed -i 's/linkTitle: '"${version}"'/linkTitle: Redis Software/' content/operate/rs/_index.md
+
+          # inject replace command in meta-links to make sure editURL and issuesURL point to right version
+          sed -i "11i \{\{ \$gh_file = replaceRE \`\^operate\/rs\/\` \"operate\/rs\/$version\/\" \$gh_file }}" layouts/partials/meta-links.html
+
+          hugo -d "rs-${version}"
+
+          git checkout .
+        done
+
     - name: List client examples
       run: ls "${{ github.workspace }}/examples"
     - name: List files to be published
@@ -80,5 +149,12 @@ jobs:
             bucket_path=staging/${{ github.ref_name }}
           fi \
           && ./google-cloud-sdk/bin/gsutil -m rsync -r -c -j html -d ${{ github.workspace }}/public gs://$BUCKET/$bucket_path
+
+          versioned_builds=($(find . -type d -regex ".*[0-9-]" -maxdepth 1 | sed -E 's/^.\///'))
+          for versioned_build in "${versioned_builds[@]}"; do
+            product=$(grep -Eo '[a-zA-Z]+' <<< $versioned_build)
+            gsutil -m rsync -r -c -j html -d "${{ github.workspace }}/${versioned_build}/operate/${product}" "gs://${BUCKET}/${versioned_build}/operate/${product}"
+          done
+
     - name: End
       run: echo "This job's status is ${{ job.status }}."

content/commands/ft.search/index.md

@@ -478,6 +478,8 @@ orders the results by the value of this attribute. This applies to both text and
 <summary><code>LIMIT first num</code></summary>
 
 limits the results to the offset and number of results given. Note that the offset is zero-indexed. The default is 0 10, which returns 10 items starting from the first result. You can use `LIMIT 0 0` to count the number of documents in the result set without actually returning them.
+
+**`LIMIT` behavior**:  If you use the `LIMIT` option without sorting, the results returned are non-deterministic, which means that subsequent queries may return duplicated or missing values. Add `SORTBY` with a unique field, or use `FT.AGGREGATE` with the `WITHCURSOR` option to ensure deterministic result set paging.
 </details>
 
 <details open>

content/develop/connect/insight/release-notes/v.2.40.0.md

@@ -15,7 +15,7 @@ This is the General Availability (GA) release of RedisInsight 2.40.
 ### Details
 
 **Features and improvements**
-- [#2879](https://github.com/RedisInsight/RedisInsight/pull/2879) UX improvements to simplify in-app provisioning of a free [Redis Cloud](https://redis.com/comparisons/oss-vs-enterprise/?utm_source=redisinsight&utm_medium=rel_notes&utm_campaign=2_40) database. Create a new database with a preselected cloud vendor and region by using the recommended sign-up settings. You can manage your database by signing in to the [Redis Cloud console](https://app.redislabs.com/#/databases?utm_source=redisinsight&utm_medium=rel_notes&utm_campaign=2_40)
+- [#2879](https://github.com/RedisInsight/RedisInsight/pull/2879) UX improvements to simplify in-app provisioning of a free [Redis Cloud](https://redis.com/comparisons/oss-vs-enterprise/?utm_source=redisinsight&utm_medium=rel_notes&utm_campaign=2_40) database. Create a new database with a preselected cloud vendor and region by using the recommended sign-up settings. You can manage your database by signing in to the [Redis Cloud console](https://cloud.redis.io/#/databases?utm_source=redisinsight&utm_medium=rel_notes&utm_campaign=2_40)
 - [#2851](https://github.com/RedisInsight/RedisInsight/pull/2851) See plan, cloud vendor, and region details after successfully provisioning your free [Redis Cloud](https://redis.com/comparisons/oss-vs-enterprise/?utm_source=redisinsight&utm_medium=rel_notes&utm_campaign=2_40) database
 - [#2882](https://github.com/RedisInsight/RedisInsight/pull/2882) Optimizations when uploading large text files with the list of Redis commands, available under bulk actions in Browser
 - [#2808](https://github.com/RedisInsight/RedisInsight/pull/2808) Enhanced security measurement to no longer display existing passwords for Redis Sentinel in plain text

content/develop/interact/search-and-query/query/vector-search.md

@@ -46,9 +46,9 @@ You can read more about the `PARAMS` argument in the [FT.SEARCH]({{< baseurl >}}
 
 The following example shows you how to query for three bikes based on their description embeddings, and by using the field alias `vector`. The result is returned in ascending order based on the distance. You can see that the query only returns the fields `__vector_score` and `description`. The field `__vector_score` is present by default. Because you can have multiple vector fields in your schema, the vector score field name depends on the name of the vector field. If you change the field name `@vector` to `@foo`, the score field name changes to `__foo_score`.
 
-```
+{{< clients-example query_vector vector1 >}}
 FT.SEARCH idx:bikes_vss "(*)=>[KNN 3 @vector $query_vector]" PARAMS 2 "query_vector" "Z\xf8\x15:\xf23\xa1\xbfZ\x1dI>\r\xca9..." SORTBY "__vector_score" ASC RETURN 2 "__vector_score" "description" DIALECT 2
-```
+{{< /clients-example >}}
 
 <!-- Python query>
 query = (
@@ -60,7 +60,7 @@ query = (
 </!-->
 
 {{% alert title="Note" color="warning" %}}
-The binary value of the query vector is significantly shortened in this example.
+The binary value of the query vector is significantly shortened in the CLI example above.
 {{% /alert  %}}
 
 
@@ -93,9 +93,9 @@ By default, [`FT.SEARCH`]({{< baseurl >}}/commands/ft.search/) returns only the
 
 The example below shows a radius query that returns the description and the distance within a radius of `0.5`. The result is sorted by the distance.
 
-```
+{{< clients-example query_vector vector2 >}}
 FT.SEARCH idx:bikes_vss "@vector:[VECTOR_RANGE 0.5 $query_vector]=>{$YIELD_DISTANCE_AS: vector_dist}" PARAMS 2 "query_vector" "Z\xf8\x15:\xf23\xa1\xbfZ\x1dI>\r\xca9..." SORTBY vector_dist ASC RETURN 2 vector_dist description DIALECT 2
-```
+{{< /clients-example >}}
 
 <!-- Python query>
 query = (

content/integrate/amazon-bedrock/set-up-redis.md

@@ -75,9 +75,9 @@ To set up a Redis Cloud instance for Bedrock, you need to:
 
     {{<image filename="images/rc/subscription-new-flexible-setup-general.png" width="75%" alt="The General settings of the Setup tab." >}}
 
-1. In the **Version** section, select **Redis 7.2**.
+1. In the **Version** section, select **Redis 7.2** or **Redis 7.4**.
 
-    {{<image filename="images/rc/subscription-new-flexible-version-section.png"  alt="Version selection between Redis 6.2 and 7.2" >}}
+    {{<image filename="images/rc/subscription-new-flexible-version-section.png"  alt="Version selection between Redis 6.2, 7.2, and 7.4" >}}
 
 1. In the **Advanced options** section, select Multi-AZ to ensure [high-availability]({{< relref "/operate/rc/databases/configuration/high-availability" >}}). 
 

content/integrate/redis-data-integration/data-pipelines/data-pipelines.md

@@ -28,8 +28,8 @@ However, you can also provide your own custom transformation [jobs](#job-files)
 for each source table, using your own data mapping and key pattern. You specify these
 jobs declaratively with YAML configuration files that require no coding.
 
-The data tranformation involves two separate stages. First, the data ingested by
-[Debezium](https://debezium.io/) is automatically transformed to a JSON format. Then,
+The data tranformation involves two separate stages. First, the data ingested
+during CDC is automatically transformed to a JSON format. Then,
 this JSON data gets passed on to your custom transformation for further processing.
 
 You can provide a job file for each source table you want to transform, but you
@@ -48,7 +48,7 @@ data in Redis as
 
 The diagram below shows the flow of data through the pipeline:
 
-{{< image filename="/images/rdi/data-transformation-pipeline.png" >}}
+{{< image filename="/images/rdi/RDIPipeDataflow.drawio.svg" >}}
 
 ## Pipeline configuration
 

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

@@ -43,6 +43,19 @@ use [`iptables`](https://www.netfilter.org/projects/iptables/index.html) to
                      /^:[A-Z]+ [^-]/ { print $1 " ACCEPT" ; }
                      /COMMIT/ { print $0; }' | sudo iptables-restore
 ```
+
+You may encounter problems if you use `iptables` v1.6.1 and earlier in
+`nftables` mode. Use `iptables` versions later than v1.6.1 or enable the `iptables`
+legacy mode with the following commands:
+
+```bash
+update-alternatives --set iptables /usr/sbin/iptables-legacy
+update-alternatives --set ip6tables /usr/sbin/ip6tables-legacy
+```
+
+Also, `iptables` versions 1.8.0-1.8.4 have known issues that can prevent RDI
+from working, especially on RHEL 8. Ideally, use `iptables` v1.8.8, which is
+known to work correctly with RDI.
 {{< /note >}}
 
 The supported OS versions for RDI are:

content/integrate/redis-data-integration/observability.md

@@ -39,7 +39,7 @@ command from the CLI.{{< /note >}}
 
 ## Collector metrics
 
-The endpoint for the collector metrics is `https://<RDI_HOST>:9121/metrics/collector-source`
+The endpoint for the collector metrics is `https://<RDI_HOST>/metrics/collector-source`
 
 These metrics are divided into three groups:
 
@@ -49,7 +49,7 @@ These metrics are divided into three groups:
 
 ## Stream processor metrics
 
-The endpoint for the stream processor metrics is `https://<RDI_HOST>:9121/metrics/rdi`
+The endpoint for the stream processor metrics is `https://<RDI_HOST>/metrics/rdi`
 
 RDI reports metrics during the two main phases of the ingest pipeline, the *snapshot*
 phase and the *change data capture (CDC)* phase. (See the

content/operate/kubernetes/deployment/openshift/openshift-operatorhub.md

@@ -29,7 +29,7 @@ To see which version of Redis Enterprise for Kubernetes supports your OpenShift
 
     Only one namespace per operator is supported.
 
-4. Update the **channel** with the version you're installing. 
+4. Update the **channel** with the version you're installing.
 
     For more information about specific versions, see the [release notes]({{< relref "/operate/kubernetes/release-notes/" >}}).
 
@@ -66,11 +66,15 @@ You only need to install the SCC once, but you must not delete it.
 After the install, the OperatorHub automatically uses the constraint for Redis Enterprise node pods.
 
 {{< note >}}
-**Known Limitation** - The automatic use of the security constraint is limited. The
-Redis Enterprise must be named `rec` for the constraint to be used automatically.  **Use the cluster name `rec` when deploying with the OperatorHub.**
+If you are using the recommended RedisEnterpriseCluster name of `rec`, the SCC is automatically bound to the RedisEnterpriseCluster after install.
+
+If you choose a different name for the RedisEnterpriseCluster, or override the default service account name, you must manually bind the SCC to the RedisEnterpriseCluster’s service account:
+
+  ```sh
+  oc adm policy add-scc-to-user redis-enterprise-scc-v2 \
+  system:serviceaccount:<my-project>:<rec-service-account-name>
+  ```
 
-If you require a different name, you must grant the SCC to the project
-namespace.
 {{< /note >}}
 
 ## Create Redis Enterprise custom resources

content/operate/oss_and_stack/stack-with-enterprise/gears-v1/installing-redisgears.md

@@ -24,7 +24,7 @@ Offline installation requires you to manually upload dependencies to the master
 
 ### Install RedisGears and dependencies
 
-1. Download the **RedisGears** package from the Redis Enterprise [download center](https://app.redislabs.com/#/rlec-downloads).
+1. Download the **RedisGears** package from the Redis Enterprise [download center](https://cloud.redis.io/#/rlec-downloads).
 
     {{<note>}}
 For offline installation of RedisGears v1.2 and later, you also need to download the **RedisGears Dependencies** packages for both Python and Java.