Check out the Infer() Summit 2026 recordings!
Momento
Talk to sales

Valkey Operator

For platform teams who can't afford surprises

Operate Valkey on any Kubernetes service with robust control systems hardened for web-scale platform engineering and safe cluster management under load.

Contact Sales Read the docs

  1. Build on a stable foundation

    Deploy proven infrastructure that powers mission-critical features for millions of users around the world.

  2. Embedded governance

    Ensure compliance by codifying operational policies and organizational architecture into infrastructure.

  3. Ship quickly and safely

    Streamline cloud operations with powerful tools and the full support of Momento's systems engineering experts.

Core Features

  1. Purpose-built CRDs

    Custom Resource Definitions provide clear, independent control over engine, node, and cluster configurations.

  2. Direct pod lifecycle management

    The operator directly controls pods during critical moments like rolling updates or traffic spikes, avoiding edge cases introduced by StatefulSets or Deployments.

  3. Express policies through RBAC

    Enforce platform standards at the infrastructure layer by publishing Valkey engine and node CRDs protected with Kubernetes-native RBAC.

  4. Flexible namespacing

    Deploy any number of Valkey clusters in a single namespace with full isolation. You determine the best approach for your internal platform.

Pricing

Valkey Operator (self-managed)

Managed Capacity Total configured storage for Valkey instances managed by the operator.
$3.50 per GB-month

Frequently Asked Questions

Which Kubernetes distributions are supported?

The Momento Valkey Operator is compatible with any CNCF-conformant Kubernetes distribution, including EKS, GKE, AKS, and on-premise clusters running Kubernetes 1.24 or later.

How does this differ from the official Valkey or Redis operator?

The Momento operator uses direct pod management instead of StatefulSets, supports multiple clusters per namespace, and gives you explicit control over engine versions, areas where the official operator requires workarounds or reduces your control.

Can I run multiple Valkey clusters in the same namespace?

Yes. The Momento Valkey Operator supports any number of clusters within a single namespace.

How do I control which Valkey version is deployed?

Engine version is declared explicitly in the ValkeyImage CRD. The operator will never perform an automatic engine upgrade, version changes are always deliberate and operator-initiated.

What RBAC permissions does the operator require?

The operator requires standard RBAC permissions for managing pods, services, and ConfigMaps within its managed namespaces, plus CRD install permissions at setup time. A full permissions manifest is included in the Helm chart.