Alauda Cache Service E2
  • English

    • Lifecycle Policy

    This page distinguishes published product facts from lifecycle information that has not yet been established for Alauda Cache Service E2.

    TOC

    Current release baselineVersion dimensionsSupported-version rulePlanning requirements

    Current release baseline

    Item2.0.0 status
    Product releaseNext major release
    Supported Valkey server lines7.2, 8.1, and 9.1
    Release dateNot yet published
    End of full supportNot yet published
    End of maintenanceNot yet published
    Alauda Container Platform compatibility matrixNot yet published

    Do not derive product support dates from the upstream Valkey lifecycle. Product, Operator, server-image, and platform support are separate compatibility dimensions.

    Version dimensions

    VersionWhat it controlsHow to inspect it
    Product versionInstalled Alauda Cache Service E2 package and OperatorInspect the installed package metadata and Operator image.
    API versionKubernetes resource schemakubectl api-resources --api-group=rds.valkey.buf.red
    Server lineValkey process created for an instanceRead spec.version, inspect every data Pod image, and run INFO server on every data Pod. status.lastVersion alone is not runtime proof.
    Container imageExact delivered server or Operator buildInspect the relevant Deployment or Pod specification.

    Upgrading the product does not by itself change spec.version on existing instances. Upgrade each server line explicitly with the instance upgrade procedure.

    Supported-version rule

    The 2.0.0 Operator image map selects 7.2, 8.1, and 9.1. The inspected image-source baseline builds patch versions 7.2.14, 8.1.9, and 9.1.1. Exact patch versions and digests still must be read from the delivered images. Generated schema enum values for 8.0 or 9.0 are not a support commitment; do not create or upgrade an instance to those values.

    The API source and canonical generated custom resource definition (CRD) include 9.1, but the inspected Helm Chart CRD copy is stale and omits it. Verify the installed CRD during release acceptance; a supported package must admit all three supported lines.

    Inventory all instance versions with:

    kubectl get valkey -A \
  -o custom-columns='NAMESPACE:.metadata.namespace,NAME:.metadata.name,ARCH:.spec.arch,DESIRED:.spec.version,LAST_RECORDED:.status.lastVersion,PHASE:.status.phase'

    status.lastVersion is a controller bookkeeping value derived from the desired version during reconciliation. It does not establish that every Pod has rolled out or that every process runs the desired line.

    Planning requirements

    Before a production rollout or upgrade, obtain the release-specific information that is not defined in this repository:

    • the final release date and supported platform versions;
    • the supported source-to-target product upgrade paths;
    • component image digests and security advisories;
    • release-specific backup, rollback, and support procedures;
    • the tested Valkey server source-to-target upgrade matrix;
    • confirmation that any requested module exists in the delivered image and is compatible with the target server.

    If any of these inputs is missing, validate the change in a representative test cluster and treat production rollout as pending product-owner confirmation.