ValkeyImage
ValkeyImage registers a Valkey container image the Momento Valkey Operator is allowed to run. It is the allowlist: if no ValkeyImage exists for an image, no ValkeyCluster can use it. Platform teams manage these resources; see Curating images and configs for the workflow.
Resource metadata
| API group/version | valkey.gomomento.com/v1alpha1 |
| Kind | ValkeyImage |
| Plural | valkeyimages |
| Scope | Cluster |
Spec
| Field | Type | Required | Default | Validation | Description |
|---|---|---|---|---|---|
repository | string | Yes | — | none | Container image repository, for example valkey/valkey. |
tag | string | Yes | — | none | Container image tag, for example 9.0.0. |
version | string | Yes | — | none | The Valkey version the image provides, for example 9.0.0. |
The operator resolves a cluster's image at reconcile time by following ValkeyCluster.spec.configRef to a ValkeyConfig, then the config's imageRef to a ValkeyImage. If the referenced ValkeyImage does not exist, resolution fails and the cluster does not progress. This is where the allowlist is enforced.
Shard scaling uses server-side slot migration commands that require Valkey 9 or later. Unless a cluster will never be resharded, register Valkey 9+ images. See Compatibility.
Status
ValkeyImage has a status subresource, but it defines no fields today.