[Features] Valkey Support

[gabrieloandco]

What is the user interaction of your feature
User should be able to deploy Valkey Clusters

Is your feature request related to a problem? Please describe.
We can't use Redis due to licencing constraints

If this is a new feature, please describe the motivation and goals.
Valkey should be a database engine supported by the project similar to what Redis already is https://kubeblocks.io/docs/preview/kubeblocks-for-redis/03-topologies/01-standlone

Describe the solution you'd like
Valkey Databases should be created with the same deploying model that Redis currently has (Santandalone, Replication and Sharding)

Describe alternatives you've considered
Be able to easily switch the images of the Components to use valkey's

Additional context
https://valkey.io/

[shanshanying]

HI @gabrieloandco

Valkey is an open-source alternative to Redis. If the assumption holds that the two share exactly the same set of commands. Then it would be quite easy for KB to support Valkey.

here is the steps if you don't want to write any code or modify existing redis addons:

1. KubeBlocks is installed and running
2. Redis Addon is enabled. (refer to : https://kubeblocks.io/docs/preview/kubeblocks-for-redis/02-quickstart for details)
3. create a new ComponentVersion for Valkey for valkey images:

apiVersion: apps.kubeblocks.io/v1
kind: ComponentVersion
metadata:
  annotations:
    kubeblocks.io/crd-api-version: apps.kubeblocks.io/v1
    meta.helm.sh/release-name: redis
  name: valkey
spec:
  compatibilityRules:
  - compDefs:
    - redis-7
    releases:
    - 7.2.9-valkey
  - compDefs:
    - redis-8
    releases:
    - 8.1.2-valkey
  releases:
  - images:
      accountProvision: docker.io/valkey/valkey:7.2.9
      init-dbctl: docker.io/apecloud/dbctl:0.1.7
      metrics: docker.io/apecloud/agamotto:0.1.2-beta.1
      postProvision: docker.io/valkey/valkey:7.2.9
      redis: docker.io/valkey/valkey:7.2.9
      switchover: docker.io/valkey/valkey:7.2.9
    name: 7.2.9-valkey
    serviceVersion: 7.2.9-valkey
  - images:
      accountProvision: docker.io/valkey/valkey:8.1.2
      init-dbctl: docker.io/apecloud/dbctl:0.1.7
      metrics: docker.io/apecloud/agamotto:0.1.2-beta.1
      postProvision: docker.io/valkey/valkey:8.1.2
      redis: docker.io/valkey/valkey:8.1.2
      switchover: docker.io/valkey/valkey:8.1.2
    name: 8.1.2-valkey
    serviceVersion: 8.1.2-valkey

This ComponentVersion defines two Redis releases using Valkey images:

1. Version 7.2.9-valkey: Compatible with redis-7 component definition
   Uses Valkey's Redis 7.2.9 image for core Redis and operational tasks
2. Version 8.1.2-valkey: Compatible with redis-8 component definition
   Uses Valkey's Redis 8.1.2 image for core Redis and operational tasks

Then you can create a Valkey Standalone Cluster with serviceVersion: 8.1.2-valkey

apiVersion: apps.kubeblocks.io/v1
kind: Cluster
metadata:
  name: rose69
  namespace: default
spec:
  clusterDef: redis
  componentSpecs:
  - disableExporter: true
    name: redis
    replicas: 1
    resources:
      limits:
        cpu: "0.5"
        memory: 0.5Gi
      requests:
        cpu: "0.5"
        memory: 0.5Gi
    serviceVersion: 8.1.2-valkey   # set it to the service version define in previous steps.
    volumeClaimTemplates:
    - name: data
      spec:
        accessModes:
        - ReadWriteOnce
        resources:
          requests:
            storage: 20Gi
  terminationPolicy: Delete
  topology: standalone

[shanshanying]

and you may refer to this draft #1776 for more details

[gabrieloandco]

Thanks! This manifest worked for us

apiVersion: apps.kubeblocks.io/v1
kind: ComponentVersion
metadata:
  annotations:
    kubeblocks.io/crd-api-version: apps.kubeblocks.io/v1
  name: valkey
spec:
  compatibilityRules:
  - compDefs:
    - redis-cluster-7
    - redis-7
    releases:
    - 7.2.6-valkey
    - 7.2.9-valkey
  - compDefs:
    - redis-8
    releases:
    - 8.1.2-valkey
  releases:
  - images:
      init-dbctl: docker.io/apecloud/dbctl:0.1.7
      metrics: docker.io/apecloud/agamotto:0.1.2-beta.1
      redis-cluster: docker.io/valkey/valkey:7.2.6
      redis: docker.io/valkey/valkey:7.2.6
      postProvision: docker.io/valkey/valkey:7.2.6
      accountProvision: docker.io/valkey/valkey:7.2.6
      switchover: docker.io/valkey/valkey:7.2.6
      preTerminate: docker.io/valkey/valkey:7.2.6
      memberLeave: docker.io/valkey/valkey:7.2.6
    name: 7.2.6-valkey
    serviceVersion: 7.2.6-valkey
  - images:
      init-dbctl: docker.io/apecloud/dbctl:0.1.7
      metrics: docker.io/apecloud/agamotto:0.1.2-beta.1
      redis-cluster: docker.io/valkey/valkey:7.2.9
      redis: docker.io/valkey/valkey:7.2.9
      ostProvision: docker.io/valkey/valkey:7.2.9
      accountProvision: docker.io/valkey/valkey:7.2.9
      switchover: docker.io/valkey/valkey:7.2.9
      preTerminate: docker.io/valkey/valkey:7.2.9
      memberLeave: docker.io/valkey/valkey:7.2.9
    name: 7.2.9-valkey
    serviceVersion: 7.2.9-valkey
---
apiVersion: apps.kubeblocks.io/v1
kind: ComponentVersion
metadata:
  annotations:
    kubeblocks.io/crd-api-version: apps.kubeblocks.io/v1
  name: valkey-cluster
spec:
  compatibilityRules:
  - compDefs:
    - redis-cluster-7
    - redis-7
    releases:
    - 7.2.6-valkey
    - 7.2.9-valkey
  releases:
  - images:
      init-dbctl: docker.io/apecloud/dbctl:0.1.7
      metrics: docker.io/apecloud/agamotto:0.1.2-beta.1
      redis-cluster: docker.io/valkey/valkey:7.2.6
      redis: docker.io/valkey/valkey:7.2.6
      postProvision: docker.io/valkey/valkey:7.2.6
      accountProvision: docker.io/valkey/valkey:7.2.6
      switchover: docker.io/valkey/valkey:7.2.6
      preTerminate: docker.io/valkey/valkey:7.2.6
      memberLeave: docker.io/valkey/valkey:7.2.6
    name: 7.2.6-valkey
    serviceVersion: 7.2.6-valkey
  - images:
      init-dbctl: docker.io/apecloud/dbctl:0.1.7
      metrics: docker.io/apecloud/agamotto:0.1.2-beta.1
      redis-cluster: docker.io/valkey/valkey:7.2.9
      redis: docker.io/valkey/valkey:7.2.9
      postProvision: docker.io/valkey/valkey:7.2.9
      accountProvision: docker.io/valkey/valkey:7.2.9
      switchover: docker.io/valkey/valkey:7.2.9
      preTerminate: docker.io/valkey/valkey:7.2.9
      memberLeave: docker.io/valkey/valkey:7.2.9
    name: 7.2.9-valkey
    serviceVersion: 7.2.9-valkey
---
apiVersion: apps.kubeblocks.io/v1
kind: ComponentVersion
metadata:
  annotations:
    kubeblocks.io/crd-api-version: apps.kubeblocks.io/v1
  name: valkey-sentinel
spec:
  compatibilityRules:
  - compDefs:
    - ^redis-sentinel-7.*
    releases:
    - 7.2.6-valkey
    - 7.2.9-valkey
  releases:
  - images:
      redis-sentinel: docker.io/valkey/valkey:7.2.6
      accountProvision: docker.io/valkey/valkey:7.2.6
      memberLeave: docker.io/valkey/valkey:7.2.6
    name: 7.2.6-valkey
    serviceVersion: 7.2.6-valkey
  - images:
      redis-sentinel: docker.io/valkey/valkey:7.2.9
      accountProvision: docker.io/valkey/valkey:7.2.9
      memberLeave: docker.io/valkey/valkey:7.2.9
    name: 7.2.9-valkey
    serviceVersion: 7.2.9-valkey

However take in acoount that valkey8 and redis 8 are not cross compatible. We don't need it right now, but not sure if at the time we will need a new addon instead of overriding redis' one.