{
  "schema_version": 2,
  "id": "operate/kubernetes/release-notes/previous-releases/k8s-6-0-8-1",
  "title": "Redis Enterprise for Kubernetes Release Notes 6.0.8-1 (October 2020)",
  "url": "https://redis.io/docs/latest/operate/kubernetes/release-notes/previous-releases/k8s-6-0-8-1/",
  "summary": "Support for RS 6.0.8-28, OpenShift 4.5, K8s 1.18, and Gesher admission controller proxy.",
  "tags": [
    "docs",
    "operate",
    "kubernetes"
  ],
  "last_updated": "2026-09-28T13:45:38+01:00",
  "page_type": "content",
  "content_hash": "e90762b71c791e8823e3e93433936cf6b47c8b5b8cacf8f3114e8600d0844e9d",
  "sections": [
    {
      "id": "overview-1",
      "title": "Overview",
      "role": "overview",
      "text": "The Redis Enterprise K8s 6.0.8-1 release is a *major release* on top of [6.0.6-24](https://github.com/RedisLabs/redis-enterprise-k8s-docs/releases/tag/v6.0.6-24) providing support for the latest [Redis Enterprise Software release 6.0.8-28](https://redis.io/docs/latest/operate/rs/release-notes/rs-6-0-8-september-2020/) and includes several enhancements (including OpenShift 4.5 and Kubernetes 1.18 support) and bug fixes."
    },
    {
      "id": "overview",
      "title": "Overview",
      "role": "overview",
      "text": "This release of the operator provides:\n\n * New features\n * New support K8s distributions and platforms\n * Various bug fixes\n\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)."
    },
    {
      "id": "images",
      "title": "Images",
      "role": "content",
      "text": "* **Redis Enterprise** - redislabs/redis:6.0.8-28 or redislabs/redis:6.0.8-28.rhel7-openshift\n * **Operator** - redislabs/operator:6.0.8-1\n * **Services Rigger** - redislabs/k8s-controller:6.0.8-1 or redislabs/services-manager:6.0.8-1 (Red Hat registry)"
    },
    {
      "id": "new-features",
      "title": "New features",
      "role": "content",
      "text": "* Redis [Modules](https://redislabs.com/redis-enterprise/modules/) can now be [configured](https://github.com/RedisLabs/redis-enterprise-k8s-docs/blob/master/redis_enterprise_database_api.md#dbmodule) in the database custom resource.\n * Support was added for **[OpenShift 4.5](https://docs.openshift.com/container-platform/4.5/release_notes/ocp-4-5-release-notes.html)**\n * Support was added for **Kubernetes 1.18**\n * Added support for the Gesher admission control proxy to provide an administrator the ability to setup delegation to avoid the need for administrator intervention on every namespaced deployed operator."
    },
    {
      "id": "important-fixes",
      "title": "Important fixes",
      "role": "content",
      "text": "* Added the missing Services Rigger health check (RED47062)\n * Fixed failures when updating the ui service type (RED45771)"
    },
    {
      "id": "known-limitations",
      "title": "Known limitations",
      "role": "content",
      "text": ""
    },
    {
      "id": "crashloopbackoff-causes-cluster-recovery-to-be-incomplete--red33713",
      "title": "CrashLoopBackOff causes cluster recovery to be incomplete  (RED33713)",
      "role": "content",
      "text": "When a pod status is CrashLoopBackOff and we run the cluster recovery, the process will not complete. The workaround is to delete the crashing pods manually and recovery process will continue."
    },
    {
      "id": "long-cluster-names-cause-routes-to-be-rejected--red25871",
      "title": "Long cluster names cause routes to be rejected  (RED25871)",
      "role": "content",
      "text": "A cluster name longer than 20 characters will result in a rejected route configuration as the host part of the domain name exceeds 63 characters. The workaround is to limit cluster name to 20 characters or less."
    },
    {
      "id": "cluster-cr-rec-errors-are-not-reported-after-invalid-updates-red25542",
      "title": "Cluster CR (REC) errors are not reported after invalid updates (RED25542)",
      "role": "content",
      "text": "A cluster CR specification error is not reported if two or more invalid CR resources are updated in sequence."
    },
    {
      "id": "an-unreachable-cluster-has-status-running-red32805",
      "title": "An unreachable cluster has status running (RED32805)",
      "role": "content",
      "text": "When a cluster is in an unreachable state the state is still running instead of being reported as an error."
    },
    {
      "id": "readiness-probe-incorrect-on-failures-red39300",
      "title": "Readiness probe incorrect on failures (RED39300)",
      "role": "content",
      "text": "STS Readiness probe doesn't mark a node as not ready when rladmin status on the node fails."
    },
    {
      "id": "role-missing-on-replica-sets-red39002",
      "title": "Role missing on replica sets (RED39002)",
      "role": "content",
      "text": "The redis-enterprise-operator role is missing permission on replica sets."
    },
    {
      "id": "private-registries-are-not-supported-on-openshift-311-red38579",
      "title": "Private registries are not supported on OpenShift 3.11 (RED38579)",
      "role": "content",
      "text": "Openshift 3.11 doesn't support dockerhub private registry. This is a known OpenShift issue."
    },
    {
      "id": "internal-dns-and-kubernetes-dns-may-have-conflicts-red37462",
      "title": "Internal DNS and Kubernetes DNS may have conflicts (RED37462)",
      "role": "content",
      "text": "DNS conflicts are possible between the cluster mdns_server and the K8s DNS. This only impacts DNS resolution from within cluster nodes for Kubernetes DNS names."
    },
    {
      "id": "5410-negatively-impacts-546-red37233",
      "title": "5.4.10 negatively impacts 5.4.6 (RED37233)",
      "role": "content",
      "text": "Kubernetes-based 5.4.10 deployments seem to negatively impact existing 5.4.6 deployments that share a Kubernetes cluster."
    },
    {
      "id": "node-cpu-usage-is-reported-instead-of-pod-cpu-usage-red36884",
      "title": "Node CPU usage is reported instead of pod CPU usage (RED36884)",
      "role": "content",
      "text": "In Kubernetes, the node CPU usage we report on is the usage of the Kubernetes worker node hosting the REC pod."
    },
    {
      "id": "master-pod-label-in-rancher-red42896",
      "title": "Master pod label in Rancher (RED42896)",
      "role": "content",
      "text": "Master pod is not always labeled in Rancher."
    },
    {
      "id": "cluster-fail-to-start-for-clusters-with-unsynchronized-clocks-red47254",
      "title": "Cluster fail to start for clusters with unsynchronized clocks (RED47254)",
      "role": "content",
      "text": "When REC clusters are deployed on clusters with unsynchronized clocks, the cluster does not start correctly. The fix is to use NTP to synchronize the underlying K8s nodes."
    },
    {
      "id": "errors-in-operator-log-for-redb-status-red44919",
      "title": "Errors in operator log for REDB status (RED44919)",
      "role": "errors",
      "text": "Benign errors are reported in the operator log when using database controller (REDB) (e.g., \"failed to update database status\". These errors can be ignored."
    },
    {
      "id": "compatibility-notes",
      "title": "Compatibility Notes",
      "role": "compatibility",
      "text": "* Support for **OpenShift 4.5** was **added**,\n* Support for **Kubernetes 1.18** was **added**,\n* Support for the previous deprecated **Kubernetes 1.11 and 1.12** has been **removed**."
    }
  ],
  "examples": []
}