RS 8.0.10 January release docs

content/embeds/rs-prometheus-metrics-v2.md

@@ -65,6 +65,12 @@
 | <span class="break-all">node_provisional_memory_bytes</span> | gauge | Amount of RAM that is available for provisioning to databases out of the total RAM allocated for databases |
 | <span class="break-all">node_provisional_memory_no_overbooking_bytes</span> | gauge | Amount of RAM that is available for provisioning to databases out of the total RAM allocated for databases, without taking into account overbooking |
 | node_metrics_up | gauge | Node is part of the cluster and is connected |
+| <span class="break-all">node_wd_dmc_ping_failures</span> | gauge | Number of consecutive DMC ping failures |
+| <span class="break-all">node_wd_dmc_ping_failure_duration_seconds</span> | gauge | Duration of ongoing DMC failures (0 when healthy) |
+| <span class="break-all">node_wd_endpoint_ping_failures</span> | gauge | Number of consecutive endpoint ping failures. Labels: endpoint_uid |
+| <span class="break-all">node_wd_endpoint_ping_failure_duration_seconds</span> | gauge | Duration of ongoing endpoint failures (0 when healthy). Labels: endpoint_uid |
+| <span class="break-all">node_wd_shard_ping_failures</span> | gauge | Number of consecutive ping failures for a shard. Labels: shard_uid, role |
+| <span class="break-all">node_wd_shard_ping_failure_duration_seconds</span> | gauge | Duration of ongoing failures (0 when healthy). Labels: shard_uid, role |
 
 ## Cluster metrics
 

content/operate/rs/installing-upgrading/upgrading/upgrade-database.md

@@ -25,7 +25,9 @@ The default Redis database version differs between Redis Enterprise releases as
 <a name="db-versions-table"></a>
 | Redis<br />Software | Bundled Redis<br />DB versions | Default DB version<br />(upgraded/new databases) |
 |-------|----------|-----|
-| 8.0.x | 6.2, 7.2, 7.4, 8.2 | 8.2 |
+| 8.0.10 | 6.2, 7.2, 7.4, 8.0, 8.2, 8.4 | 8.4 |
+| 8.0.6 | 6.2, 7.2, 7.4, 8.0, 8.2 | 8.2 |
+| 8.0.2 | 6.2, 7.2, 7.4, 8.0, 8.2 | 8.2 |
 | 7.22.x | 6.2, 7.2, 7.4 | 7.4 |
 | 7.8.x | 6.2, 7.2, 7.4 | 7.4 |
 | 7.4.x | 6.0, 6.2, 7.2 | 7.2 |

content/operate/rs/references/rest-api/objects/crdb/database_config.md

@@ -22,6 +22,9 @@ An object that represents the database configuration.
 | cert | string | Optional PEM-encoded server certificate for the underlying database instance |
 | data_persistence | 'disabled'<br />'snapshot'<br />**'aof'** | Database on-disk persistence policy. For snapshot persistence, a [snapshot_policy]({{< relref "/operate/rs/references/rest-api/objects/bdb/snapshot_policy" >}}) must be provided |
 | <span class="break-all">enforce_client_authentication</span> | **'enabled'** <br />'disabled' | Require authentication of client certificates for SSL connections to the database. If enabled, a certificate should be provided in either <span class="break-all">`authentication_ssl_client_certs`</span> or <span class="break-all">`authentication_ssl_crdt_certs`</span> |
+| <span class="break-all">authentication_ssl_client_certs</span> | array | List of authorized client certificates. For Active-Active databases, it is strongly advised to configure the client certificates individually for each instance instead of using the default database configuration, even if the same certificate is used across all instances.<br />{{<code>}}[{<br />  "client_cert": string<br />}, ...]{{</code>}}<br />**client_cert**: X.509 PEM (Base64) encoded certificate |
+| <span class="break-all">mtls_allow_outdated_certs</span> | boolean (default: false) | An optional mTLS relaxation flag for certs verification |
+| <span class="break-all">mtls_allow_weak_hashing</span> | boolean (default: false) | An optional mTLS relaxation flag for certs verification |
 | max_aof_file_size | integer | Maximum AOF file size in bytes |
 | max_aof_load_time | integer (default: 3600) | Maximum AOF reload time in seconds |
 | memory_size | integer (default: 0) | Database memory size limit in bytes. 0 is unlimited. |

content/operate/rs/release-notes/rs-8-0-releases/_index.md

@@ -5,7 +5,7 @@ categories:
 - docs
 - operate
 - rs
-compatibleOSSVersion: Redis 8.2, 8.0, 7.4, 7.2, 6.2
+compatibleOSSVersion: Redis 8.4, 8.2, 8.0, 7.4, 7.2, 6.2
 description: Redis Software 8! The most performant, most secure, and richest version so far. Built for performance, scale, and reliability to power modern ML and AI applications.
 hideListLinks: true
 linkTitle: 8.0.x releases
@@ -19,7 +19,7 @@ weight: 67
 
 This version offers:
 
-- Redis 8.0 and 8.2 feature set versions
+- Redis 8.0, 8.2, and 8.4 feature set versions
 
 - Performance improvements and memory reduction
 
@@ -199,12 +199,18 @@ The following table provides a snapshot of supported platforms as of this Redis
 
     As a workaround, use an IPv4-based address for the SSO service base address, or register a DNS name that resolves to the IPv6 address.
 
+    This issue was fixed in Redis Enterprise Software version 8.0.10.
+
 - RS131972: Creating an ACL that contains a line break in the Cluster Manager UI can cause shard migration to fail due to ACL errors. This issue was fixed in Redis Enterprise Software version 8.0.6.
 
 - RS155734: Endpoint availability metrics do not work as expected due to a calculation error.
 
 ## Known limitations
 
+#### Trim ACKED not supported for Active-Active 8.4 databases
+
+For Active-Active databases running Redis database version 8.4, the `ACKED` option is not supported for trimming commands.
+
 #### Rolling upgrade limitation for clusters with custom or deprecated modules
 
 Due to module handling changes introduced in Redis Enterprise Software version 8.0, upgrading a cluster that contains custom or deprecated modules, such as RedisGraph and RedisGears v2, can become stuck when adding a new node to the cluster during a rolling upgrade.