diff --git a/content/embeds/supported-platforms-embed.md b/content/embeds/supported-platforms-embed.md index f9876faa9..4156f9657 100644 --- a/content/embeds/supported-platforms-embed.md +++ b/content/embeds/supported-platforms-embed.md @@ -13,6 +13,7 @@ Redis Enterprise Software is supported on several operating systems, cloud envi | [**End-of-life date**]({{< relref "/operate/rs/installing-upgrading/product-lifecycle#endoflife-schedule" >}}) | Determined after
next major release | Nov 2026 | Feb 2026 | Aug 2025 | Feb 2025 | | **Platforms** | | | | | | | RHEL 9 &
compatible distros[1](#table-note-1) | ✅ | ✅ | – | – | – | +| RHEL 9
FIPS mode[5](#table-note-5) | ✅ | – | – | – | – | | RHEL 8 &
compatible distros[1](#table-note-1) | ✅ | ✅ | ✅ | ✅ | ✅ | | RHEL 7 &
compatible distros[1](#table-note-1) | – | – | :warning: | ✅ | ✅ | | Ubuntu 20.04[2](#table-note-2) | ✅ | ✅ | ✅ | ✅ | – | @@ -23,14 +24,15 @@ Redis Enterprise Software is supported on several operating systems, cloud envi | Kubernetes[3](#table-note-3) | ✅ | ✅ | ✅ | ✅ | ✅ | | Docker[4](#table-note-4) | ✅ | ✅ | ✅ | ✅ | ✅ | -1. The RHEL-compatible distributions CentOS, CentOS Stream, Alma, and Rocky are supported if they have full RHEL compatibility. Oracle Linux running the Red Hat Compatible Kernel (RHCK) is supported, but the Unbreakable Enterprise Kernel (UEK) is not supported. +1. The RHEL-compatible distributions CentOS, CentOS Stream, Alma, and Rocky are supported if they have full RHEL compatibility. Oracle Linux running the Red Hat Compatible Kernel (RHCK) is supported, but the Unbreakable Enterprise Kernel (UEK) is not supported. -2. The server version of Ubuntu is recommended for production installations. The desktop version is only recommended for development deployments. +2. The server version of Ubuntu is recommended for production installations. The desktop version is only recommended for development deployments. -3. See the [Redis Enterprise for Kubernetes documentation]({{< relref "/operate/kubernetes/reference/supported_k8s_distributions" >}}) for details about support per version and Kubernetes distribution. +3. See the [Redis Enterprise for Kubernetes documentation]({{< relref "/operate/kubernetes/reference/supported_k8s_distributions" >}}) for details about support per version and Kubernetes distribution. -4. -[Docker images]({{< relref "/operate/rs/installing-upgrading/quickstarts/docker-quickstart" >}}) of Redis Enterprise Software are certified for development and testing only. +4. [Docker images]({{< relref "/operate/rs/installing-upgrading/quickstarts/docker-quickstart" >}}) of Redis Enterprise Software are certified for development and testing only. + +5. Supported only if [FIPS was enabled during RHEL installation](https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/9/html/security_hardening/switching-rhel-to-fips-mode_security-hardening#proc_installing-the-system-with-fips-mode-enabled_switching-rhel-to-fips-mode) to ensure FIPS compliance. The following table shows which Redis Enterprise Software version first tested and added support for each RHEL version: diff --git a/content/operate/rs/clusters/monitoring/_index.md b/content/operate/rs/clusters/monitoring/_index.md index ad6d62cfc..a9e2a69c8 100644 --- a/content/operate/rs/clusters/monitoring/_index.md +++ b/content/operate/rs/clusters/monitoring/_index.md @@ -13,14 +13,21 @@ weight: 96 --- You can use the metrics that measure the performance of your Redis Enterprise Software clusters, nodes, databases, and shards to monitor the performance of your databases. -In the Redis Enterprise Cluster Manager UI, you can see real-time metrics and configure alerts that send notifications based on alert parameters. You can also access metrics and configure alerts through the REST API. +In the Redis Enterprise Cluster Manager UI, you can view metrics, configure alerts, and send notifications based on alert parameters. You can also access metrics and configure alerts through the REST API. + +Redis Enterprise version 7.8.2 introduces a preview of the new metrics stream engine that exposes the v2 Prometheus scraping endpoint at https://:8070/v2 . +This new engine exports all time-series metrics to external monitoring tools such as Grafana, DataDog, NewRelic, and Dynatrace using Prometheus. + +The new engine enables real-time monitoring, including full monitoring during maintenance operations, providing full visibility into performance during events such as shards' failovers and scaling operations. + +If you are already using the existing scraping endpoint for integration, follow this guide [link] to transition and try the new engine. It is possible to scrape both existing and new endpoints simultaneously, allowing advanced dashboard preparation and a smooth transition. To integrate Redis Enterprise metrics into your monitoring environment, see the integration guides for [Prometheus and Grafana]({{< relref "/integrate/prometheus-with-redis-enterprise/" >}}) or [Uptrace]({{< relref "/integrate/uptrace-with-redis-enterprise/" >}}). Make sure you read the [definition of each metric]({{< relref "/operate/rs/references/metrics/" >}}) so that you understand exactly what it represents. -## Real-time metrics +## Cluster manager metrics You can see the metrics of the cluster in: diff --git a/content/operate/rs/release-notes/rs-7-8-releases/_index.md b/content/operate/rs/release-notes/rs-7-8-releases/_index.md index a4b7ccb68..8ab06b97a 100644 --- a/content/operate/rs/release-notes/rs-7-8-releases/_index.md +++ b/content/operate/rs/release-notes/rs-7-8-releases/_index.md @@ -206,6 +206,7 @@ The following table provides a snapshot of supported platforms as of this Redis | [**End-of-life date**]({{< relref "/operate/rs/installing-upgrading/product-lifecycle#endoflife-schedule" >}}) | Determined after
next major release | Nov 2026 | Feb 2026 | Aug 2025 | Feb 2025 | | **Platforms** | | | | | | | RHEL 9 &
compatible distros[1](#table-note-1) | ✅ | ✅ | – | – | – | +| RHEL 9
FIPS mode[5](#table-note-5) | ✅ | – | – | – | – | | RHEL 8 &
compatible distros[1](#table-note-1) | ✅ | ✅ | ✅ | ✅ | ✅ | | RHEL 7 &
compatible distros[1](#table-note-1) | – | – | :warning: | ✅ | ✅ | | Ubuntu 20.04[2](#table-note-2) | ✅ | ✅ | ✅ | ✅ | – | @@ -216,14 +217,15 @@ The following table provides a snapshot of supported platforms as of this Redis | Kubernetes[3](#table-note-3) | ✅ | ✅ | ✅ | ✅ | ✅ | | Docker[4](#table-note-4) | ✅ | ✅ | ✅ | ✅ | ✅ | -1. The RHEL-compatible distributions CentOS, CentOS Stream, Alma, and Rocky are supported if they have full RHEL compatibility. Oracle Linux running the Red Hat Compatible Kernel (RHCK) is supported, but the Unbreakable Enterprise Kernel (UEK) is not supported. +1. The RHEL-compatible distributions CentOS, CentOS Stream, Alma, and Rocky are supported if they have full RHEL compatibility. Oracle Linux running the Red Hat Compatible Kernel (RHCK) is supported, but the Unbreakable Enterprise Kernel (UEK) is not supported. -2. The server version of Ubuntu is recommended for production installations. The desktop version is only recommended for development deployments. +2. The server version of Ubuntu is recommended for production installations. The desktop version is only recommended for development deployments. -3. See the [Redis Enterprise for Kubernetes documentation]({{< relref "/operate/kubernetes/reference/supported_k8s_distributions" >}}) for details about support per version and Kubernetes distribution. +3. See the [Redis Enterprise for Kubernetes documentation]({{< relref "/operate/kubernetes/reference/supported_k8s_distributions" >}}) for details about support per version and Kubernetes distribution. -4. -[Docker images]({{< relref "/operate/rs/installing-upgrading/quickstarts/docker-quickstart" >}}) of Redis Software are certified for development and testing only. +4. [Docker images]({{< relref "/operate/rs/installing-upgrading/quickstarts/docker-quickstart" >}}) of Redis Software are certified for development and testing only. + +5. Supported only if [FIPS was enabled during RHEL installation](https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/9/html/security_hardening/switching-rhel-to-fips-mode_security-hardening#proc_installing-the-system-with-fips-mode-enabled_switching-rhel-to-fips-mode) to ensure FIPS compliance. ## Known issues diff --git a/content/operate/rs/release-notes/rs-7-8-releases/rs-7-8-2-28.md b/content/operate/rs/release-notes/rs-7-8-releases/rs-7-8-2-28.md index 2d2a4e285..c0ccf56b3 100644 --- a/content/operate/rs/release-notes/rs-7-8-releases/rs-7-8-2-28.md +++ b/content/operate/rs/release-notes/rs-7-8-releases/rs-7-8-2-28.md @@ -56,7 +56,7 @@ This version offers: - Client-side caching support: - - Client-side caching allows Redis clients to store a subset of data in a local cache and avoid sending repeated requests to the Redis database. + - Client-side caching allows Redis clients to store a subset of data in a local cache and avoid sending repeated read requests to the Redis database. - When used to cache frequently accessed data, this technique can improve performance by decreasing network traffic, latency, and load on the database. @@ -64,7 +64,13 @@ This version offers: - For more information, see the [client-side caching introduction]({{}}) and [client-side caching compatibility with Redis Software]({{}}). -- [Database availability API]({{}}), which verifies whether a Redis Software database is available to perform read and write operations and can respond to queries from client applications. Load balancers and automated monitoring tools can use this API to monitor database availability. +- Database availability API: + + - Verifies whether a Redis Software database is available to perform read and write operations and can respond to queries from client applications. + + - Load balancers and automated monitoring tools can use this API to monitor database availability. + + - See [Check database availability]({{}}) and the [REST API reference]({{}}) for details. - Metrics stream engine preview: @@ -366,6 +372,7 @@ The following table provides a snapshot of supported platforms as of this Redis | [**End-of-life date**]({{< relref "/operate/rs/installing-upgrading/product-lifecycle#endoflife-schedule" >}}) | Determined after
next major release | Nov 2026 | Feb 2026 | Aug 2025 | Feb 2025 | | **Platforms** | | | | | | | RHEL 9 &
compatible distros[1](#table-note-1) | ✅ | ✅ | – | – | – | +| RHEL 9
FIPS mode[5](#table-note-5) | ✅ | – | – | – | – | | RHEL 8 &
compatible distros[1](#table-note-1) | ✅ | ✅ | ✅ | ✅ | ✅ | | RHEL 7 &
compatible distros[1](#table-note-1) | – | – | :warning: | ✅ | ✅ | | Ubuntu 20.04[2](#table-note-2) | ✅ | ✅ | ✅ | ✅ | – | @@ -376,14 +383,15 @@ The following table provides a snapshot of supported platforms as of this Redis | Kubernetes[3](#table-note-3) | ✅ | ✅ | ✅ | ✅ | ✅ | | Docker[4](#table-note-4) | ✅ | ✅ | ✅ | ✅ | ✅ | -1. The RHEL-compatible distributions CentOS, CentOS Stream, Alma, and Rocky are supported if they have full RHEL compatibility. Oracle Linux running the Red Hat Compatible Kernel (RHCK) is supported, but the Unbreakable Enterprise Kernel (UEK) is not supported. +1. The RHEL-compatible distributions CentOS, CentOS Stream, Alma, and Rocky are supported if they have full RHEL compatibility. Oracle Linux running the Red Hat Compatible Kernel (RHCK) is supported, but the Unbreakable Enterprise Kernel (UEK) is not supported. + +2. The server version of Ubuntu is recommended for production installations. The desktop version is only recommended for development deployments. -2. The server version of Ubuntu is recommended for production installations. The desktop version is only recommended for development deployments. +3. See the [Redis Enterprise for Kubernetes documentation]({{< relref "/operate/kubernetes/reference/supported_k8s_distributions" >}}) for details about support per version and Kubernetes distribution. -3. See the [Redis Enterprise for Kubernetes documentation]({{< relref "/operate/kubernetes/reference/supported_k8s_distributions" >}}) for details about support per version and Kubernetes distribution. +4. [Docker images]({{< relref "/operate/rs/installing-upgrading/quickstarts/docker-quickstart" >}}) of Redis Software are certified for development and testing only. -4. -[Docker images]({{< relref "/operate/rs/installing-upgrading/quickstarts/docker-quickstart" >}}) of Redis Software are certified for development and testing only. +5. Supported only if [FIPS was enabled during RHEL installation](https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/9/html/security_hardening/switching-rhel-to-fips-mode_security-hardening#proc_installing-the-system-with-fips-mode-enabled_switching-rhel-to-fips-mode) to ensure FIPS compliance. ## Downloads diff --git a/content/operate/rs/security/encryption/tls/enable-tls.md b/content/operate/rs/security/encryption/tls/enable-tls.md index 102c8e4b5..4c9a10dff 100644 --- a/content/operate/rs/security/encryption/tls/enable-tls.md +++ b/content/operate/rs/security/encryption/tls/enable-tls.md @@ -36,11 +36,11 @@ To enable mutual TLS for client connections: 1. Select **Mutual TLS (Client authentication)**. - {{Mutual TLS authentication configuration.}} + {{Mutual TLS authentication configuration.}} 1. For each client certificate, select **+ Add certificate**, paste or upload the client certificate, then select **Done**. - If your database uses Replica Of or Active-Active replication, you also need to add the syncer certificates for the participating clusters. See [Enable TLS for Replica Of cluster connections](#enable-tls-for-replica-of-cluster-connections) or [Enable TLS for Active-Active cluster connections](#enable-tls-for-active-active-cluster-connections) for instructions. + If your database uses Replica Of, you also need to add the syncer certificates for the participating clusters. See [Enable TLS for Replica Of cluster connections](#enable-tls-for-replica-of-cluster-connections) for instructions. 1. You can configure **Additional certificate validations** to further limit connections to clients with valid certificates. @@ -73,59 +73,27 @@ To enable mutual TLS for client connections: 1. Select **Save**. - {{< note >}} By default, Redis Enterprise Software validates client certificate expiration dates. You can use `rladmin` to turn off this behavior. ```sh rladmin tune db < db:id | name > mtls_allow_outdated_certs enabled ``` - - {{< /note >}} ## Enable TLS for Active-Active cluster connections -To enable TLS for Active-Active cluster connections: - -1. If you are using the new Cluster Manager UI, switch to the legacy admin console. - - {{Select switch to legacy admin console from the dropdown.}} - -1. [Retrieve syncer certificates.](#retrieve-syncer-certificates) - -1. [Configure TLS certificates for Active-Active.](#configure-tls-certificates-for-active-active) - -1. [Configure TLS on all participating clusters.](#configure-tls-on-all-participating-clusters) - -{{< note >}} You cannot enable or turn off TLS after the Active-Active database is created, but you can change the TLS configuration. -{{< /note >}} - -### Retrieve syncer certificates -For each participating cluster, copy the syncer certificate from the **general** settings tab. - -{{< image filename="/images/rs/general-settings-syncer-cert.png" alt="general-settings-syncer-cert" >}} +To enable TLS for Active-Active cluster connections: -### Configure TLS certificates for Active-Active +1. During [database creation]({{}}), expand the **TLS** configuration section. -1. During database creation (see [Create an Active-Active Geo-Replicated Database]({{< relref "/operate/rs/databases/active-active/create.md" >}}), select **Edit** from the **configuration** tab. -1. Enable **TLS**. - - **Enforce client authentication** is selected by default. If you clear this option, you will still enforce encryption, but TLS client authentication will be deactivated. -1. Select **Require TLS for CRDB communication only** from the dropdown menu. - {{< image filename="/images/rs/crdb-tls-all.png" alt="crdb-tls-all" >}} -1. Select **Add** {{< image filename="/images/rs/icon_add.png#no-click" alt="Add" >}} -1. Paste a syncer certificate into the text box. - {{< image filename="/images/rs/database-tls-replica-certs.png" alt="Database TLS Configuration" >}} -1. Save the syncer certificate. {{< image filename="/images/rs/icon_save.png#no-click" alt="Save" >}} -1. Repeat this process, adding the syncer certificate for each participating cluster. -1. Optional: If also you want to require TLS for client connections, select **Require TLS for All Communications** from the dropdown and add client certificates as well. -1. Select **Update** at the bottom of the screen to save your configuration. +1. Select **On** to enable TLS. -### Configure TLS on all participating clusters + {{TLS is enabled on the Cluster Manager UI screen.}} -Repeat this process on all participating clusters. +1. Click **Create**. -To enforce TLS authentication, Active-Active databases require syncer certificates for each cluster connection. If every participating cluster doesn't have a syncer certificate for every other participating cluster, synchronization will fail. +If you also want to require TLS for client connections, you must edit the Active-Active database configuration after creation. See [Enable TLS for client connections](#client) for instructions. ## Enable TLS for Replica Of cluster connections diff --git a/static/images/rs/screenshots/databases/active-active-databases/enable-tls-for-active-active-db.png b/static/images/rs/screenshots/databases/active-active-databases/enable-tls-for-active-active-db.png new file mode 100644 index 000000000..d45e3039a Binary files /dev/null and b/static/images/rs/screenshots/databases/active-active-databases/enable-tls-for-active-active-db.png differ diff --git a/static/images/rs/screenshots/databases/security-mtls-clients-7-8-2.png b/static/images/rs/screenshots/databases/security-mtls-clients-7-8-2.png new file mode 100644 index 000000000..c39fc8f8d Binary files /dev/null and b/static/images/rs/screenshots/databases/security-mtls-clients-7-8-2.png differ