Valkey support ?

[Nuranto]

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

[m2-assistant]

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.

• For more details, review the Magento Contributor Assistant documentation.
• 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.

[ctadlock]

In AWS; Valkey requires all connections to use TLS which from what I have found Magento2 does not support. When setting up Valkey you must manually configure an instance/cluster to disable "encryption during transit"; serverless requires it to be enabled.

Once magento supports TLS then it will be fully supported.

[ctadlock]

In AWS; Valkey requires all connections to use TLS which from what I have found Magento2 does not support. When setting up Valkey you must manually configure an instance/cluster to disable "encryption during transit"; serverless requires it to be enabled.

Once magento supports TLS then it will be fully supported.

Found this link and confirmed it works with AWS Valkey. However AWS Valkey serverless is a cluster so it doesnt support multiple databases per cluster; only database 0. So need to use seperate clusters for cache and session.

https://dev.to/mayconheerdt/magento2-redis-tls-1i3k

[barbrick]

Found this link and confirmed it works with AWS Valkey. However AWS Valkey serverless is a cluster so it doesnt support multiple databases per cluster; only database 0. So need to use seperate clusters for cache and session.

https://dev.to/mayconheerdt/magento2-redis-tls-1i3k

@ctadlock To confirm, are you saying you have AWS Valkey working with Magento 2 in serverless mode? Do you not get the below error when Redis/Valkey is in a cluster?

CROSSSLOT Keys in request don't hash to the same slot

[warp3r]

Besides a rewrite on how Magento approaches connecting and handling data in redis, right now the requirements on documentation state that you need redis 7.2.

There is no mention of compatibility at all with valkey (neither for AWS, GCP, Azure versions, or the self hosted)

is there any plan for this to be reviewed?

[thomas-kl1]

Valkey support is added in Magento 2.4.8.

[MagePsycho]

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

What about this one?

[thomas-kl1]

@MagePsycho I'm not part of Adobe, so I don't know, but I guess the community can drive this change as a separate project or with a PR

[engcom-Bravo]

@thomas-kl1 Thanks for your Contribution!!.

As per this comment #39242 (comment) valkey support was added.Hence we are closing this issue.

Thanks.