New memory database service based on Valkey

[ricsanfre]

Scope

• Deploy new common memory database service based on Valkey.
  • Valkey is a Redis fork backed by Linux Foundation created after Redis license change.
• Migrate Oauth2-proxy to use new Valkey external service instead of deploying its own based in Redis
  • Oauth-Proxy deploy Redis cluster as subchart DandyDeveloper/redis-ha helm chart
  • Valkey support Redis protocol and should be valid for Oauth-Proxy [Feature]: Support for Redis alternatives oauth2-proxy/oauth2-proxy#2572

Requirements

• HA deployment of Memory database. Valkey cluster deployment
• Enable Observability

[ricsanfre]

Valkey Deployment Options

Helm Charts

• Bitnami does provide a Helm Chart (https://github.com/bitnami/charts/tree/main/bitnami/valkey). But due to recent changes in Bitnami Public Images catalog is not an option
• Valkey community does provide a Helm Chart to deploy Valkey: https://github.com/valkey-io/valkey-helm
  • It does not support cluster deployment yet: Cluster support valkey-io/valkey-helm#18
    • PR to be merged to fix this: feat: support Valkey Cluster with sharding valkey-io/valkey-helm#116

Operator

• There is a Valkey Kubernetes Operator: https://github.com/hyperspike/valkey-operator
  • It seems not well maintained
• Valkey community also have intentions to develop a Kuberentes Operator. See initial discussion in Create valkey-k8s-operator valkey-io/valkey-rfc#28

[ricsanfre]

Even when Oauth-proxy have been deprecated, it is still a requirement to deploy a memory database so it can be used by demo applications used to try microservices architectures out.

Valkey community new operator https://github.com/valkey-io/valkey-operator. First beta 0.1.0 recently released.