The module lifecycle stage: Preview

Valkey

A namespaced resource that allows creating the final configuration and serves as the source of truth for the state of a specific deployed valkey service.

ValkeyClassName

The name of the class that will be associated with a specific resource.
Without a created ValkeyClass, deploying the service is impossible.

spec:
  valkeyClassName: default

Instance

A section that describes the resources of the service being created.
Must pass validation according to the sizingPolicy of the corresponding class:

spec:
  instance:
    memory:
      size: 1Gi
    cpu:
      cores: 1
      coreFraction: 50
    persistentVolumeClaim:
      size: 1Gi
      storageClassName: default

Configuration

A section describing the configuration of the valkey service.
Must pass validation according to the overridableConfiguration and validations of the corresponding class:

spec:
  configuration:
    maxMemory: "512Mi"
    maxMemoryPolicy: Volatile-lfu

Supported Valkey Versions

The only supported Valkey version is 9.0.1

Our images for running Valkey containers are based on distroless architecture.

Status

The status of the Managed Valkey service is reflected in the Valkey resource.
The Conditions structure clearly shows the current status of the service

Significant types:

  • LastValidConfigurationApplied - An aggregating type that shows whether the last valid configuration has been successfully applied at least once.
  • ConfigurationValid - shows whether the configuration has passed all validations of the associated ValkeyClass.
  • ScaledToLastValidConfiguration - shows whether the number of running replicas matches the specified configuration.
  • Available - shows whether the master replica of the service is running and accepting connections.
  • UsersSynced - shows whether all users have been synchronized and brought to the described state.
  • DatabasesSynced - shows whether all logical databases have been synchronized and brought to the described state.
conditions:
    - lastTransitionTime: '2025-09-22T23:20:36Z'
      observedGeneration: 2
      status: 'True'
      type: Available
    - lastTransitionTime: '2025-09-22T14:38:04Z'
      observedGeneration: 2
      status: 'True'
      type: ConfigurationValid
    - lastTransitionTime: '2025-09-22T14:38:06Z'
      observedGeneration: 2
      status: 'True'
      type: DatabasesSynced
    - lastTransitionTime: '2025-09-22T14:38:47Z'
      observedGeneration: 2
      status: 'True'
      type: LastValidConfigurationApplied
    - lastTransitionTime: '2025-09-22T23:20:36Z'
      observedGeneration: 2
      status: 'True'
      type: ScaledToLastValidConfiguration
    - lastTransitionTime: '2025-09-22T14:38:05Z'
      observedGeneration: 2
      status: 'True'
      type: UsersSynced

A False status indicates a problem at one stage or another, or incomplete state synchronization.
For such a state, a reason and message with a description will be specified.

---
    - lastTransitionTime: '2025-09-23T14:53:33Z'
      message: Syncing
      observedGeneration: 1
      reason: Syncing
      status: 'False'
      type: LastValidConfigurationApplied
    - lastTransitionTime: '2025-09-23T14:54:58Z'
      message: Not all the instances are running still waiting for 1 to become ready
      observedGeneration: 1
      reason: ScalingInProgress
      status: 'False'
      type: ScaledToLastValidConfiguration
---

Usage Examples

Basic Usage

Without persistent data storage.

  1. Create a namespace named valkey.
  2. Create a Valkey resource
kubectl apply -f managed-services_v1alpha1_valkey.yaml -n valkey

apiVersion: managed-services.deckhouse.io/v1alpha1
kind: Valkey
metadata:
  name: valkey-sample
spec:
  valkeyClassName: default
  configuration:
    maxMemory: "256Mi"
    maxMemoryPolicy: Volatile-lfu
    save: ""
    appendOnly: "No"
  instance:
    memory:
      size: "512Mi"
    cpu:
      cores: 1
      coreFraction: "25%"
    persistentVolumeClaim:
      size: "1Gi"
  1. Wait until the cluster is created and all conditions are True:
  kubectl get valkey valkey-sample -n valkey -o wide -w
  1. To connect, use the redis-cli client and the d8ms-vlk-valkey-sample service
  redis-cli -h d8ms-vlk-valkey-sample -p 6379

Using AOF Storage

  1. Create a namespace named valkey.
  2. Create a Valkey resource
kubectl apply -f managed-services_v1alpha1_valkey.yaml -n valkey

apiVersion: managed-services.deckhouse.io/v1alpha1
kind: Valkey
metadata:
  name: valkey-sample
spec:
  valkeyClassName: default
  configuration:
    maxMemory: "256Mi"
    maxMemoryPolicy: Volatile-lfu
    save: ""
    appendOnly: "Yes"
  instance:
    memory:
      size: "512Mi"
    cpu:
      cores: 1
      coreFraction: "50%"
    persistentVolumeClaim:
      size: "1Gi"
  1. Wait until the cluster is created and all conditions are True:
  kubectl get valkey valkey-sample -n valkey -o wide -w
  1. To connect, use the redis-cli client and the d8ms-vlk-valkey-sample service
  redis-cli -h d8ms-vlk-valkey-sample -p 6379

Using RDB Storage

  1. Create a namespace named valkey.
  2. Create a Valkey resource
kubectl apply -f managed-services_v1alpha1_valkey.yaml -n valkey

apiVersion: managed-services.deckhouse.io/v1alpha1
kind: Valkey
metadata:
  name: valkey-sample
spec:
  valkeyClassName: default
  configuration:
    maxMemory: "256Mi"
    maxMemoryPolicy: Volatile-ttl
    save: "60 5"
    appendOnly: "No"
  instance:
    memory:
      size: "512Mi"
    cpu:
      cores: 1
      coreFraction: "50%"
    persistentVolumeClaim:
      size: "1Gi"
  1. Wait until the cluster is created and all conditions are True:
  kubectl get valkey valkey-sample -n valkey -o wide -w
  1. To connect, use the redis-cli client and the d8ms-vlk-valkey-sample service
  redis-cli -h d8ms-vlk-valkey-sample -p 6379