Redis Software cluster version 7.8 reaches end of life (EOL) on May 30, 2027. This applies to every 7.8.x build. Clusters will continue running after this date, but will no longer receive security patches, bug fixes, maintenance releases, or full support. Review the Prerequisites, follow the Upgrade planning steps, and understand What happens after EOL to prepare your upgrade.
This announcement applies to the Redis Software cluster version; the bundled Redis database versions have separate lifecycles.
Prerequisites
Identify your current cluster and database versions.
- Check the cluster version in the Cluster Manager UI or with rladmin status nodes.
- Check database versions with rladmin status databases.
Review compatibility before selecting an upgrade target.
- Confirm that your operating system is listed in the target release’s supported platforms.
- Review the module lifecycle and compatibility of the Search, JSON, TimeSeries, Bloom, or other modules you use.
- Confirm that your database versions are supported by the target cluster version using the bundled database version table.
Common Scenarios and Actions
| If you are… | What to do |
| Running any Redis Software 7.8.x build | Plan a cluster upgrade before May 30, 2027. |
| Selecting a target cluster version | Review the target options below and confirm platform, database, and module compatibility. |
| Running Redis 6.2 databases on a 7.8 cluster | Plan for both the cluster and database lifecycles when coordinating upgrades. |
| Running Active-Active databases (CRDBs) | Use the Active-Active upgrade procedure linked below. |
| Running Redis for Kubernetes | Use the Kubernetes upgrade procedure linked below. |
| Unsure about compatibility or upgrade sequencing | Contact your TAM or Redis Support before starting the upgrade. |
Upgrade planning steps
1. Select a target cluster version
Direct cluster upgrades from 7.8.x are supported to the following targets without an intermediate upgrade.
| Target cluster version | End of life | Planning guidance |
| 8.2.x | Not listed in the lifecycle schedule | Recommended target. |
| 8.0.x | July 31, 2028 | Alternative supported target. |
| 7.22.x | October 30, 2027 | Supported, but provides only five additional months beyond the 7.8 EOL date. Use when a specific constraint requires it. |
Confirm the exact target release against the Redis Software lifecycle and supported upgrade paths.
2. Review release changes and database requirements
Review the target release and every intervening release before upgrading.
- Read the release notes for Redis Software 7.22, 8.0, and 8.2, as applicable to your upgrade path.
- Check deprecations, default-setting changes, preparation steps, and operating system requirements.
- Validate application compatibility with the module versions in the target release.
Plan database upgrades where needed.
- Before upgrading the cluster, upgrade any databases running a Redis version that the target cluster version does not support.
- If also upgrading databases to Redis 7.4 or 8.x, review the database-level breaking changes.
- Follow the database upgrade procedure for database upgrades.
3. Test and complete pre-upgrade checks
Validate the upgrade in a non-production environment first.
- Test application behavior and the upgrade procedure in staging or pre-production.
- Run rlcheck on every node and confirm that no node is in maintenance mode.
- Review the prerequisites and node sequencing for your chosen method in the cluster upgrade procedure.
- If the operating system also needs upgrading, review the operating system upgrade procedure.
4. Follow the procedure for your deployment
| Deployment | Upgrade approach | Procedure |
| Redis Software cluster | In-place or rolling upgrade | Upgrade a Redis Software cluster |
| Active-Active databases (CRDBs) | Cluster by cluster | Upgrade Active-Active databases |
| Redis for Kubernetes | Operator-driven rolling upgrade | Upgrade Redis Enterprise for Kubernetes |
Plan for the availability impact of your chosen method.
- An in-place upgrade may briefly interrupt active connections as each node is upgraded.
- The official cluster upgrade guide describes rolling upgrades as a way to minimize downtime and recommends them for production environments that require continuous availability.
What happens after EOL
Redis Software 7.8 clusters continue running after May 30, 2027, with the following limitations.
- The 7.8 line no longer receives security patches, CVE fixes, bug fixes, or maintenance releases.
- Support for 7.8-specific issues is limited according to your subscription agreement. Redis Support may require an upgrade before investigating an issue.
- Remaining on an unsupported version increases security and compliance risk.
See the Redis Software product lifecycle for the lifecycle policy.
Get help with upgrade planning
Contact Redis before starting if the target version, compatibility, or sequencing is unclear.
- If you have an assigned Technical Account Manager, contact your TAM to build an upgrade plan.
- If you do not have an assigned TAM, open a Redis Support ticket for help assessing readiness and sequencing.
- If you need more time, contact your account team or Redis Support before the EOL date to discuss your situation.
0 comments
Please sign in to leave a comment.