{
  "schema_version": 2,
  "id": "operate/kubernetes/release-notes/previous-releases/k8s-6-0-6-6",
  "title": "Redis Enterprise for Kubernetes Release Notes 6.0.6-6 (June 2020)",
  "url": "https://redis.io/docs/latest/operate/kubernetes/release-notes/previous-releases/k8s-6-0-6-6/",
  "summary": "Support for RS 6.0.6, new database and admission controllers, various improvements and bug fixes.",
  "tags": [
    "docs",
    "operate",
    "kubernetes"
  ],
  "last_updated": "2026-09-28T13:45:38+01:00",
  "page_type": "content",
  "content_hash": "c5e93aa1fd0856d4d44efead32b2582773d0dd455ba809f8beea83cd6b906be0",
  "sections": [
    {
      "id": "overview-1",
      "title": "Overview",
      "role": "overview",
      "text": "Redis Enterprise for Kubernetes 6.0.6-6 is now available. This release includes Redis Enterprise (RS) version [6.0](https://redis.io/docs/latest/operate/rs/release-notes/rs-6-0-may-2020) and introduces new features, improvements, and bug fixes."
    },
    {
      "id": "overview",
      "title": "Overview",
      "role": "overview",
      "text": "This release of the operator provides:\n\n- Support for the Redis Enterprise Software release 6.0.6\n- Includes the new database and admission controllers\n- Various improvements and bug fixes\n\nTo upgrade your deployment to this latest release, see [\"Upgrade a Redis Enterprise cluster (REC) on Kubernetes\"](https://redis.io/docs/latest/operate/kubernetes/upgrade/upgrade-redis-cluster).\n\n> [!NOTE]\n> If you are running Active-Active (CRBD) databases on a previous release, do not upgrade to 6.0.6-6 at this time. There is an issue with the upgrade process that is currently being investigated (RED43635). For more information and support please [contact Redis support](https://redislabs.com/company/support/)."
    },
    {
      "id": "images",
      "title": "Images",
      "role": "content",
      "text": "- **Redis Enterprise** - redislabs/redis:6.0.6-6 or redislabs/redis:6.0.6-6.rhel7-openshift\n- **Operator** - redislabs/operator:6.0.6-6 or redislabs/operator:6.0.6-6.rhel7\n- **Services Rigger** - redislabs/k8s-controller:6.0.6-6 or redislabs/k8s-controller:6.0.6-6.rhel7"
    },
    {
      "id": "new-features-and-improvements",
      "title": "New features and improvements",
      "role": "content",
      "text": "- Database controller - A new database controller in the operator provides the ability to create\nand manage databases on a Redis Enterprise cluster via a custom resource (RED36516).\n\n- Admission controller - A new admission controller in the operator provides validation of\ndatabase custom resources (RED36458).\n\n- Pod tolerations - Support for specifying Redis Enterprise cluster node pod tolerations of node taints\nhas been added to the cluster CR (see podTolerations) (RED33069).\n\n- Pod annotations - Support for specifying Redis Enterprise cluster node pod annotations has been\nadded to the cluster CR (see podAnnotations) (RED35613).\n\n- Kubernetes versions - Support for Kubernetes 1.17 was added and versions 1.9 and 1.10 (previously deprecated) are no longer supported (RED41049).\n\n- Improved OLM Experience - The overall user experience and documentation in the OLM (OperatorHub) has been improved (RED37008).\n\n- Resource limits - Resource limits have been added to the recommended operator configuration (RED39572).\n\n- LoadBalancer service type added - The `LoadBalancer` value has been added to the `databaseServiceType` option in `servicesRiggerSpec` (RED43215):\n\n    [code example]"
    },
    {
      "id": "important-fixes",
      "title": "Important fixes",
      "role": "content",
      "text": "- Service creation failure causes cluster setup failure (RED37197)\n- UI service update failure (RED37198)\n- Error shown in OLM deployment: \"The field status.state is invalid\" (RED40278)\n- OLM: StatefulSet not listed as an object owned by the Redis Enterprise Cluster (RED39296)\n- Setting extraLabels in the cluster CR did not label pods on OpenShift (RED39763)\n- log_collector failed to get the pods logs when a namespace wasn't given (RED39292)\n- Role and RoleBinding created or updated using an existing ServiceAccount in REC spec (RED42912)"
    },
    {
      "id": "known-limitations",
      "title": "Known limitations",
      "role": "content",
      "text": "- CrashLoopBackOff pod status and cluster recovery - When a pod status is CrashLoopBackOff and we run the cluster recovery, the process\nwill not complete. The solution is to delete the crashing pods manually and\nrecovery process will continue (RED33713).\n\n- Active-Active (CRDB) - limitation on cluster name length - A cluster name longer than 20 characters will result in a rejected route\nconfiguration as the host part of the domain name exceeds 63 characters. Cluster\nnames must be limited to 20 characters or less (RED25871).\n\n- Active-Active (CRDB) service broker cleanup - The service broker doesn't clean up database service bindings in case of failures.\nThese bindings must be removed manually (RED25825).\n\n- Service broker deployment error - The service broker deployment results in an error when two types of service naming\nschemes are set. Choosing one of the methods will resolve this error (`redis-port`\nis the recommended default) (RED25547).\n\n- Cluster spec invalid errors not reported - A cluster CR specification error is not reported if two or more invalid CR resources are\nupdated in sequence (RED25542).\n\n- Unreachable cluster does not produce an error - When a cluster is in an unreachable state the state is still `running` instead of\nbeing reported as an error (RED32805).\n\n- Readiness probe ignores rladmin failure - STS Readiness probe doesn't mark a node as not ready when rladmin status nodes fails (RED39300).\n\n- Missing permission for role - The redis-enterprise-operator role is missing permission on replicasets (RED39002).\n\n- Openshift 3.11 doesn't support DockerHub private registry - Openshift 3.11 doesn't support DockerHub private registry. This is a known OpenShift\nissue and not addressable by Redis Enterprise for Kubernetes (RED38579).\n\n- Possible DNS conflicts within cluster nodes - DNS conflicts are possible between the cluster mdns_server and the K8s DNS.\nThis only impacts DNS resolution from within cluster node and while using the full fqdn *.cluster.local (RED37462).\n\n- Coexistence of 5.4.10 and 5.4.6 clusters - K8s clusters with Redis Enterprise 5.4.6 clusters are negatively affected by installing a Redis Enterprise 5.4.10 cluster due to changes in CRD (CustomeResourceDefinition) (RED37233).\n\n- Redis Enterprise CPU utilization metric reports at K8s node level rather than at pod level - In Kubernetes, the node CPU usage we report on is the usage of the K8S worker node hosting the REC pod (RED-36884). Pod resource utilization should be measured by K8s-native means rather than through the application.\n\n- Cluster name is limited on OpenShift via OLM - In OLM-deployed operators, the deployment of the cluster will fail if the name\nis not \"rec\". When the operator is deployed via the OLM, the security context constraints (scc)\nis bound to a specific service account name (i.e., \"rec\"). Naming the cluster\n\"rec\" resolves the issue (RED39825)."
    },
    {
      "id": "coming-soon",
      "title": "Coming Soon",
      "role": "content",
      "text": "The following lists features, fixes and changes the Redis team is currently investing in:\n\n- Redis Enterprise and Kubernetes Container Artifacts - tarting from the next release of Redis Enterprise for K8s, new container artifacts will be published using different base images:\n\n    - **Redis Enterprise** - A UBI (RHEL 7) base image will replace the Ubuntu and the RHEL7 base images\n    - **Operator** - An Image built from scratch containing the Golang executable will replace the Ubuntu and the RHEL7 base images\n    - **Services Rigger** - A UBI (RHEL 7) base image will replace the Ubuntu and the RHEL7 base images\n\n- Deprecation notice - he service broker solution is deprecated and will not be supported starting from the next release of the Redis Enterprise Operator for Kubernetes.\n\n- Additional Redis Enterprise Database configuration options in the Database Controller - We're currently investing in the following additional capabilities of the Database Controller:\n    - Support for loading database modules\n    - Support for setting up Alerts, expressed as K8s events\n    - Support for configuring database backup options\n    - Support for Kubernetes 1.18\n    - Support for Rancher K8s distribution"
    }
  ],
  "examples": [
    {
      "id": "new-features-and-improvements-ex0",
      "language": "yaml",
      "code": "servicesRiggerSpec:\n       databaseServiceType: LoadBalancer",
      "section_id": "new-features-and-improvements"
    }
  ]
}