Deckhouse Standard Edition

managed-valkey

moduleSubsystem: Managed Services ·Documentation
Changes on Beta
newest first · a suspension is a segment, a rollback is a step back
0.1.5·arrival time on the release channel unknown

That is the whole history

0.1.5

AlphaBetaEarly AccessStableRock Solid
Dates
released 05.09.2026 00:03 detected 05.10.2026 01:20
Requirements
  • deckhouse ≥ 1.72
  • kubernetes ≥ 1.30
Stage
Preview
On release channels
Alpha — since unknown · Beta — since unknown · Early Access — since unknown · Stable — since unknown · Rock Solid — since unknown
Before
never
What changed in 0.1.5

Improvements 4

  • Introduce bilingual MR changelog/release-notes workflow with CI sync to changes/unreleased and release freeze flow0.1.5duplicate not checked
  • Update release/bundle werf stages for structured release artifacts and changelog OCI packaging0.1.5duplicate not checked
  • CRD moved from operator to module repository together with ru documentation overlays0.1.5duplicate not checked
  • Ship docs, openapi and CRDs inside bundle and release images0.1.5duplicate not checked

Fixes 3

  • The agent now reacts only to its own server TLS secret and caches only TLS-type secrets, so foreign TLS secrets in the same namespace no longer trigger reconciles of another Valkey instance0.1.5duplicate not checked
  • The admission webhook now runs the same flavour selection on update as on create, so a Valkey update with CPU outside the class sizing policies is rejected at admission instead of failing later0.1.5duplicate not checked
  • Reconcile the finalizer through the meta-operator finalizer reconciler when the ValkeyClass is already deleted, instead of returning from reconcile early — deleting a Valkey no longer leaves the finalizer in place and hangs the namespace in Terminating0.1.5duplicate not checked

Other 3

  • Split admission webhook and controller into separate deployments for clearer operation and scaling0.1.5duplicate not checked
  • Valkey configuration is delivered via a ConfigMap and applied by the agent to a live instance, without restarting the pod0.1.5duplicate not checked
  • Reload TLS certs in a running Valkey instance without restarting the pod0.1.5duplicate not checked

0.1.4 — changelog not loaded yet: the version metadata image has not been read

0.1.3 — changelog not loaded yet: the version metadata image has not been read

0.1.2 — changelog not loaded yet: the version metadata image has not been read

0.1.1 — changelog not loaded yet: the version metadata image has not been read

0.1.0 — changelog not loaded yet: the version metadata image has not been read

10 entries without a PR number: duplicates not checked