You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @Nuranto. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.
Add a comment to assign the issue: @magento I am working on this
To learn more about issue processing workflow, refer to the Code Contributions.
Join Magento Community Engineering Slack and ask your questions in #github channel. ⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.
Description
The same scenario as Elasticsearch/Opensearch is happening with Redis/Valkey (starting from Redis 7.4).
Shouldn't Valkey support be added too ? (and drop redis support in 2.4.8 ?)
(Technically, valkey is at the moment just a fork of redis, so it will work fine. But official support would be reassuring for long-term usage)
https://valkey.io/about/
Note that bitnami stopped supporting latest security updates from 7.2 : bitnami/charts#29798
Let's dream : could be the occasion for a refactoring (by dropping colinmollenhour libraries dependency, and rewrite a clean implementation in magento's framework) that would solves all redis-related issues https://github.com/magento/magento2/issues?q=is%3Aissue+is%3Aopen+redis
The text was updated successfully, but these errors were encountered: