title: RedisEnterpriseDatabase API Reference

page_type: content

title: Overview

role: overview

text:
apiVersion:

- [app.redislabs.com/v1alpha1](#appredislabscomv1alpha1)

# app.redislabs.com/v1alpha1

RedisEnterpriseDatabase is the Schema for the redisenterprisedatabases API

            Name
            Type
            Description
            Required

      apiVersion
      string
      app.redislabs.com/v1alpha1
      true

      kind
      string
      RedisEnterpriseDatabase
      true

      metadata
      object
      Refer to the Kubernetes API documentation for the fields of the `metadata` field.
      true

        spec
        object

          RedisEnterpriseDatabaseSpec defines the desired state of RedisEnterpriseDatabase

        false

        status
        object

          RedisEnterpriseDatabaseStatus defines the observed state of RedisEnterpriseDatabase

        false

title: spec

role: content

text:
[↩ Parent](#)

RedisEnterpriseDatabaseSpec defines the desired state of RedisEnterpriseDatabase

            Name
            Type
            Description
            Required

        activeActive
        object

          Connection/ association to the Active-Active database.

        false

        alertSettings
        object

          Settings for database alerts

        false

        auditing
        object

          Database auditing configuration.

        false

        backup
        object

          Target for automatic database backups.

        false

        clientAuthenticationCertificates
        []string

          The Secrets containing TLS Client Certificate to use for Authentication

        false

        dataInternodeEncryption
        boolean

          Internode encryption (INE) setting. An optional boolean setting, overriding a similar cluster-wide policy. If set to False, INE is guaranteed to be turned off for this DB (regardless of cluster-wide policy). If set to True, INE will be turned on, unless the capability is not supported by the DB ( in such a case we will get an error and database creation will fail). If left unspecified, will be disabled if internode encryption is not supported by the DB (regardless of cluster default). Deleting this property after explicitly setting its value shall have no effect.

        false

        databasePort
        integer

          TCP port assigned to the database within the Redis Enterprise cluster. Must be unique across all databases in the Redis Enterprise cluster. Will be generated automatically if omitted. can not be changed after creation

        false

        databaseSecretName
        string

          Name of the secret containing the database password (Redis databases only). The secret is created automatically if it does not exist. The password is stored under the "password" key in the secret. If creating the secret manually, create an opaque secret with the password under the "password" key. To disable authentication, set the value of the "password" key in the secret to an empty string. Note: For Active-Active databases, this secret is not created automatically. For memcached databases, use memcachedSaslSecretName instead.

        false

        databaseServicePort
        integer

          A custom port to be exposed by the database Services. Can be modified/added/removed after REDB creation. If set, it'll replace the default service port (namely, databasePort or defaultRedisPort).

        false

        defaultUser
        boolean

          Allows connections with the default user. When disabled, the DatabaseSecret is not created or updated.

        false

        evictionPolicy
        string

          Database eviction policy. See https://redis.io/docs/latest/operate/rs/databases/memory-performance/eviction-policy/

        false

        isRof
        boolean

          Enables Auto Tiering (formerly Redis on Flash) for Redis databases only. Defaults to false.

        false

        memcachedSaslSecretName
        string

          Name of the secret containing credentials for memcached database authentication. Store credentials in an opaque secret with "username" and "password" keys. Note: Connections are not encrypted.

        false

        memorySize
        string

          Memory size for the database using formats like 100MB or 0.1GB. Minimum value is 100MB. For Auto Tiering (formerly Redis on Flash), this value represents RAM+Flash memory and must be at least 1GB.

        false

        modulesList
        []object

          List of modules associated with the database. The list of valid modules for the specific cluster can be retrieved from the status of the REC object. Use the "name" and "versions" fields for the specific module configuration. If specifying an explicit version for a module, automatic modules versions upgrade must be disabled by setting the '.upgradeSpec.upgradeModulesToLatest' field in the REC to 'false'. Note that the option to specify module versions is deprecated, and will be removed in future releases. for Redis version 8 and above, bundled modules are enabled automatically, so there is no need to specify them

        false

        ossCluster
        boolean

          Enables OSS cluster mode for this database. By default, advertised database topology includes the internal endpoints (pod IPs) for the Redis Enterprise nodes hosting the database shards. To enable external access, configure ossClusterSettings.enableExternalAccess for this RedisEnterpriseDatabase as well as ossClusterSettings.externalAccessType for the RedisEnterpriseCluster. Note: Not all client libraries support OSS cluster mode.

        false

        ossClusterSettings
        object

          Additional OSS cluster mode settings.

        false

        persistence
        enum

          Database persistence policy for on-disk storage.

            Enum: disabled, aofEverySecond, aofAlways, snapshotEvery1Hour, snapshotEvery6Hour, snapshotEvery12Hour

        false

        proxyPolicy
        string

          Proxy policy for the database. Supported proxy policies are: single/all-master-shards/all-nodes When left blank, the default value will be chosen according to the value of ossCluster - single if disabled, all-master-shards when enabled

        false

        rackAware
        boolean

          Enables rack awareness for improved availability. See https://redis.io/docs/latest/operate/rs/clusters/configure/rack-zone-awareness/

        false

        redisEnterpriseCluster
        object

          Connection to the Redis Enterprise Cluster.

        false

        redisVersion
        string

          Redis OSS version. Version can be specified via <major.minor> prefix, or via channels - for existing databases - Upgrade Redis OSS version. For new databases - the version which the database will be created with. If set to 'major' - will always upgrade to the most recent major Redis version. If set to 'latest' - will always upgrade to the most recent Redis version. Depends on 'redisUpgradePolicy' - if you want to set the value to 'latest' for some databases, you must set redisUpgradePolicy on the cluster before. Possible values are 'major' or 'latest' When using upgrade - make sure to backup the database before. This value is used only for database type 'redis'

        false

        replicaSources
        []object

          What databases to replicate from

        false

        replication
        boolean

          Enables in-memory database replication for higher availability. Creates a replica shard for every master shard. Defaults to false.

        false

        resp3
        boolean

          Whether this database supports RESP3 protocol. Note - Deleting this property after explicitly setting its value shall have no effect. Please view the corresponding field in RS doc for more info.

        false

        rofRamRatio
        integer

          RAM allocation ratio for Redis Flex (v2) databases as a percentage of total data size. Valid range 0-100. When omitted, RS uses the default value of 50%. Controls how much RAM is allocated per unit of data (e.g., 30% means 3MB RAM per 10MB data). RAM grows proportionally with data until rofRamSize limit is reached (if specified). Only applicable when isRof=true and Redis version >= 8.0 (BigStore v2 - Redis Flex).

            Minimum: 0

            Maximum: 100

        false

        rofRamSize
        string

          The size of the RAM portion of an Auto Tiering (formerly Redis on Flash) database. Similarly to "memorySize" use formats like 100MB, 0.1GB. It must be at least 10% of combined memory size (RAM and Flash), as specified by "memorySize".

        false

        rolesPermissions
        []object

          List of Redis Enteprise ACL and Role bindings to apply

        false

        shardCount
        integer

          Number of database server-side shards.

        false

        shardingEnabled
        boolean

          Toggles database sharding for REAADBs (Active Active databases) and enabled by default. This field is blocked for REDB (non-Active Active databases) and sharding is toggled via the shardCount field - when shardCount is 1 this is disabled otherwise enabled.

        false

        shardsPlacement
        enum

          Shard placement strategy: "dense" or "sparse". dense: Shards reside on as few nodes as possible. sparse: Shards are distributed across as many nodes as possible.

            Enum: dense, sparse

        false

        tlsMode
        enum

          Require TLS authenticated and encrypted connections to the database. enabled - all client and replication connections to the Database must use TLS. disabled - no incoming connection to the Database should use TLS. replica_ssl - databases that replicate from this one need to use TLS.

            Enum: disabled, enabled, replica_ssl

        false

        type
        enum

          Database type: redis or memcached.

            Enum: redis, memcached

        false

        upgradeSpec
        object

          Specifications for DB upgrade.

        false

title: spec.activeActive

text:
[↩ Parent](#spec)

Connection/ association to the Active-Active database.

            Name
            Type
            Description
            Required

        name
        string

          The the corresponding Active-Active database name, Redis Enterprise Active Active Database custom resource name, this Resource is associated with. In case this resource is created manually at the active active database creation this field must be filled via the user, otherwise, the operator will assign this field automatically. Note: this feature is currently unsupported.

        true

        participatingClusterName
        string

          The corresponding participating cluster name, Redis Enterprise Remote Cluster custom resource name, in the Active-Active database, In case this resource is created manually at the active active database creation this field must be filled via the user, otherwise, the operator will assign this field automatically. Note: this feature is currently unsupported.

        true

title: spec.alertSettings

text:
[↩ Parent](#spec)

Settings for database alerts

            Name
            Type
            Description
            Required

        bdb_backup_delayed
        object

          Periodic backup has been delayed for longer than specified threshold value [minutes]. -Note threshold is commented (allow string/int/float and support backwards compatibility) but is required

        false

        bdb_crdt_src_high_syncer_lag
        object

          Active-active source - sync lag is higher than specified threshold value [seconds] -Note threshold is commented (allow string/int/float and support backwards compatibility) but is required

        false

        bdb_crdt_src_syncer_connection_error
        object

          Active-active source - sync has connection error while trying to connect replica source -Note threshold is commented (allow string/int/float and support backwards compatibility) but is required

        false

        bdb_crdt_src_syncer_general_error
        object

          Active-active source - sync encountered in general error -Note threshold is commented (allow string/int/float and support backwards compatibility) but is required

        false

        bdb_high_latency
        object

          Latency is higher than specified threshold value [micro-sec] -Note threshold is commented (allow string/int/float and support backwards compatibility) but is required

        false

        bdb_high_throughput
        object

          Throughput is higher than specified threshold value [requests / sec.] -Note threshold is commented (allow string/int/float and support backwards compatibility) but is required

        false

        bdb_long_running_action
        object

          An alert for state-machines that are running for too long -Note threshold is commented (allow string/int/float and support backwards compatibility) but is required

        false

        bdb_low_throughput
        object

          Throughput is lower than specified threshold value [requests / sec.] -Note threshold is commented (allow string/int/float and support backwards compatibility) but is required

        false

        bdb_proxy_cert_expiring_soon
        object

          Proxy certificate will expire in less than specified threshold value [days]

        false

        bdb_ram_dataset_overhead
        object

          Dataset RAM overhead of a shard has reached the threshold value [% of its RAM limit] -Note threshold is commented (allow string/int/float and support backwards compatibility) but is required

        false

        bdb_ram_values
        object

          Percent of values kept in a shard's RAM is lower than [% of its key count] -Note threshold is commented (allow string/int/float and support backwards compatibility) but is required

        false

        bdb_replica_src_high_syncer_lag
        object

          Replica-of source - sync lag is higher than specified threshold value [seconds] -Note threshold is commented (allow string/int/float and support backwards compatibility) but is required

        false

        bdb_replica_src_syncer_connection_error
        object

          Replica-of source - sync has connection error while trying to connect replica source -Note threshold is commented (allow string/int/float and support backwards compatibility) but is required

        false

        bdb_shard_num_ram_values
        object

          Number of values kept in a shard's RAM is lower than [values] -Note threshold is commented (allow string/int/float and support backwards compatibility) but is required

        false

        bdb_size
        object

          Dataset size has reached the threshold value [% of the memory limit] expected fields: -Note threshold is commented (allow string/int/float and support backwards compatibility) but is required

        false

title: spec.alertSettings.bdb_backup_delayed

text:
[↩ Parent](#specalertsettings)

Periodic backup has been delayed for longer than specified threshold value [minutes]. -Note threshold is commented (allow string/int/float and support backwards compatibility) but is required

            Name
            Type
            Description
            Required

        enabled
        boolean

          Alert enabled or disabled

        false

title: spec.alertSettings.bdb_crdt_src_high_syncer_lag

text:
[↩ Parent](#specalertsettings)

Active-active source - sync lag is higher than specified threshold value [seconds] -Note threshold is commented (allow string/int/float and support backwards compatibility) but is required

            Name
            Type
            Description
            Required

        enabled
        boolean

          Alert enabled or disabled

        false

title: spec.alertSettings.bdb_crdt_src_syncer_connection_error

text:
[↩ Parent](#specalertsettings)

Active-active source - sync has connection error while trying to connect replica source -Note threshold is commented (allow string/int/float and support backwards compatibility) but is required

            Name
            Type
            Description
            Required

        enabled
        boolean

          Alert enabled or disabled

        false

title: spec.alertSettings.bdb_crdt_src_syncer_general_error

text:
[↩ Parent](#specalertsettings)

Active-active source - sync encountered in general error -Note threshold is commented (allow string/int/float and support backwards compatibility) but is required

            Name
            Type
            Description
            Required

        enabled
        boolean

          Alert enabled or disabled

        false

title: spec.alertSettings.bdb_high_latency

text:
[↩ Parent](#specalertsettings)

Latency is higher than specified threshold value [micro-sec] -Note threshold is commented (allow string/int/float and support backwards compatibility) but is required

            Name
            Type
            Description
            Required

        enabled
        boolean

          Alert enabled or disabled

        false

title: spec.alertSettings.bdb_high_throughput

text:
[↩ Parent](#specalertsettings)

Throughput is higher than specified threshold value [requests / sec.] -Note threshold is commented (allow string/int/float and support backwards compatibility) but is required

            Name
            Type
            Description
            Required

        enabled
        boolean

          Alert enabled or disabled

        false

title: spec.alertSettings.bdb_long_running_action

text:
[↩ Parent](#specalertsettings)

An alert for state-machines that are running for too long -Note threshold is commented (allow string/int/float and support backwards compatibility) but is required

            Name
            Type
            Description
            Required

        enabled
        boolean

          Alert enabled or disabled

        false

title: spec.alertSettings.bdb_low_throughput

text:
[↩ Parent](#specalertsettings)

Throughput is lower than specified threshold value [requests / sec.] -Note threshold is commented (allow string/int/float and support backwards compatibility) but is required

            Name
            Type
            Description
            Required

        enabled
        boolean

          Alert enabled or disabled

        false

title: spec.alertSettings.bdb_proxy_cert_expiring_soon

text:
[↩ Parent](#specalertsettings)

Proxy certificate will expire in less than specified threshold value [days]

            Name
            Type
            Description
            Required

        enabled
        boolean

          Alert enabled or disabled

        false

title: spec.alertSettings.bdb_ram_dataset_overhead

text:
[↩ Parent](#specalertsettings)

Dataset RAM overhead of a shard has reached the threshold value [% of its RAM limit] -Note threshold is commented (allow string/int/float and support backwards compatibility) but is required

            Name
            Type
            Description
            Required

        enabled
        boolean

          Alert enabled or disabled

        false

title: spec.alertSettings.bdb_ram_values

text:
[↩ Parent](#specalertsettings)

Percent of values kept in a shard's RAM is lower than [% of its key count] -Note threshold is commented (allow string/int/float and support backwards compatibility) but is required

            Name
            Type
            Description
            Required

        enabled
        boolean

          Alert enabled or disabled

        false

title: spec.alertSettings.bdb_replica_src_high_syncer_lag

text:
[↩ Parent](#specalertsettings)

Replica-of source - sync lag is higher than specified threshold value [seconds] -Note threshold is commented (allow string/int/float and support backwards compatibility) but is required

            Name
            Type
            Description
            Required

        enabled
        boolean

          Alert enabled or disabled

        false

title: spec.alertSettings.bdb_replica_src_syncer_connection_error

text:
[↩ Parent](#specalertsettings)

Replica-of source - sync has connection error while trying to connect replica source -Note threshold is commented (allow string/int/float and support backwards compatibility) but is required

            Name
            Type
            Description
            Required

        enabled
        boolean

          Alert enabled or disabled

        false

title: spec.alertSettings.bdb_shard_num_ram_values

text:
[↩ Parent](#specalertsettings)

Number of values kept in a shard's RAM is lower than [values] -Note threshold is commented (allow string/int/float and support backwards compatibility) but is required

            Name
            Type
            Description
            Required

        enabled
        boolean

          Alert enabled or disabled

        false

title: spec.alertSettings.bdb_size

text:
[↩ Parent](#specalertsettings)

Dataset size has reached the threshold value [% of the memory limit] expected fields: -Note threshold is commented (allow string/int/float and support backwards compatibility) but is required

            Name
            Type
            Description
            Required

        enabled
        boolean

          Alert enabled or disabled

        false

title: spec.auditing

text:
[↩ Parent](#spec)

Database auditing configuration.

            Name
            Type
            Description
            Required

        dbConnsAuditing
        boolean

          Enables auditing of database connection and authentication events.
When enabled, connection, authentication, and disconnection events are tracked and sent
to the configured audit listener (configured at the cluster level).
The cluster-level auditing configuration must be set before enabling this on a database.

        false

title: spec.backup

text:
[↩ Parent](#spec)

Target for automatic database backups.

            Name
            Type
            Description
            Required

        abs
        object

        false

        ftp
        object

        false

        gcs
        object

          GoogleStorage

        false

        interval
        integer

          Backup Interval in seconds

        false

        mount
        object

          MountPointStorage

        false

        s3
        object

        false

        sftp
        object

        false

        swift
        object

        false

title: spec.backup.abs

text:
[↩ Parent](#specbackup)

            Name
            Type
            Description
            Required

        absSecretName
        string

          The name of the K8s secret that holds ABS credentials. The secret must contain the keys "AccountName" and "AccountKey", and these must hold the corresponding credentials

        true

        container
        string

          Azure Blob Storage container name.

        true

        subdir
        string

          Optional. Azure Blob Storage subdir under container.

        false

title: spec.backup.ftp

text:
[↩ Parent](#specbackup)

            Name
            Type
            Description
            Required

        url
        string

          a URI of the ftps://[USER[:PASSWORD]@]HOST[:PORT]/PATH[/]

        true

title: spec.backup.gcs

text:
[↩ Parent](#specbackup)

GoogleStorage

            Name
            Type
            Description
            Required

        bucketName
        string

          Google Storage bucket name.

        true

        gcsSecretName
        string

          The name of the K8s secret that holds the Google Cloud Storage credentials. The secret must contain the keys "CLIENT_ID", "PRIVATE_KEY", "PRIVATE_KEY_ID", "CLIENT_EMAIL" and these must hold the corresponding credentials. The keys should correspond to the values in the key JSON.

        true

        subdir
        string

          Optional. Google Storage subdir under bucket.

        false

title: spec.backup.mount

text:
[↩ Parent](#specbackup)

MountPointStorage

            Name
            Type
            Description
            Required

        path
        string

          Path to the local mount point. You must create the mount point on all nodes, and the redislabs:redislabs user must have read and write permissions on the local mount point.

        true

title: spec.backup.s3

text:
[↩ Parent](#specbackup)

            Name
            Type
            Description
            Required

        awsSecretName
        string

          The name of the K8s secret that holds the AWS credentials. The secret must contain the keys "AWS_ACCESS_KEY_ID" and "AWS_SECRET_ACCESS_KEY", and these must hold the corresponding credentials.

        true

        bucketName
        string

          Amazon S3 bucket name.

        true

        subdir
        string

          Optional. Amazon S3 subdir under bucket.

        false

title: spec.backup.sftp

text:
[↩ Parent](#specbackup)

            Name
            Type
            Description
            Required

        sftpSecretName
        string

          The name of the K8s secret that holds SFTP credentials. The secret must contain the "Key" key, which is the SSH private key for connecting to the sftp server.

        true

        sftp_url
        string

          SFTP url

        true

title: spec.backup.swift

text:
[↩ Parent](#specbackup)

            Name
            Type
            Description
            Required

        auth_url
        string

          Swift service authentication URL.

        true

        container
        string

          Swift object store container for storing the backup files.

        true

        swiftSecretName
        string

          The name of the K8s secret that holds Swift credentials. The secret must contain the keys "Key" and "User", and these must hold the corresponding credentials: service access key and service user name (pattern for the latter does not allow special characters &,<,>,")

        true

        prefix
        string

          Optional. Prefix (path) of backup files in the swift container.

        false

title: spec.modulesList[]

text:
[↩ Parent](#spec)

Redis Enterprise module (see https://redis.io/docs/latest/develop/reference/modules/)

            Name
            Type
            Description
            Required

        name
        string

          The name of the module, e.g. "search" or "ReJSON". The complete list of modules available in the cluster can be retrieved from the '.status.modules' field in the REC.

        true

        config
        string

          Module command line arguments e.g. VKEY_MAX_ENTITY_COUNT 30 30

        false

        version
        string

          The semantic version of the module, e.g. '1.6.12'. Optional for REDB, must be set for REAADB. Note that this field is deprecated, and will be removed in future releases.

        false

title: spec.ossClusterSettings

text:
[↩ Parent](#spec)

Additional OSS cluster mode settings.

            Name
            Type
            Description
            Required

        enableExternalAccess
        boolean

          Toggles whether this database supports external access in OSS cluster mode. When enabled, advertised database topology includes the external endpoints for the Redis Enterprise nodes hosting the database shards. The external access mechanism (e.g., LoadBalancer services) is configured via the ossClusterSettings.externalAccessType field of the RedisEnterpriseCluster. When external access is enabled, the corresponding database secret will have the list of primary shard IPs in the oss_startup_nodes field.

        false

title: spec.redisEnterpriseCluster

text:
[↩ Parent](#spec)

Connection to the Redis Enterprise Cluster.

            Name
            Type
            Description
            Required

        name
        string

          The name of the Redis Enterprise Cluster where the database should be stored.

        true

title: spec.replicaSources[]

text:
[↩ Parent](#spec)

            Name
            Type
            Description
            Required

        replicaSourceName
        string

          The name of the resource from which the source database URI is derived. The type of resource must match the type specified in the ReplicaSourceType field.

        true

        replicaSourceType
        string

          The type of resource from which the source database URI is derived. If set to 'SECRET', the source database URI is derived from the secret named in the ReplicaSourceName field. The secret must have a key named 'uri' that defines the URI of the source database in the form of 'redis://...'. The type of secret (kubernetes, vault, ...) is determined by the secret mechanism used by the underlying REC object. If set to 'REDB', the source database URI is derived from the RedisEnterpriseDatabase resource named in the ReplicaSourceName field.

        true

        clientKeySecret
        string

          Secret that defines the client certificate and key used by the syncer in the target database cluster. The secret must have 2 keys in its map: "cert" which is the PEM encoded certificate, and "key" which is the PEM encoded private key.

        false

        compression
        integer

          GZIP compression level (0-6) to use for replication.

        false

        serverCertSecret
        string

          Secret that defines the server certificate used by the proxy in the source database cluster. The secret must have 1 key in its map: "cert" which is the PEM encoded certificate.

        false

        tlsSniName
        string

          TLS SNI name to use for the replication link.

        false

title: spec.rolesPermissions[]

text:
[↩ Parent](#spec)

Redis Enterprise Role and ACL Binding

            Name
            Type
            Description
            Required

        acl
        string

          Acl Name of RolePermissionType

        true

        role
        string

          Role Name of RolePermissionType

        true

        type
        enum

          Type of Redis Enterprise Database Role Permission. Currently, only "redis-enterprise" is supported, which uses roles and ACLs defined within Redis Enterprise directly.

            Enum: redis-enterprise

            Default: redis-enterprise

        true

title: spec.upgradeSpec

text:
[↩ Parent](#spec)

Specifications for DB upgrade.

            Name
            Type
            Description
            Required

        upgradeModulesToLatest
        boolean

          DEPRECATED Upgrades the modules to the latest version that supports the DB version during a DB upgrade action, to upgrade the DB version view the 'redisVersion' field. Notes - All modules must be without specifying the version. in addition, This field is currently not supported for Active-Active databases. The default is true

        true

title: status

text:
[↩ Parent](#)

RedisEnterpriseDatabaseStatus defines the observed state of RedisEnterpriseDatabase

            Name
            Type
            Description
            Required

        activeActive
        object

          Connection/ association to the Active-Active database.

        false

        backupInfo
        object

          Information on the database's periodic backup

        false

        bigstoreVersion
        integer

          BigStore version for Redis on Flash databases (1 for Auto Tiering, 2 for Redis Flex). Read-only field populated from RS.

        false

        createdTime
        string

          Time when the database was created

        false

        databaseUID
        string

          Database UID provided by redis enterprise

        false

        internalEndpoints
        []object

          Endpoints listed internally by the Redis Enterprise Cluster. Can be used to correlate a ReplicaSourceStatus entry.

        false

        lastActionStatus
        string

          Status of the last action done by operator on this database

        false

        lastActionUid
        string

          UID of the last action done by operator on this database

        false

        lastUpdated
        string

          Time when the database was last updated

        false

        observedGeneration
        integer

          The generation (built in update counter of K8s) of the REDB resource that was fully acted upon, meaning that all changes were handled and sent as an API call to the Redis Enterprise Cluster (REC). This field value should equal the current generation when the resource changes were handled. Note: the lastActionStatus field tracks actions handled asynchronously by the Redis Enterprise Cluster.

            Format: int64

        false

        redisEnterpriseCluster
        string

          The Redis Enterprise Cluster Object this Resource is associated with

        false

        replicaSourceStatuses
        []object

          ReplicaSource statuses

        false

        shardStatuses
        map[string]integer

          Aggregated statuses of shards

        false

        specStatus
        string

          Whether the desired specification is valid

        false

        status
        string

          The status of the database

        false

        version
        string

          Database compatibility version

        false

title: status.activeActive

text:
[↩ Parent](#status)

Connection/ association to the Active-Active database.

            Name
            Type
            Description
            Required

        name
        string

          The the corresponding Active-Active database name, Redis Enterprise Active Active Database custom resource name, this Resource is associated with. In case this resource is created manually at the active active database creation this field must be filled via the user, otherwise, the operator will assign this field automatically. Note: this feature is currently unsupported.

        true

        participatingClusterName
        string

          The corresponding participating cluster name, Redis Enterprise Remote Cluster custom resource name, in the Active-Active database, In case this resource is created manually at the active active database creation this field must be filled via the user, otherwise, the operator will assign this field automatically. Note: this feature is currently unsupported.

        true

title: status.backupInfo

text:
[↩ Parent](#status)

Information on the database's periodic backup

            Name
            Type
            Description
            Required

        backupFailureReason
        string

          Reason of last failed backup process

        false

        backupHistory
        integer

          Backup history retention policy (number of days, 0 is forever)

        false

        backupInterval
        integer

          Interval in seconds in which automatic backup will be initiated

        false

        backupIntervalOffset
        integer

          Offset (in seconds) from round backup interval when automatic backup will be initiated (should be less than backup_interval)

        false

        backupProgressPercentage
        integer

          Database scheduled periodic backup progress (percentage)

        false

        backupStatus
        string

          Status of scheduled periodic backup process

        false

        lastBackupTime
        string

          Time of last successful backup

        false

title: status.internalEndpoints[]

text:
[↩ Parent](#status)

            Name
            Type
            Description
            Required

        host
        string

          Hostname assigned to the database

        false

        port
        integer

          Database port name

        false

title: status.replicaSourceStatuses[]

text:
[↩ Parent](#status)

            Name
            Type
            Description
            Required

        endpointHost
        string

          The internal host name of the replica source database. Can be used as an identifier. See the internalEndpoints list on the REDB status.

        true

        lag
        integer

          Lag in millisec between source and destination (while synced).

        false

        lastError
        string

          Last error encountered when syncing from the source.

        false

        lastUpdate
        string

          Time when we last receive an update from the source.

        false

        rdbSize
        integer

          The source’s RDB size to be transferred during the syncing phase.

        false

        rdbTransferred
        integer

          Number of bytes transferred from the source’s RDB during the syncing phase.

        false

        status
        string

          Sync status of this source

        false


title: RedisEnterpriseRemoteCluster API Reference

title: Overview

text:
apiVersion:

- [app.redislabs.com/v1alpha1](#appredislabscomv1alpha1)

# app.redislabs.com/v1alpha1

RedisEntepriseRemoteCluster represents a remote participating cluster.

            Name
            Type
            Description
            Required

      apiVersion
      string
      app.redislabs.com/v1alpha1
      true

      kind
      string
      RedisEnterpriseRemoteCluster
      true

      metadata
      object
      Refer to the Kubernetes API documentation for the fields of the `metadata` field.
      true

        spec
        object

        false

        status
        object

        false

title: spec

text:
[↩ Parent](#)

            Name
            Type
            Description
            Required

        apiFqdnUrl
        string

          The URL of the cluster, will be used for the active-active database URL.

        true

        recName
        string

          The name of the REC that the RERC is pointing at

        true

        recNamespace
        string

          The namespace of the REC that the RERC is pointing at

        true

        apiPort
        integer

          The port number of the cluster's URL used for connectivity/sync

        false

        dbFqdnSuffix
        string

          The database URL suffix, will be used for the active-active database replication endpoint and replication endpoint SNI.

        false

        secretName
        string

          The name of the secret containing cluster credentials. Must be of the following format: "redis-enterprise-<RERC name>"

        false

title: status

text:
[↩ Parent](#)

            Name
            Type
            Description
            Required

        internalObservedSecretResourceVersion
        string

          The observed secret resource version. Used for internal purposes only.

        false

        local
        boolean

          Indicates whether this object represents a local or a remote cluster.

        false

        observedGeneration
        integer

          The most recent generation observed for this RERC. It corresponds to the RERC's generation, which is updated by the API Server.

        false

        specStatus
        string

          Whether the desired specification is valid.

        false

        status
        string

          The status of the remote cluster.

        false


title: Reference

summary: Resources to help you manage Redis Enterprise custom resources on Kubernetes.

summary: Support matrix for the current Redis Enterprise K8s operator

title: Supported Kubernetes distributions

summary: Reference documentation for Redis Enterprise operator APIs

title: API reference

summary: Example YAML files for deploying Redis Enterprise on Kubernetes with different configurations.

title: YAML examples

title: Overview

text: This reference documentation covers Redis Enterprise custom resources, API specifications, and practical instructions for creating, configuring, and managing Redis Enterprise deployments on Kubernetes.

title: Work with custom resources

text: Redis Enterprise for Kubernetes uses custom resources to manage clusters and databases. Use standard Kubernetes tools to create, modify, and delete these resources.

title: Create custom resources

text:
Use `kubectl apply` with YAML manifests to create custom resources:

[code example]

title: View custom resources

text:
Use these commands to list and inspect existing custom resources:

[code example]

title: Modify custom resources

text:
Edit the YAML manifest and reapply to update custom resources:

[code example]

title: YAML examples

text:
Find complete YAML examples for common deployment scenarios:

- [YAML examples]() - Ready-to-use YAML configurations for different deployment types

title: Example categories

role: example

text:
- [Basic deployment]() - Essential YAML files for simple Redis Enterprise deployment
- [Rack awareness]() - YAML examples for rack-aware deployments across availability zones
- [Active-Active]() - YAML examples for Active-Active databases across multiple clusters
- [Multi-namespace]() - YAML examples for deploying across multiple namespaces

title: API reference

text: Review complete API specifications for all Redis Enterprise custom resources:

title: Core resources

text:
- [Redis Enterprise cluster API (REC)]() - Manage Redis Enterprise clusters
- [Redis Enterprise database API (REDB)]() - Manage Redis databases

title: Active-Active resources

text:
- [Active-Active database API (REAADB)]() - Manage Active-Active databases
- [Remote cluster API (RERC)]() - Configure remote cluster connections

title: Compatibility

role: compatibility

text:
Check supported Kubernetes distributions and versions:

- [Supported Kubernetes distributions]() - Compatible Kubernetes platforms and versions

title: Best practices

text:
Follow these best practices when working with custom resources:

- **Use version control**: Store your YAML manifests in version control systems
- **Validate before applying**: Use `kubectl apply --dry-run=client` to validate changes
- **Monitor resource status**: Check resource status after you apply changes
- **Follow naming conventions**: Use consistent naming for easier management
- **Document configurations**: Add annotations and labels to describe resource purpose

code:
kubectl apply -f my-redis-cluster.yaml
kubectl apply -f my-redis-database.yaml

section_id: create-custom-resources

code:
# List Redis Enterprise clusters
kubectl get rec

# List Redis Enterprise databases
kubectl get redb

# List Active-Active databases
kubectl get reaadb

# List remote clusters
kubectl get rerc

# Get detailed information about a specific resource
kubectl describe rec my-cluster
kubectl describe redb my-database

section_id: view-custom-resources

code:
# Edit and apply updated manifest
kubectl apply -f updated-redis-cluster.yaml

# Or edit directly (not recommended for production)
kubectl edit rec my-cluster
kubectl edit redb my-database

section_id: modify-custom-resources


title: Supported Kubernetes distributions

title: Overview

text:
We thoroughly test each release of Redis Enterprise for Kubernetes against a set of Kubernetes distributions. The table below lists Redis Enterprise for Kubernetes versions and the Kubernetes distributions they support.

✅ Supported – This distribution is supported for this version of Redis Enterprise Software for Kubernetes.

:warning: Deprecated – This distribution is still supported for this version of Redis Enterprise Software for Kubernetes, but support will be removed in a future release.

❌ End of life – Support for this distribution ended.

Any distribution not listed below is not supported for production workloads.

Each platform is tested with its default configuration, including storage, network, security, and container runtime components.

title: Community Kubernetes

text:
For details on this platform, see the Kubernetes [documentation](https://kubernetes.io/docs/home/supported-doc-versions/).

| Redis operator | **<nobr>8.0.10-21</nobr>** | **<nobr>8.0.6-6</nobr>** | **<nobr>8.0.2-2</nobr>** | **<nobr>7.22.2-21</nobr>** | **<nobr>7.22.0-15</nobr>** | **<nobr>7.22.0-7</nobr>** | **<nobr>7.8.6-1</nobr>** | **<nobr>7.8.4-9</nobr>** | **<nobr>7.8.4-8</nobr>** | **<nobr>7.8.2-6</nobr>** | **<nobr>7.4.6-2</nobr>** | **<nobr>7.4.2-12</nobr>** | **<nobr>7.4.2-2</nobr>** | **<nobr>7.2.4-12</nobr>** | **<nobr>7.2.4-7</nobr>** | **<nobr>7.2.4-2</nobr>** | **<nobr>6.4.2-8</nobr>** | **<nobr>6.4.2-6</nobr>** | **<nobr>6.4.2-5</nobr>** | **<nobr>6.4.2-4</nobr>** | **<nobr>6.2.18-41</nobr>** | **<nobr>6.2.18-3</nobr>** | **<nobr>6.2.12-1</nobr>** | **<nobr>**<nobr>6.2.10-4</nobr>**5</nobr>** | **<nobr>6.2.10-34</nobr>** | **<nobr>6.2.10-4</nobr>** | **<nobr>6.2.8-15</nobr>** | **<nobr>6.2.8-11</nobr>** | **<nobr>6.2.8-2</nobr>** | **<nobr>6.2.4-1</nobr>** |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|  | Jan 2026 | December 2025 | October 2025 | October 2025 | July 2025 | April 2025 | March 2025 | March 2025 | Feb 2025 | Nov 2024 | July 2024 | May 2024 | March 2024 | Dec 2023 | Oct 2023 | Aug 2023 | July 2023 | June 2023 | April 2023 | March 2023 | Jan 2023 | Nov 2022 | Sept 2022 | July 2022 | May 2022 | March 2022 | Jan 2022 | Jan 2022 | Nov 2021 | Sept 2021 |
| **Community K8s** |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.35 | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.34 | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.33 | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.32 | :warning: | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.31 |  | ❌ | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.30 |  |  | ❌ | :warning: | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.29 |  |  |  |  |  | ❌ | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.28 |  |  |  |  |  | ❌ | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.27 |  |  |  |  |  |  |  | ❌ | ❌ | ❌ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.26 |  |  |  |  |  |  |  |  |  |  | :warning: | :warning: | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |
| 1.25 |  |  |  |  |  |  |  |  |  |  |  |  | ❌ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |
| 1.24 |  |  |  |  |  |  |  |  |  |  |  |  | ❌ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |
| 1.23 |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  | ❌ | :warning: | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |
| 1.22 |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  | ❌ | :warning: | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |
| 1.21 |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  | ❌ | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
| 1.20 |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  | ❌ | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ |
| 1.19 |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  | ❌ | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ |
| 1.18 |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  | ✅ | ✅ | ✅ | ✅ | ✅ |
| 1.17 |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  | ❌ | :warning: |
| 1.16 |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  | ❌ | :warning: |

title: OpenShift Container Platform

text:
For details on this platform, see the [OpenShift documentation](https://docs.openshift.com/container-platform/4.13/welcome/index.html).

| Redis operator | **<nobr>8.0.10-21</nobr>** | **<nobr>8.0.6-6</nobr>** | **<nobr>8.0.2-2</nobr>** | **<nobr>7.22.2-21</nobr>** | **<nobr>7.22.0-15</nobr>** | **<nobr>7.22.0-7</nobr>** | **<nobr>7.8.6-1</nobr>** | **<nobr>7.8.4-9</nobr>** | **<nobr>7.8.4-8</nobr>** | **<nobr>7.8.2-6</nobr>** | **<nobr>7.4.6-2</nobr>** | **<nobr>7.4.2-12</nobr>** | **<nobr>7.4.2-2</nobr>** | **<nobr>7.2.4-12</nobr>** | **<nobr>7.2.4-7</nobr>** | **<nobr>7.2.4-2</nobr>** | **<nobr>6.4.2-8</nobr>** | **<nobr>6.4.2-6</nobr>** | **<nobr>6.4.2-5</nobr>** | **<nobr>6.4.2-4</nobr>** | **<nobr>6.2.18-41</nobr>** | **<nobr>6.2.18-3</nobr>** | **<nobr>6.2.12-1</nobr>** | **<nobr>6.2.10-45</nobr>** | **<nobr>6.2.10-34</nobr>** | **<nobr>6.2.10-4</nobr>** | **<nobr>6.2.8-15</nobr>** | **<nobr>6.2.8-11</nobr>** | **<nobr>6.2.8-2</nobr>** | **<nobr>6.2.4-1</nobr>** |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|  | Jan 2026 | December 2025 | October 2025 | October 2025 | July 2025 | April 2025 | March 2025 | March 2025 | Feb 2025 | Nov 2024 | July 2024 | May 2024 | March 2024 | Dec 2023 | Oct 2023 | Aug 2023 | July 2023 | June 2023 | April 2023 | March 2023 | Jan 2023 | Nov 2022 | Sept 2022 | July 2022 | May 2022 | March 2022 | Jan 2022 | Jan 2022 | Nov 2021 | Sept 2021 |
| **OpenShift** |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 4.20 | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 4.19 | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 4.18 | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 4.17 | :warning: | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 4.16 |  | ❌ | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 4.15 |  |  | ❌ | :warning: | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 4.14 |  |  |  |  |  | ❌ | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 4.13 |  |  |  |  |  | ❌ | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 4.12 |  |  |  |  |  |  | ❌ | ✅ | ✅ | ✅ | ✅ | ✅ | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |
| 4.11 |  |  |  |  |  |  |  |  |  |  | ❌ | :warning: | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |
| 4.10 |  |  |  |  |  |  |  |  |  |  |  |  |  | ❌ | :warning: | :warning: | :warning: | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |
| 4.9 |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  | ❌ | :warning: | :warning: | :warning: | :warning: | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |
| 4.8 |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  | ❌ | :warning: | :warning: | :warning: | :warning: | :warning: | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
| 4.7 |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  | :warning: | :warning: | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ |
| 4.6 |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ |
| 4.5 |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  | ✅ | ✅ | ✅ | ✅ | ✅ |
| 3.11 |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  | ❌ | :warning: | :warning: | :warning: | :warning: | :warning: |

title: Amazon Elastic Kubernetes Service (EKS)

text:
For details on this platform, see the [EKS documentation](https://docs.aws.amazon.com/eks/?icmpid=docs_homepage_containers).

| Redis operator | **<nobr>8.0.10-21</nobr>** | **<nobr>8.0.6-6</nobr>** | **<nobr>8.0.2-2</nobr>** | **<nobr>7.22.2-21</nobr>** | **<nobr>7.22.0-15</nobr>** | **<nobr>7.22.0-7</nobr>** | **<nobr>7.8.6-1</nobr>** | **<nobr>7.8.4-9</nobr>** | **<nobr>7.8.4-8</nobr>** | **<nobr>7.8.2-6</nobr>** | **<nobr>7.4.6-2</nobr>** | **<nobr>7.4.2-12</nobr>** | **<nobr>7.4.2-2</nobr>** | **<nobr>7.2.4-12</nobr>** | **<nobr>7.2.4-7</nobr>** | **<nobr>7.2.4-2</nobr>** | **<nobr>6.4.2-8</nobr>** | **<nobr>6.4.2-6</nobr>** | **<nobr>6.4.2-5</nobr>** | **<nobr>6.4.2-4</nobr>** | **<nobr>6.2.18-41</nobr>** | **<nobr>6.2.18-3</nobr>** | **<nobr>6.2.12-1</nobr>** | **<nobr>6.2.10-45</nobr>** | **<nobr>6.2.10-34</nobr>** | **<nobr>6.2.10-4</nobr>** | **<nobr>6.2.8-15</nobr>** | **<nobr>6.2.8-11</nobr>** | **<nobr>6.2.8-2</nobr>** | **<nobr>6.2.4-1</nobr>** |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|  | Jan 2026 | December 2025 | October 2025 | October 2025 | July 2025 | April 2025 | March 2025 | March 2025 | Feb 2025 | Nov 2024 | July 2024 | May 2024 | March 2024 | Dec 2023 | Oct 2023 | Aug 2023 | July 2023 | June 2023 | April 2023 | March 2023 | Jan 2023 | Nov 2022 | Sept 2022 | July 2022 | May 2022 | March 2022 | Jan 2022 | Jan 2022 | Nov 2021 | Sept 2021 |
| **Amazon EKS** |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.34 | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.33 | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.32 | :warning: | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.31 |  | ❌ | :warning: | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.30 |  |  | ❌ | :warning: | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.29 |  |  |  |  |  | ❌ | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.28 |  |  |  |  |  |  | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.27 |  |  |  |  |  |  | ❌ | :warning: | :warning: | :warning: | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.26 |  |  |  |  |  |  |  | ❌ | ❌ | ❌ | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.25 |  |  |  |  |  |  |  |  |  |  | ❌ | :warning: | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.24 |  |  |  |  |  |  |  |  |  |  |  |  | ❌ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |
| 1.23 |  |  |  |  |  |  |  |  |  |  |  |  | ❌ | :warning: | :warning: | :warning: | :warning: | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |
| 1.22 |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  | ❌ | :warning: | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |
| 1.21 |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  | ❌ | :warning: | :warning: | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
| 1.20 |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  | ❌ | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
| 1.19 |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  | ❌ | :warning: | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ |
| 1.18 |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  | ❌ | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ |

title: Azure Kubernetes Service (AKS)

text:
For details on this platform, see the [AKS documentation](https://learn.microsoft.com/en-us/azure/aks/).

| Redis operator | **<nobr>8.0.10-21</nobr>** | **<nobr>8.0.6-6</nobr>** | **<nobr>8.0.2-2</nobr>** | **<nobr>7.22.2-21</nobr>** | **<nobr>7.22.0-15</nobr>** | **<nobr>7.22.0-7</nobr>** | **<nobr>7.8.6-1</nobr>** | **<nobr>7.8.4-9</nobr>** | **<nobr>7.8.4-8</nobr>** | **<nobr>7.8.2-6</nobr>** | **<nobr>7.4.6-2</nobr>** | **<nobr>7.4.2-12</nobr>** | **<nobr>7.4.2-2</nobr>** | **<nobr>7.2.4-12</nobr>** | **<nobr>7.2.4-7</nobr>** | **<nobr>7.2.4-2</nobr>** | **<nobr>6.4.2-8</nobr>** | **<nobr>6.4.2-6</nobr>** | **<nobr>6.4.2-5</nobr>** | **<nobr>6.4.2-4</nobr>** | **<nobr>6.2.18-41</nobr>** | **<nobr>6.2.18-3</nobr>** | **<nobr>6.2.12-1</nobr>** | **<nobr>6.2.10-45</nobr>** | **<nobr>6.2.10-34</nobr>** | **<nobr>6.2.10-4</nobr>** | **<nobr>6.2.8-15</nobr>** | **<nobr>6.2.8-11</nobr>** | **<nobr>6.2.8-2</nobr>** | **<nobr>6.2.4-1</nobr>** |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|  | Jan 2026 | December 2025 | October 2025 | October 2025 | July 2025 | April 2025 | March 2025 | March 2025 | Feb 2025 | Nov 2024 | July 2024 | May 2024 | March 2024 | Dec 2023 | Oct 2023 | Aug 2023 | July 2023 | June 2023 | April 2023 | March 2023 | Jan 2023 | Nov 2022 | Sept 2022 | July 2022 | May 2022 | March 2022 | Jan 2022 | Jan 2022 | Nov 2021 | Sept 2021 |
| **Azure AKS** |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.34 | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.33 | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.32 | :warning: | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.31 |  | ❌ | :warning: | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.30 |  |  | ❌ | :warning: | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.29 |  |  |  |  |  | ❌ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.28 |  |  |  |  |  |  | ❌ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.27 |  |  |  |  |  |  | ❌ | :warning: | :warning: | :warning: | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.26 |  |  |  |  |  |  |  |  |  |  | ❌ | :warning: | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.25 |  |  |  |  |  |  |  |  |  |  |  |  | ❌ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |
| 1.24 |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  | ❌ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |
| 1.23 |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  | ❌ | :warning: | :warning: | :warning: | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |
| 1.22 |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |
| 1.21 |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  | ❌ | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ |  |
| 1.20 |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  | ❌ | :warning: | ✅ | ✅ | ✅ | ✅ |  |
| 1.19 |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  | ❌ | :warning: |  | ✅ | ✅ | ✅ | ✅ |
| 1.18 |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  | ✅ |

title: Google Kubernetes Engine (GKE)

text:
For details on this platform, see the [GKE documentation](https://cloud.google.com/kubernetes-engine/docs).

| Redis operator | **<nobr>8.0.10-21</nobr>** | **<nobr>8.0.6-6</nobr>** | **<nobr>8.0.2-2</nobr>** | **<nobr>7.22.2-21</nobr>** | **<nobr>7.22.0-15</nobr>** | **<nobr>7.22.0-7</nobr>** | **<nobr>7.8.6-1</nobr>** | **<nobr>7.8.4-9</nobr>** | **<nobr>7.8.4-8</nobr>** | **<nobr>7.8.2-6</nobr>** | **<nobr>7.4.6-2</nobr>** | **<nobr>7.4.2-12</nobr>** | **<nobr>7.4.2-2</nobr>** | **<nobr>7.2.4-12</nobr>** | **<nobr>7.2.4-7</nobr>** | **<nobr>7.2.4-2</nobr>** | **<nobr>6.4.2-8</nobr>** | **<nobr>6.4.2-6</nobr>** | **<nobr>6.4.2-5</nobr>** | **<nobr>6.4.2-4</nobr>** | **<nobr>6.2.18-41</nobr>** | **<nobr>6.2.18-3</nobr>** | **<nobr>6.2.12-1</nobr>** | **<nobr>6.2.10-45</nobr>** | **<nobr>6.2.10-34</nobr>** | **<nobr>6.2.10-4</nobr>** | **<nobr>6.2.8-15</nobr>** | **<nobr>6.2.8-11</nobr>** | **<nobr>6.2.8-2</nobr>** | **<nobr>6.2.4-1</nobr>** |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|  | Jan 2026 | December 2025 | October 2025 | October 2025 | July 2025 | April 2025 | March 2025 | March 2025 | Feb 2025 | Nov 2024 | July 2024 | May 2024 | March 2024 | Dec 2023 | Oct 2023 | Aug 2023 | July 2023 | June 2023 | April 2023 | March 2023 | Jan 2023 | Nov 2022 | Sept 2022 | July 2022 | May 2022 | March 2022 | Jan 2022 | Jan 2022 | Nov 2021 | Sept 2021 |
| **Google GKE** |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.35 | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.34 | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.33 | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.32 | :warning: | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.31 |  | ❌ | :warning: | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.30 |  |  | ❌ | :warning: | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.29 |  |  |  |  |  | ❌ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.28 |  |  |  |  |  |  | ❌ | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.27 |  |  |  |  |  |  |  | ❌ | ❌ | ❌ | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.26 |  |  |  |  |  |  |  |  |  |  | ❌ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.25 |  |  |  |  |  |  |  |  |  |  | ❌ | :warning: | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |
| 1.24 |  |  |  |  |  |  |  |  |  |  |  |  | ❌ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |
| 1.23 |  |  |  |  |  |  |  |  |  |  |  |  |  | ❌ | :warning: | :warning: | :warning: | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |
| 1.22 |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  | ❌ | :warning: | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |
| 1.21 |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  | ❌ | :warning: | :warning: | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
| 1.20 |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  | ❌ | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
| 1.19 |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  | ❌ | :warning: | ✅ |  | ✅ | ✅ | ✅ | ✅ |
| 1.18 |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  | ✅ |

title: Rancher

text:
For details on this platform, see the [Rancher documentation](https://ranchermanager.docs.rancher.com/).

| Redis operator | **<nobr>8.0.10-21</nobr>** | **<nobr>8.0.6-6</nobr>** | **<nobr>8.0.2-2</nobr>** | **<nobr>7.22.2-21</nobr>** | **<nobr>7.22.0-15</nobr>** | **<nobr>7.22.0-7</nobr>** | **<nobr>7.8.6-1</nobr>** | **<nobr>7.8.4-9</nobr>** | **<nobr>7.8.4-8</nobr>** | **<nobr>7.8.2-6</nobr>** | **<nobr>7.4.6-2</nobr>** | **<nobr>7.4.2-12</nobr>** | **<nobr>7.4.2-2</nobr>** | **<nobr>7.2.4-12</nobr>** | **<nobr>7.2.4-7</nobr>** | **<nobr>7.2.4-2</nobr>** | **<nobr>6.4.2-8</nobr>** | **<nobr>6.4.2-6</nobr>** | **<nobr>6.4.2-5</nobr>** | **<nobr>6.4.2-4</nobr>** | **<nobr>6.2.18-41</nobr>** | **<nobr>6.2.18-3</nobr>** | **<nobr>6.2.12-1</nobr>** | **<nobr>6.2.10-45</nobr>** | **<nobr>6.2.10-34</nobr>** | **<nobr>6.2.10-4</nobr>** | **<nobr>6.2.8-15</nobr>** | **<nobr>6.2.8-11</nobr>** | **<nobr>6.2.8-2</nobr>** | **<nobr>6.2.4-1</nobr>** |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|  | Jan 2026 | December 2025 | October 2025 | October 2025 | July 2025 | April 2025 | March 2025 | March 2025 | Feb 2025 | Nov 2024 | July 2024 | May 2024 | March 2024 | Dec 2023 | Oct 2023 | Aug 2023 | July 2023 | June 2023 | April 2023 | March 2023 | Jan 2023 | Nov 2022 | Sept 2022 | July 2022 | May 2022 | March 2022 | Jan 2022 | Jan 2022 | Nov 2021 | Sept 2021 |
| **RKE2** |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.34 | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.33 | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.32 | :warning: | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.31 | ❌ | :warning: | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.30 |  | ❌ | :warning: | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.29 |  | ❌ | :warning: | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.28 |  |  | ❌ | :warning: | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.27 |  |  |  |  |  | ❌ | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.26 |  |  |  |  |  |  | ❌ | :warning: | :warning: | :warning: | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.25 |  |  |  |  |  |  |  |  |  |  | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.24 |  |  |  |  |  |  |  |  |  |  |  | ❌ | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |
| 1.23 |  |  |  |  |  |  |  |  |  |  |  |  | ❌ | :warning: | :warning: | :warning: | :warning: | :warning: | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |
| 1.24 |  |  |  |  |  |  |  |  |  |  |  |  |  | ❌ | :warning: | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |
| 1.23 |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  | ❌ | :warning: | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |
| **Rancher** |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.22 |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  | ❌ | :warning: | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |
| 1.21 |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  | ❌ | :warning: | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |
| 1.20 |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  | ❌ | :warning: | ✅ |  |  |  |  |  |
| 1.19 |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  | ❌ | :warning: | ✅ |  |  |  |  |  |
| 1.18 |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  | :warning: |  |  |  |  |  |
| 1.20 |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  | ❌ | :warning: | ✅ | ✅ | ✅ | ✅ |
| 1.19 |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  | ❌ | :warning: | ✅ | ✅ | ✅ | ✅ |
| 1.18 |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  | ❌ | :warning: | ✅ | ✅ | ✅ | ✅ |
| 1.17 |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  | ❌ | :warning: | ✅ | ✅ | ✅ | ✅ |
| 1.18 |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  | :warning: | ✅ |
| 1.17 |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  | :warning: | ✅ |

title: VMware Tanzu Kubernetes Grid Integrated Edition (TKGI)

text:
For details on this platform, see the [TKGI documentation](https://docs.vmware.com/en/VMware-Tanzu-Kubernetes-Grid-Integrated-Edition/index.html).

| Redis operator | **<nobr>8.0.10-21</nobr>** | **<nobr>8.0.6-6</nobr>** | **<nobr>8.0.2-2</nobr>** | **<nobr>7.22.2-21</nobr>** | **<nobr>7.22.0-15</nobr>** | **<nobr>7.22.0-7</nobr>** | **<nobr>7.8.6-1</nobr>** | **<nobr>7.8.4-9</nobr>** | **<nobr>7.8.4-8</nobr>** | **<nobr>7.8.2-6</nobr>** | **<nobr>7.4.6-2</nobr>** | **<nobr>7.4.2-12</nobr>** | **<nobr>7.4.2-2</nobr>** | **<nobr>7.2.4-12</nobr>** | **<nobr>7.2.4-7</nobr>** | **<nobr>7.2.4-2</nobr>** | **<nobr>6.4.2-8</nobr>** | **<nobr>6.4.2-6</nobr>** | **<nobr>6.4.2-5</nobr>** | **<nobr>6.4.2-4</nobr>** | **<nobr>6.2.18-41</nobr>** | **<nobr>6.2.18-3</nobr>** | **<nobr>6.2.12-1</nobr>** | **<nobr>6.2.10-45</nobr>** | **<nobr>6.2.10-34</nobr>** | **<nobr>6.2.10-4</nobr>** | **<nobr>6.2.8-15</nobr>** | **<nobr>6.2.8-11</nobr>** | **<nobr>6.2.8-2</nobr>** | **<nobr>6.2.4-1</nobr>** |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|  | Jan 2026 | December 2025 | October 2025 | October 2025 | July 2025 | April 2025 | March 2025 | March 2025 | Feb 2025 | Nov 2024 | July 2024 | May 2024 | March 2024 | Dec 2023 | Oct 2023 | Aug 2023 | July 2023 | June 2023 | April 2023 | March 2023 | Jan 2023 | Nov 2022 | Sept 2022 | July 2022 | May 2022 | March 2022 | Jan 2022 | Jan 2022 | Nov 2021 | Sept 2021 |
| **VMware TKGI** |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.23 | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.22 | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.21 | :warning: | :warning: | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.20 |  | ❌ | :warning: | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.19 |  |  | ❌ | :warning: | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.18 |  |  |  |  | ❌ | :warning: | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.17 |  |  |  |  | ❌ | :warning: | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.16 |  |  |  |  |  |  |  | ❌ | ❌ | ❌ | :warning: | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.15 |  |  |  |  |  |  |  |  |  |  |  |  | ❌ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |
| 1.14 |  |  |  |  |  |  |  |  |  |  |  |  |  | ❌ | :warning: | :warning: | :warning: | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |
| 1.13 |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  | ❌ | :warning: | :warning: | :warning: | :warning: | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |
| 1.12 |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  | ❌ | :warning: | ✅ | ✅ |  |  |  |  |  |
| 1.11 |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  | ❌ | :warning: | :warning: | ✅ | ✅ |  |  |  |  |
| 1.10 |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  | ❌ | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
| 1.09 |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.08 |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  | ❌ | :warning: |
| 1.07 |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  | ❌ | :warning: |

title: VMware vSphere Kubernetes Service (VKS)

text:
For details on this platform, see the [VKS documentation](https://techdocs.broadcom.com/us/en/vmware-cis/vcf/vsphere-supervisor-services-and-standalone-components/latest/release-notes/vmware-tanzu-kubernetes-grid-service-release-notes.html).

| Redis operator | **<nobr>8.0.10-21</nobr>** | **<nobr>8.0.6-6</nobr>** | **<nobr>8.0.2-2</nobr>** |
|---|---|---|---|
|  | Jan 2026 | December 2025 | October 2025 |
| **VMware VKS** |  |  |  |
| 1.32 | ✅ | ✅ | ✅ |

title: VMware Tanzu Kubernetes Grid (TKG)

text:
For details on this platform, see the [TKG documentation](https://docs.vmware.com/en/VMware-Tanzu-Kubernetes-Grid/index.html).

|  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Redis operator | **<nobr>8.0.2-2</nobr>** | **<nobr>7.22.2-21</nobr>** | **<nobr>7.22.0-15</nobr>** | **<nobr>7.22.0-7</nobr>** | **<nobr>7.8.6-1</nobr>** | **<nobr>7.8.4-9</nobr>** | **<nobr>7.8.4-8</nobr>** | **<nobr>7.8.2-6</nobr>** | **<nobr>7.4.6-2</nobr>** | **<nobr>7.4.2-12</nobr>** | **<nobr>7.4.2-2</nobr>** | **<nobr>7.2.4-12</nobr>** | **<nobr>7.2.4-7</nobr>** | **<nobr>7.2.4-2</nobr>** | **<nobr>6.4.2-8</nobr>** | **<nobr>6.4.2-6</nobr>** | **<nobr>6.4.2-5</nobr>** | **<nobr>6.4.2-4</nobr>** | **<nobr>6.2.18-41</nobr>** |
|  | October 2025 | October 2025 | July 2025 | April 2025 | March 2025 | March 2025 | Feb 2025 | Nov 2024 | July 2024 | May 2024 | March 2024 | Dec 2023 | Oct 2023 | Aug 2023 | July 2023 | June 2023 | April 2023 | March 2023 | Jan 2023 |
| **VMWare TKG 2.4** |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.27 |  |  | ❌ | :warning: | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |
| 1.26 |  |  | ❌ | :warning: | :warning: | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |  |
| 1.25 |  |  |  |  |  |  |  |  |  | ✅ | ✅ |  |  |  |  |  |  |  |  |
| **VMware TKG 2.3** |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.26 |  |  |  |  | ❌ | :warning: | :warning: | :warning: | :warning: | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |
| 1.25 |  |  |  |  |  |  |  |  | ❌ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |
| 1.24 |  |  |  |  |  |  |  |  | ❌ | ✅ | ✅ | ✅ |  |  |  |  |  |  |  |
| **VMware TKG 2.2** |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.25 |  |  |  |  |  |  |  |  | ❌ | :warning: | :warning: | ✅ | ✅ | ✅ |  |  |  |  |  |
| 1.24 |  |  |  |  |  |  |  |  | ❌ | :warning: | :warning: | ✅ | ✅ | ✅ |  |  |  |  |  |
| 1.23 |  |  |  |  |  |  |  |  |  |  | ❌ | ✅ | ✅ | ✅ |  |  |  |  |  |
| **VMware TKG 2.1** |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.24 |  |  |  |  |  |  |  |  |  |  | ❌ | ✅ | ✅ | ✅ |  |  |  |  |  |
| 1.23 |  |  |  |  |  |  |  |  |  |  | ❌ | :warning: | :warning: | :warning: |  |  |  |  |  |
| 1.22 |  |  |  |  |  |  |  |  |  |  |  | ❌ | :warning: | :warning: |  |  |  |  |  |
| **VMware TKG 1.6** |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 1.24 |  |  |  |  |  |  |  |  |  |  |  |  | :warning: | :warning: |  |  |  |  |  |
| 1.23 |  |  |  |  |  |  |  |  |  |  |  |  |  | ❌ | :warning: | :warning: | ✅ | ✅ | ✅ |
| 1.22 |  |  |  |  |  |  |  |  |  |  |  |  |  | ❌ | :warning: | :warning: | ✅ | ✅ | ✅ |


title: Active-Active examples

summary: YAML examples for Active-Active Redis Enterprise databases across multiple Kubernetes clusters.

title: Overview

text:
This page provides YAML examples for deploying Active-Active Redis Enterprise databases across multiple Kubernetes clusters. Active-Active databases provide multi-master replication with conflict resolution, enabling global distribution and local read/write access.

For complete deployment instructions, see [Active-Active databases]().

title: Applying the configuration

text: To deploy Active-Active databases using these YAML files, follow [Create Active-Active database (REAADB)](), which provides detailed instructions for preparing clusters, creating RERC resources, and deploying REAADB configurations.

title: Namespace examples

text:
A namespace is an abstraction used by Kubernetes to support multiple virtual clusters on the same physical cluster.

`ns-illinois.yaml` is used in [Create Active-Active database]().

`ns-virginia.yaml` is used in [Create Active-Active database]().

title: REC examples

text:
A Redis Enterprise cluster is a collection of Redis Enterprise nodes that pools system resources across nodes and supports multi-tenant database instances.

`rec-chicago.yaml` is used in [Create Active-Active database]() and [Create RERC]().

`rec-arlington.yaml` is used in [Create Active-Active database]() and [Create RERC]().

title: RERC examples

text:
RedisEnterpriseRemoteCluster represents a remote participating cluster.

`rerc-ohare.yaml` is used in the [Create RERC]() section.

`rerc-raegan.yaml` is used in the [Create RERC]() section.

title: RERC configuration

text:
- [metadata.name](): Unique name for this remote cluster reference
- [spec.recName](): Name of the remote REC
- [spec.recNamespace](): Namespace of the remote REC
- [spec.apiFqdnUrl](): API endpoint URL for the remote cluster
- [spec.dbFqdnSuffix](): Database hostname suffix for the remote cluster
- [spec.secretName](): Secret containing authentication credentials

Edit the values in the downloaded YAML file for your specific setup, updating the remote cluster details, API endpoints, and secret names to match your actual environment.

title: Active-Active database examples

text:
Active-Active databases are geo-distributed databases that span multiple Redis Enterprise clusters and use multi-primary replication and conflict-free replicated data types (CRDTs).

`reaadb-boeing.yaml` is used in the [Create Active-Active database]() section.

title: REAADB configuration

text:
- [metadata.name](): Active-Active database name
- [spec.participatingClusters](): List of RERC names that participate in this database
- [spec.globalConfigurations](): Database settings applied to all participating clusters

Edit the downloaded YAML file to add global database settings such as memory allocation, shard count, replication settings, database secrets, Redis modules, and database-specific Redis configuration.

title: Related documentation

role: related

text:
- [Active-Active databases (index)]()
- [Prepare participating clusters]()
- [Create Active-Active database (REAADB)]()
- [Edit global configuration]()
- [Sync global database secret]()
- [RERC API reference]()
- [REAADB API reference]()
- [Networking configuration]()


title: Basic deployment examples

summary: YAML examples for basic Redis Enterprise deployment including RBAC, cluster, and database configurations.

title: Overview

text:
This page provides complete YAML examples for a basic Redis Enterprise deployment on Kubernetes. These examples include all the essential components you need to deploy a Redis Enterprise cluster and create a database.

For complete deployment instructions, see [Deploy on Kubernetes]().

title: Service account

text:
The service account provides an identity for the Redis Enterprise operator.

Service account configuration:
- `name`: The service account name used by the operator
- `labels`: Standard labels for Redis Enterprise resources

title: Role

text:
The Role defines the permissions needed by the Redis Enterprise operator within the namespace.

Role configuration:
- `name`: Must match the role name referenced in the role binding
- `rules`: Comprehensive permissions for managing Redis Enterprise resources
- `apiGroups`: Includes core Kubernetes APIs and Redis Enterprise custom resources

Key permissions:
- `app.redislabs.com`: Full access to Redis Enterprise custom resources
- `secrets`: Manage TLS certificates and database credentials
- `services`: Create and manage service endpoints
- `pods`: Monitor and manage Redis Enterprise pods
- `persistentvolumeclaims`: Manage persistent storage

title: Role binding

text:
The RoleBinding connects the service account to the role, granting the necessary permissions.

Role binding configuration:
- `subjects.name`: Must match the service account name
- `roleRef.name`: Must match the role name
- `namespace`: Apply in the same namespace as other resources

title: Redis Enterprise cluster

text:
The RedisEnterpriseCluster (REC) custom resource defines the cluster specification.

Cluster configuration:
- `metadata.name`: Cluster name (cannot be changed after creation)
- `spec.nodes`: Number of Redis Enterprise nodes (minimum 3)
- `persistentSpec.volumeSize`: Storage size per node
- `redisEnterpriseNodeResources`: CPU and memory allocation per node

Edit the values in the downloaded YAML file based on your requirements, such as increasing the number of nodes, adjusting storage size, or modifying resource allocation.

title: Redis Enterprise database

text:
The RedisEnterpriseDatabase (REDB) custom resource defines the database specification.

Database configuration:
- `metadata.name`: Database name
- `spec.memorySize`: Memory allocation for the database
- `spec.shardCount`: Number of shards (affects performance and scalability)
- `spec.replication`: Enable/disable database replication

Edit the values in the downloaded YAML file based on your requirements, such as increasing memory for larger datasets, adding more shards for better performance, enabling replication for high availability, or adding Redis modules.

title: Apply the configuration

text: To deploy these YAML files, follow [Deploy on Kubernetes](), which provides step-by-step instructions for creating namespaces, deploying the operator, and applying these configuration files.

title: Related documentation

text:
- [Deploy on Kubernetes]()
- [REC API reference]()
- [REDB API reference]()


title: YAML examples

title: Basic deployment examples

summary: YAML examples for rack-aware Redis Enterprise deployments that distribute nodes across availability zones.

title: Rack awareness examples

title: Active-Active examples

summary: YAML examples for deploying Redis Enterprise across multiple Kubernetes namespaces.

title: Multi-namespace examples

summary: YAML examples for configuring RBAC permissions for the Redis Enterprise log collector tool in `restricted` and `all` modes.

title: Log collector RBAC examples

title: Overview

text: This section provides complete YAML examples that cover common Redis Enterprise for Kubernetes deployment scenarios. Each example includes the necessary configuration files and step-by-step instructions for editing and applying them.

title: How to use these examples

title: Download and customize

text:
1. Copy the YAML content from the examples below
2. Save each YAML block to a separate file with a descriptive name
3. Edit the configuration values to match your environment
4. Apply the files in the correct order using `kubectl apply`

title: Configuration storage

role: configuration

text:
Redis Enterprise for Kubernetes stores configuration in several places:

- Custom resources: Cluster and database specifications are stored as Kubernetes custom resources (REC, REDB, REAADB, RERC)
- Secrets: Sensitive data like passwords and certificates are stored in Kubernetes secrets
- ConfigMaps: Non-sensitive configuration data is stored in ConfigMaps
- RBAC resources: Permissions are defined through Roles, ClusterRoles, and their bindings

title: Applying YAML files

text:
Apply YAML files using `kubectl apply`:

[code example]

title: Monitoring deployment

text:
Check the status of your resources after applying:

[code example]

title: Example categories

text:
- [Basic deployment examples]() - Service account, RBAC, cluster, and database configurations
- [Rack awareness examples]() - Rack-aware cluster configuration and required RBAC
- [Active-Active examples]() - Multi-cluster Active-Active database setup
- [Multi-namespace examples]() - Cross-namespace operator and cluster configurations
- [Log collector RBAC examples]() - RBAC permissions for log collection in restricted and all modes

title: Best practices

text:
- Validate configuration: Use `kubectl apply --dry-run=client` to validate YAML syntax and object schemas before applying
- Version control: Store your customized YAML files in version control
- Resource naming: Use consistent, descriptive names for all resources

title: Related documentation

text:
- [Reference]() - Complete API specifications for all custom resources
- [Deploy Redis Enterprise Software for Kubernetes]() - Step-by-step deployment instructions
- [Manage databases in multiple namespaces]() - Detailed multi-namespace setup instructions
- [Active-Active databases]() - Active-Active configuration and management

code:
# Apply a single file
kubectl apply -f my-config.yaml

# Apply multiple files
kubectl apply -f rbac/ -f cluster/ -f database/

# Validate files without applying
kubectl apply --dry-run=client -f my-config.yaml

section_id: applying-yaml-files

code:
# Check operator deployment
kubectl get deployment redis-enterprise-operator

# Check cluster status
kubectl get rec
kubectl describe rec <cluster-name>

# Check database status
kubectl get redb
kubectl describe redb <database-name>

# View events for troubleshooting
kubectl get events --sort-by=.metadata.creationTimestamp

section_id: monitoring-deployment


title: Log collector RBAC examples

title: Overview

text:
This page provides YAML examples for configuring RBAC permissions for the Redis Enterprise log collector tool. The log collector requires different permission levels depending on the collection mode you choose.

For complete log collection instructions, see [Collect logs]().

title: Prerequisites

text:
- Install the [Redis Enterprise operator]()
- Appropriate permissions to create RBAC resources in target namespaces
- Understanding of your deployment model (single namespace, multi-namespace, etc.)

title: Collection modes

text:
The log collector has two collection modes that require different RBAC permissions:

- **`restricted` mode** (recommended): Collects only Redis Enterprise resources with minimal security exposure. Default for versions 6.2.18-3+.
- **`all` mode**: Collects comprehensive cluster information including nodes, storage classes, and operator resources. Use when specifically requested by Redis Support.

title: `restricted` mode RBAC

text:
The `restricted` mode configuration provides minimal permissions for collecting Redis Enterprise resources only.

`restricted` mode configuration:

- `Role`: Namespace-scoped permissions for Redis Enterprise resources
- `ClusterRole`: Cluster-wide permissions for CRDs and basic cluster resources
- `rules`: Minimal permissions for Redis Enterprise diagnostics

Key permissions:

- `pods, pods/log, pods/exec`: Access to pod information and logs
- `app.redislabs.com/*`: All Redis Enterprise custom resources
- `persistentvolumes`: Storage information for troubleshooting

title: `all` mode RBAC

text:
The `all` mode configuration provides comprehensive permissions for collecting detailed cluster information.

`all` mode configuration:

- `Role`: Extended namespace permissions including operator resources
- `ClusterRole`: Additional cluster-wide permissions for nodes and storage
- `rules`: Comprehensive permissions for full cluster diagnostics

Additional permissions in `all` mode:

- `nodes`: Node information and status
- `storageclasses, volumeattachments`: Storage system details
- `operators.coreos.com/*`: OpenShift operator information
- `networking.istio.io/*`: Istio service mesh resources

title: Apply the configuration

title: Namespace requirements

text:
Create the Role and RoleBinding in every namespace where you need to collect logs:

- Single namespace: Apply to the namespace where Redis Enterprise runs
- Multi-namespace with single REC: Apply to the REC namespace plus each REDB namespace
- Multi-namespace with multiple RECs: Apply to each REC namespace

The ClusterRole and ClusterRoleBinding need to be created only once per cluster.

Edit the values in the downloaded YAML file for your specific setup, updating the namespace references and role binding subjects to match your environment.

title: Role binding configuration

text:
The RBAC configurations include both roles and role bindings. The role bindings must reference the user or service account that will execute the log collector:

- User subject: If running the log collector as a specific user, update the `subjects` section in the RoleBinding and ClusterRoleBinding to reference your username
- Service account: If using a service account, create or reference the appropriate service account in the role bindings

title: Manual deployment

text:
To apply the RBAC configurations manually:

[code example]

title: Usage

role: syntax

text:
After applying the RBAC configuration, run the log collector:

[code example]

title: Security considerations

role: security

title: Best practices

text:
- Use `restricted` mode unless you specifically need additional cluster information
- Limit namespace access to only where log collection is needed
- Handle collected data according to your organization's security policies

title: Secrets permission explanation

text:
The RBAC configurations request read access to secrets in the collected namespaces. **Secrets are not collected or included in the log package sent to Redis Support.** This permission is required because:

- The log collector uses Helm commands (`helm list`, `helm get all`) to gather Redis Enterprise Helm chart deployment information
- Helm stores its deployment metadata in Kubernetes secrets
- This metadata contains only deployment configuration (not sensitive data)

If your security policies prohibit secrets access, you can remove the secrets permission from the Role, but this will limit the log collector's ability to gather Helm deployment information.

title: Troubleshooting

role: errors

title: Permission errors

text:
- Verify that roles and bindings are applied correctly in the target namespaces
- Check that the ClusterRole is applied cluster-wide
- Ensure the service account has proper role bindings

title: Missing resources

text:
- Consider switching to `all` mode if additional cluster resources are needed
- Verify that custom resource definitions are installed
- Check that the operator has proper permissions

title: Next steps

text:
- [Collect logs guide]()
- [Basic deployment examples]()
- [Multi-namespace deployment]()

title: Related documentation

text:
- [Kubernetes RBAC documentation](https://kubernetes.io/docs/reference/access-authn-authz/rbac/)
- [Redis Enterprise troubleshooting]()
- [Operator deployment guide]()

code:
# Apply restricted mode RBAC
kubectl apply -f log-collector-restricted-rbac.yaml --namespace <namespace>

# Apply all mode RBAC
kubectl apply -f log-collector-all-rbac.yaml --namespace <namespace>

section_id: manual-deployment

code:
# Restricted mode (default for 6.2.18-3+)
python log_collector.py -m restricted -n <namespace>

# All mode
python log_collector.py -m all -n <namespace>

section_id: usage


title: Multi-namespace examples

title: Overview

text:
Multi-namespace deployment lets a single Redis Enterprise operator manage clusters and databases in different namespaces, providing better resource isolation and organization.

Multi-namespace deployment enables:
- Namespace isolation: Separate Redis Enterprise resources by team, environment, or application
- Centralized management: Single operator manages multiple namespaces
- Resource sharing: Efficient use of cluster resources across namespaces
- Flexible RBAC: Fine-grained permissions per namespace

This example shows:
- Operator namespace: `redis-enterprise-operator` (where the operator and REC run)
- Consumer namespaces: `app-production`, `app-staging` (where REDB resources are created)

For complete deployment instructions, see [Manage databases in multiple namespaces]().

title: Operator service account

text: Deploy these resources in the namespace where the Redis Enterprise operator runs.

title: Operator cluster role

text: Grant the operator cluster-wide permissions to manage resources across namespaces.

title: Operator cluster role binding

title: Consumer role

title: Consumer role binding

text:
Consumer namespace configuration:

- `subjects.name`: Must match the operator service account name
- `subjects.namespace`: Must be the operator namespace, not the consumer namespace
- `roleRef.name`: Must match the consumer role name

title: Next steps

text:
- [Configure networking across namespaces]()
- [Set up monitoring for multi-namespace deployment]()
- [Learn about resource management]()

title: Related documentation

text:
- [Manage databases in multiple namespaces]()
- [RBAC configuration]()
- [Kubernetes namespaces](https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/)


title: Rack awareness examples

title: Overview

text: This page provides YAML examples for deploying Redis Enterprise with [rack awareness](). Rack awareness distributes Redis Enterprise nodes and database shards across different availability zones or failure domains to improve high availability and fault tolerance.

title: Prerequisites

text:
- Label [Kubernetes nodes](https://kubernetes.io/docs/concepts/architecture/nodes/) with zone information
- Typically uses the standard label `topology.kubernetes.io/zone`
- Verify node labels: `kubectl get nodes -o custom-columns="name:metadata.name","rack\\zone:metadata.labels.topology\.kubernetes\.io/zone"`
- Install the [Redis Enterprise operator]()

For complete deployment instructions, see [Deploy on Kubernetes]().

title: Service account

text: The service account for rack-aware deployments is the same as [basic deployments]().

title: Cluster role

text:
Rack awareness requires additional permissions to read [node labels](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/) across the cluster.

Cluster role configuration:

- `name`: ClusterRole name for rack awareness permissions
- `rules`: Permissions to read nodes and their labels cluster-wide
- `resources`: Access to `nodes` resource for zone label discovery

Key permissions:

- `nodes`: Read access to discover node zone labels
- `get, list, watch`: Monitor node changes and zone assignments

title: Cluster role binding

text:
The [ClusterRoleBinding](https://kubernetes.io/docs/reference/access-authn-authz/rbac/#rolebinding-and-clusterrolebinding) grants cluster-wide permissions to the service account.

Cluster role binding configuration:

- `subjects.name`: Must match the service account name
- `subjects.namespace`: Namespace where the operator is deployed
- `roleRef.name`: Must match the cluster role name

title: Rack-aware Redis Enterprise cluster

text:
The rack-aware [REC configuration]() includes the `rackAwarenessNodeLabel` field.

Rack-aware cluster configuration:

- `metadata.name`: Cluster name (cannot be changed after creation)
- `spec.rackAwarenessNodeLabel`: Node label used for zone identification
- `spec.nodes`: Minimum 3 nodes, ideally distributed across zones

Edit the values in the downloaded YAML file based on your environment, such as increasing nodes for better zone distribution, using custom zone labels, adding resource specifications, or enabling persistent storage.

title: Common zone labels

text:
Different Kubernetes distributions use different zone labels:

- `Standard`: `topology.kubernetes.io/zone`
- `Legacy`: `failure-domain.beta.kubernetes.io/zone`
- `Custom`: Your organization's specific labeling scheme

Verify the correct label on your nodes:

[code example]

title: Redis Enterprise database

text:
Database configuration for rack-aware clusters is the same as [basic deployments]().

**Important**: For rack awareness to be effective, ensure your database has replication enabled. Rack awareness distributes primary and replica shards across zones, so databases without replication will not benefit from zone distribution.

title: Apply the configuration

text: To deploy rack-aware Redis Enterprise clusters, follow [Deploy on Kubernetes]() and ensure your Kubernetes nodes have proper zone labels. For detailed rack awareness configuration, see the [node selection recommendations]().

title: Troubleshooting

title: Nodes not distributed across zones

text:
- Verify node labels are correct
- Check that sufficient nodes exist in each zone
- Ensure the `rackAwarenessNodeLabel` matches actual node labels

title: Cluster role permissions denied

text:
- Verify the ClusterRole and ClusterRoleBinding are applied
- Check that the service account name matches in all resources

title: Database shards not distributed

text:
- Confirm the cluster has rack awareness enabled
- **Check that the database has replication enabled** - rack awareness distributes primary/replica pairs across zones
- Verify the database has multiple shards
- Ensure sufficient nodes exist across zones

title: Next steps

text:
- [Configure Active-Active databases]()
- [Set up multi-namespace deployment]()
- [Learn about database replication]()

title: Related documentation

text:
- [Node selection recommendations]()
- [REC API reference]()
- [REDB API reference]()
- [Kubernetes node affinity](https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/)
- [Redis Enterprise cluster architecture]()

section_id: common-zone-labels


title: 6.2.18 release notes

summary: Release notes for the 6.2.x releases of Redis Enterprise Software for Kubernetes.

summary: This is a maintenance release for 6.2.18 and includes support for Redis Enterprise 6.2.18-72.

title: Redis Enterprise for Kubernetes release notes 6.2.18-41 (Jan 2023)

summary: This is a maintenance release for 6.2.18 and includes bug fixes.

title: Redis Enterprise for Kubernetes release notes 6.2.18-41 (Dec 2022)

summary: Support added for additional distributions, as well as feature improvements and bug fixes.

title: Redis Enterprise for Kubernetes release notes 6.2.12-1 (Sept 2022)

title: Redis Enterprise for Kubernetes release notes 6.2.18-3 (Nov 2022)

summary: Support added for additional distributions as well as some feature improvements.

title: Redis Enterprise for Kubernetes release notes 6.2.10-45 (July 2022)

summary: Support for REBD specific upgrade policies, memcached type REDBs, and RHEL8 for OpenShift, as well as feature improvements and bug fixes.

title: Redis Enterprise for Kubernetes Release Notes 6.2.10-34 (May 2022)

summary: Added support for RS 6.2.10 as well as feature improvements and bug fixes.

title: Redis Enterprise for Kubernetes Release Notes 6.2.10-4 (March 2022)

summary: Maintenance release with bug fixes

title: Redis Enterprise for Kubernetes Release Notes 6.2.8-15 (January 2022)

summary: Support for Istio as ingress controller, K8s 1.22 (AKS, kOps, GKE), OpenShift 4.9

title: Redis Enterprise for Kubernetes Release Notes 6.2.8-11 (January 2022)

summary: Support for RS 6.2.8, certificate management, and Redis upgrade policy.

title: Redis Enterprise for Kubernetes Release Notes 6.2.8-2 (November 2021)

summary: Support for RS 6.2.4 and OpenShift 4.8. Support for K8s 1.19 (EKS and AKS), K8s 1.20 (Rancher, EKS, AKS), K8s 1.21 (GKE and kOps).

title: Redis Enterprise for Kubernetes Release Notes 6.2.4-1 (September 2021)

title: Before upgrading

text: Be aware the following changes included in this release affect the upgrade process. Please read carefully before upgrading.

title: Supported upgrade paths

text: If you are using operator version 6.2.8-15 or earlier, you cannot upgrade directly to operator versions 6.2.12 through 6.4.2-5. You must upgrade to operator version 6.2.10-45 before you can upgrade to operator versions between 6.2.12 and 6.4.2-5. However, upgrades directly to operator version 6.4.2-6 are supported.

title: OpenShift versions 6.2.12 or earlier

text:
Due to a change in the SCC, on OpenShift clusters running version 6.2.12 or earlier upgrading to version 6.2.18 or later, where `node:1` is <b>not</b> the master node, the upgrade might get stuck.

For more info and steps to prevent this issue, see [upgrade a Redis Enterprise cluster (REC)]().

Operator version 6.4.2-6 includes a fix for this issue.

title: Large clusters

text: On clusters with more than 9 REC nodes, a Kubernetes upgrade can render the Redis cluster unresponsive in some cases. A fix is available in the 6.4.2-5 release. Upgrade your operator version to 6.4.2-5 or later before upgrading your Kubernetes cluster.