{ "id": "rs-8-2-releases", "title": "Redis Software release notes 8.2.x", "url": "https://redis.io/docs/latest/operate/rs/release-notes/rs-8-2-releases/", "summary": "Database-scoped management roles. Data path command auditing.", "tags": [ "docs", "operate", "rs" ], "last_updated": "2026-07-24T10:52:10-07:00", "children": [ { "id": "rs-8-2-0-25", "summary": "Database-scoped management roles. Data path command auditing.", "title": "Redis Software release notes 8.2.0-25 (July 2026)", "url": "https://redis.io/docs/latest/operate/rs/release-notes/rs-8-2-releases/rs-8-2-0-25/" } ], "page_type": "content", "content_hash": "6b486cca9270373a3043f3db7397e45663e7d966579068aa8b4d44bafa8838e4", "sections": [ { "id": "overview", "title": "Overview", "role": "overview", "text": "​[​Redis Software version 8.2](https://redis.io/downloads/#Redis_Software) is now available!" }, { "id": "highlights", "title": "Highlights", "role": "content", "text": "This version offers:\n\n- Database-scoped management roles\n\n- Data path command auditing\n\n- FIPS 140-3 support" }, { "id": "detailed-release-notes", "title": "Detailed release notes", "role": "content", "text": "For more detailed release notes, select a build version from the following table:" }, { "id": "version-changes", "title": "Version changes", "role": "compatibility", "text": "" }, { "id": "breaking-changes", "title": "Breaking changes", "role": "content", "text": "Redis Software version 8.2.0 introduces the following breaking changes:\n\n- **Local import from Redis Software system directories is no longer supported.** To improve security, database imports that use the `mount_point` source can no longer read files from Redis Software system directories, including `/opt/redislabs`, `/var/opt/redislabs`, `/etc/opt/redislabs`, and any of their subdirectories.\n\n - Import operations that reference files in these directories now fail.\n\n - Store import files in a non-system location accessible to Redis Software before you start the import.\n\n- **`smtp_password` is now a write-only field in the Cluster API.** To improve security, the API no longer returns the SMTP password in responses to `GET /v1/cluster`, and the Cluster Manager UI no longer reads or displays the existing password.\n\n - Applications or scripts that previously expected `smtp_password` to be returned by the Cluster API no longer receive this field.\n\n - When you update SMTP settings, the existing password cannot be retrieved. To change the SMTP password, provide a new password as part of the update request.\n\n- **Custom module upload is disabled by default.** To improve security, custom (user-defined) module uploads are now disabled by default. A new cluster setting, `allow_modules_upload`, controls access to the custom module upload APIs. When this setting is disabled (the default), requests to `POST /v2/modules/user-defined` and `POST /v2/local/modules/user-defined/artifacts` return `403 modules_upload_disabled`, regardless of user role.\n\n - To enable custom module uploads, set `allow_modules_upload` to `true` with a `PUT /v1/cluster` request.\n\n - Applications or automation that call the custom module upload APIs directly receive a `403 modules_upload_disabled` response until the setting is enabled.\n\n - Existing functionality for listing, deleting, and loading modules is unchanged." }, { "id": "openssl-version", "title": "OpenSSL version", "role": "content", "text": "Redis Software version 8.0.16 and later requires OpenSSL 3.3 or later." }, { "id": "reserved-ports", "title": "Reserved ports", "role": "content", "text": "Make sure the following ports are open before upgrading Redis Software.\n\nThe following port was added as a reserved port in Redis Software version 8.0.18; however, it is optional instead of reserved in Redis Software version 8.0.20-44:\n\n| Port | Process name | Usage |\n|------|--------------|-------|\n| 3357 | reconciliation_tree_grpc | Internal communication |\n\nPorts reserved as of Redis Software version 7.22.0:\n\n| Port | Process name | Usage | \n|------|--------------|-------|\n| 3346 | cluster_api_internal | Cluster API internal port |\n| 3351 | cluster_watchdog_grpc_api | Cluster watchdog now supports gRPC |\n| 3352 | grpc_service_mesh | gRPC communication between nodes |\n| 3353 | local_grpc_service_mesh | Local gRPC services |\n| 3354 | grpc_gossip_envoy | gRPC gossip protocol communication between nodes |\n| 3355 | authentication_service | Authentication service internal port |\n\nPorts reserved as of Redis Software version 7.8.2:\n\n| Port | Process name | Usage | \n|------|--------------|-------|\n| 3347 | cert_exporter | Reports cluster certificate metrics |\n| 3348 | process_exporter | Reports process metrics for DMC and Redis processes |\n| 3349 | cluster_wd_exporter | Reports cluster watchdog metrics |\n| 3350 | db_controller | Internode communication |\n| 9091 | node_exporter | Reports host node metrics related to CPU, memory, disk, and more |\n| 9125 | statsd_exporter | Reports push metrics related to the DMC and syncer, and some cluster and node metrics |\n\nSee [Ports and port ranges used by Redis Software](https://redis.io/docs/latest/operate/rs/networking/port-configurations#ports-and-port-ranges-used-by-redis-software) for a complete list." }, { "id": "deprecations", "title": "Deprecations", "role": "content", "text": "#### API deprecations\n\n- The `db_conns_auditing` cluster policy and database configuration field is deprecated. Use the `audit_settings.audit_mode` field instead. Setting `db_conns_auditing` to `true` is equivalent to setting `audit_mode` to `connection`. See [Audit events](https://redis.io/docs/latest/operate/rs/security/audit-events) for the current auditing configuration.\n\n- The `gradual_src_mode`, `gradual_sync_mode`, and `gradual_sync_max_shards_per_source` parameters are deprecated. Use `gradual_sync_policy` instead. You can set it with [`rladmin tune db`](https://redis.io/docs/latest/operate/rs/references/cli-utilities/rladmin/tune) or the REST API.\n\n- The `old_password` field in `POST /v1/users/password` and `PUT /v1/users/password` requests is deprecated and ignored. It was optional and had no effect when adding or resetting a password, so you can remove it from these requests. `old_password` is still required for `DELETE /v1/users/password`, which uses it to identify the password to delete.\n\n- The following REST API fields, deprecated since Redis Software version 6.4.2, are removed in this release:\n\n - `use_ipv6` (cluster object) — use `use_external_ipv6` instead.\n\n - `redis_cleanup_job_settings` (job scheduler object) — use `persistence_cleanup_scan_interval` instead.\n\n#### Internal monitoring and v1 Prometheus metrics deprecation\n\nThe existing [internal monitoring engine](https://redis.io/docs/latest/operate/rs/monitoring/v1_monitoring) is deprecated. We recommend transitioning to the new [metrics stream engine](https://redis.io/docs/latest/operate/rs/monitoring/metrics_stream_engine) for improved performance, enhanced integration capabilities, and modernized metrics streaming.\n\nV1 Prometheus metrics are deprecated but still available. To transition to the new metrics stream engine, either migrate your existing dashboards using [this guide](https://redis.io/docs/latest/operate/rs/references/metrics/prometheus-metrics-v1-to-v2) or use [new preconfigured dashboards](https://redis.io/docs/latest/integrate/prometheus-with-redis-enterprise#grafana-dashboards-for-redis-software).\n\nAs part of the transition to the metrics stream engine, some internal cluster manager alerts were deprecated in favor of external monitoring solutions. See the [alerts transition plan](https://redis.io/docs/latest/operate/rs/references/alerts/alerts-v1-to-v2) for guidance." }, { "id": "supported-platforms", "title": "Supported platforms", "role": "compatibility", "text": "The following table provides a snapshot of supported platforms as of this Redis Software release. See the [supported platforms reference](https://redis.io/docs/latest/operate/rs/references/supported-platforms) for more details about operating system compatibility.\n\n✅ Supported – The platform is supported for this version of Redis Software and Redis Stack modules.\n\n:warning: Deprecation warning – The platform is still supported for this version of Redis Software, but support will be removed in a future release.\n\n| Redis Software
major versions | 8.2 | 8.0 | 7.22 | 7.8 | 7.4 | 7.2 | 6.4 | 6.2 |\n|---------------------------------|:-----:|:-----:|:-----:|:-----:|:-----:|:-----:|:-----:|:-----:|\n| **Release date** | Jul 2026 | Oct 2025 | May 2025 | Nov 2024 | Feb 2024 | Aug 2023 | Feb 2023 | Aug 2021 |\n| [**End-of-life date**](https://redis.io/docs/latest/operate/rs/installing-upgrading/product-lifecycle#endoflife-schedule) | Determined after
next major release | Jul 2028 | Oct 2027 | May 2027 | Nov 2026 | Feb 2026 | Aug 2025 | Feb 2025 |\n| **Platforms** | | | | | | | | |\n| RHEL 9 &
compatible distros[1](#table-note-1) | ✅ | ✅ | ✅ | ✅ | ✅ | – | – | – |\n| RHEL 9
FIPS mode[5](#table-note-5) | ✅ | ✅ | ✅ | ✅ | – | – | – | – |\n| RHEL 8 &
compatible distros[1](#table-note-1) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |\n| RHEL 7 &
compatible distros[1](#table-note-1) | – | – | – | – | – | :warning: | :warning: | :warning: |\n| Ubuntu 22.04[2](#table-note-2) | ✅ | ✅ | ✅ | ✅ | – | – | – | – |\n| Ubuntu 20.04[2](#table-note-2) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | – |\n| Ubuntu 18.04[2](#table-note-2) | – | – | – | – | :warning: | :warning: | :warning: | :warning: |\n| Ubuntu 16.04[2](#table-note-2) | – | – | – | – | – | :warning: | :warning: | :warning: |\n| Amazon Linux 2023[6](#table-note-6) | ✅ | ✅ | – | – | – | – | – | – |\n| Amazon Linux 2 | – | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | – |\n| Amazon Linux 1 | – | – | – | – | – | :warning: | :warning: | :warning: |\n| Kubernetes[3](#table-note-3) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |\n| Docker[4](#table-note-4) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |\n\n1. 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.\n\n2. The server version of Ubuntu is recommended for production installations. The desktop version is only recommended for development deployments.\n\n3. See the [Redis Enterprise for Kubernetes documentation](https://redis.io/docs/latest/operate/kubernetes/reference/supported_k8s_distributions) for details about support per version and Kubernetes distribution.\n\n4. [Docker images](https://redis.io/docs/latest/operate/rs/installing-upgrading/quickstarts/docker-quickstart) of Redis Software are certified for development and testing only.\n\n5. 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.\n\n6. Amazon Linux 2023 support was added in Redis Software version 8.0.20." }, { "id": "known-issues", "title": "Known issues", "role": "content", "text": "- RS155734: Endpoint availability metrics do not work as expected due to a calculation error." }, { "id": "known-limitations", "title": "Known limitations", "role": "content", "text": "#### Redis Search query failures during rolling upgrades across the 8.4 version boundary\n\nRedis Search queries can fail during a rolling upgrade when a cluster contains shards running Redis versions earlier than 8.4 and shards running Redis version 8.4 or later, due to an internal protocol change introduced in version 8.4. This issue affects only clusters where `parallel_shards_upgrade` has been changed from its default value of `0`. If both conditions apply, expect Redis Search downtime until all nodes are upgraded.\n\n#### Trim ACKED not supported for Active-Active 8.4 databases\n\nFor Active-Active databases running Redis database version 8.4, the `ACKED` option is not supported for trimming commands.\n\n#### Rolling upgrade limitation for clusters with custom or deprecated modules\n\nDue to module handling changes introduced in Redis 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.\n\n#### Module commands limitation during Active-Active database upgrades to Redis 8.0\n\nWhen upgrading an Active-Active database to Redis version 8.0, you cannot use module commands until all Active-Active database instances have been upgraded. Currently, these commands are not blocked automatically.\n\n#### Redis 8.0 database cannot be created with flash\n\nYou cannot create a Redis 8.0 database with flash storage enabled. Create a Redis 8.0 database with RAM-only storage instead, or use Redis 8.2 for flash-enabled (Redis Flex) databases.\n\n#### New Cluster Manager UI limitations\n\nThe following legacy UI features are not yet available in the new Cluster Manager UI:\n\n- Purge an Active-Active instance.\n\n Use [`crdb-cli crdb purge-instance`](https://redis.io/docs/latest/operate/rs/references/cli-utilities/crdb-cli/crdb/purge-instance) instead.\n\n- Search and export the log." } ], "examples": [] }