Release notes

v0.1.5

Summary

This release significantly improves Managed Valkey operability and release process maturity. Webhook and controller now run as separate components, Valkey configuration is delivered through a ConfigMap and applied by the agent without a pod restart, and the module ships its own CRDs, documentation and structured bilingual release notes.

Highlights

• Webhook and controller are split into separate deployments.
• Valkey configuration is delivered via ConfigMap and applied by the agent to a live instance, without a pod restart.
• Reload TLS certs in a running Valkey instance without restarting the pod.
• Release notes/changelog flow is now bilingual and CI-automated.

v0.1.4

Improvements

• valkey-json is included in the standard delivery.
• The certificate TTL is reported in the Valkey resource status.

Fixes

• Minor fixes in how the resource status is composed.

v0.1.3

Improvements

• Every Valkey pod now gets a managed-agent native sidecar, which watches the Valkey configuration and updates it on changes in the CR.
• Added TLS support in two modes: CertManager and CustomCertificate.

Fixes

• Roles for resources have been updated in accordance with RBAC v1.

Miscellaneous

• Go updated to 1.26.3 (was 1.25.7).

v0.1.2

Improvements

• Added a mutating webhook for ValkeyClass, so class defaults are applied on admission.
• The operator readiness probe now waits for the controller cache to be synced before reporting readiness.
• The operator is deployed on master nodes with a high availability strategy and replica count.

Fixes

• Added migrations for legacy objects created without module labels, and removal of the deprecated class.
• Fixed a panic in the operator when updating a condition while status.conditions is nil.

v0.1.1

First release of the Managed Valkey module. This version implements the basic capabilities for deploying and managing Valkey instances (a Redis-compatible in-memory data store) in a DKP cluster.

Features

Creating standalone Valkey instances

Added the namespaced Valkey CRD, which deploys a standalone Valkey instance. When creating a resource, the user specifies compute resources (CPU cores and core fraction, memory), storage parameters and the Valkey configuration.

Configuration templates via ValkeyClass

Added the cluster-wide ValkeyClass CRD, which allows administrators to create named templates for instances. Every Valkey resource must reference an existing class, and its configuration is checked against that class before the service is deployed. A class defines the allowed sizing policies, the list of configuration parameters a user may override, class-level configuration values and custom validation rules.

When the module is enabled, a ValkeyClass named default is created automatically.

Validation via webhooks

All create and update operations on Valkey and ValkeyClass resources go through admission webhooks. The webhooks verify the correctness of parameters: sizing policies of the associated class, the whitelist of overridable configuration parameters, and custom rules set by the administrator.

Custom CEL validation rules

Administrators can define arbitrary validation rules for Valkey resources in ValkeyClass using CEL (Common Expression Language) expressions, which allows organization-specific constraints to be implemented without changing the operator’s code.

Service state in the resource status

The state of the service is reflected in the conditions of the Valkey resource.

Support for distroless images

Valkey images are based on the distroless architecture, which improves security by minimizing the number of components in the container.