feat: ValkeyNode integration with ValkeyCluster

[jdheyburn]

• ValkeyCluster creates ValkeyNode instances over managing deployments directly.
• Introduces StatefulSets as a workload Type
  • This is the new default, with an option to deploy Deployment too
• Splits out multiple config/samples of ValkeyCluster

What this PR does not include (and will be fixed in subsequent PRs):

• Updates to ValkeyNodes (i.e. image changes)
  • This mimics the current behaviour

What this PR unblocks:

• Live config reconciliation (avoiding pod rolls if necessary)
  • Will also address the temporary ScriptsConfigMapName and UsersACLSecretName fields on ValkeyNode
• Persistent volume management

What can be improved after this PR is merged:

• ValkeyNode ROLE reconciliation
  • Can report an incorrect role for up to 1m
• More e2e tests...?

Below after applying config/samples/v1alpha1_valkeycluster.yaml

$ kg valkeynode
NAME                 READY   ROLE      POD                           AGE
cluster-sample-0-0   true    primary   valkey-cluster-sample-0-0-0   3m49s
cluster-sample-0-1   true    replica   valkey-cluster-sample-0-1-0   3m49s
cluster-sample-1-0   true    primary   valkey-cluster-sample-1-0-0   3m49s
cluster-sample-1-1   true    replica   valkey-cluster-sample-1-1-0   3m49s
cluster-sample-2-0   true    primary   valkey-cluster-sample-2-0-0   3m49s
cluster-sample-2-1   true    replica   valkey-cluster-sample-2-1-0   19s

Deploying this yaml:

apiVersion: valkey.io/v1alpha1
kind: ValkeyCluster
metadata:
  name: cluster-sample-deployment
spec:
  shards: 3
  replicas: 1
  workloadType: Deployment
  resources:
    requests:
      memory: "256Mi"
      cpu: "100m"
    limits:
      memory: "512Mi"
      cpu: "500m"
  containers:
    - name: metrics-exporter
      image: oliver006/redis_exporter:v1.82.0

Deploys this:

$ kg valkeynode
NAME                            READY   ROLE      POD                                                     AGE
cluster-sample-deployment-0-0   true    primary   valkey-cluster-sample-deployment-0-0-7c94f6d589-5kp5t   20s
cluster-sample-deployment-0-1   true    replica   valkey-cluster-sample-deployment-0-1-784d8c999f-jqzjb   20s
cluster-sample-deployment-1-0   true    primary   valkey-cluster-sample-deployment-1-0-6c66c58f8c-xm74t   20s
cluster-sample-deployment-1-1   true    replica   valkey-cluster-sample-deployment-1-1-74c4dd5d57-fjdnc   20s
cluster-sample-deployment-2-0   true    primary   valkey-cluster-sample-deployment-2-0-75dc8dbcd9-7pbrz   20s
cluster-sample-deployment-2-1   true    replica   valkey-cluster-sample-deployment-2-1-6f8d757c59-9tv64   20s

And the container merge traverses to the pod (the default exporter version is 1.80.0):

$ kgpo valkey-cluster-sample-deployment-2-1-6f8d757c59-9tv64 -o yaml G redis_exporter
    image: oliver006/redis_exporter:v1.82.0
    image: docker.io/oliver006/redis_exporter:v1.82.0
    imageID: docker.io/oliver006/redis_exporter@sha256:6a97d4dd743b533e1f950c677b87d880e44df363c61af3f406fc9e53ed65ee03

[bjosv]

Looks good, added some questions

[bjosv]

Nice!