New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replace Redis with ValKey #17892
Comments
I'd be happy to give writing an enhancement proposal a go, feel free to assign me and provide any pointers if there is anything i missed or should specifically be addressed for this case. |
i put together a draft in #17904 and i hope it's not to ranty, any feedback is appreciated |
i mentioned this effort in the ValKey discussion boards as well: https://github.com/orgs/valkey-io/discussions/340 |
Also see manifests/ha/base/redis-ha and manifests/ha/base/redis-ha/chart/requirements.yaml For HA install of ArgoCD, the redis-ha configuration is provided by a 3rd party helm chart: https://github.com/DandyDeveloper/charts/tree/master/charts/redis-ha |
Summary
Redis Inc announced that they are changing Redis' license to the source available BUSL license here which is in violation of CNCF policy and does not align with the Argo Projects values.
The BSD-3-Clause licensed Redis OSS code has now been forked as ValKey in an effort hosted by the Linux Foundation.
After ValKey's first generally available (GA) release and stable release it is time to start replacing Redis.
Prior to this issue, the change was discussed here: #17599
Motivation
Taking swift action when this kind of change happens in our supply chain is a the core of upholding our opensource values.
Proposal
I propose to write a Argo CD enhancement proposal in
docs/proposals/valkey.md
to further detail this architecture decision and to then implement it by replacing the manifests in manifests/base/redis along with proper documentation to communicate this change.The text was updated successfully, but these errors were encountered: