Redis Enterprise for Kubernetes 发行说明 6.0.6-6（2020 年 6 月）

支持 RS 6.0.6、新的数据库和准入控制器、各种改进和错误修复。

适用于 Kubernetes 的 Redis Enterprise

Redis Enterprise for Kubernetes 6.0.6-6 现已推出。此版本包括 Redis Enterprise （RS） 版本 6.0，并引入了新功能、改进和错误修复。

概述

此版本的 Operator 提供：

  • 支持 Redis Enterprise Software 版本 6.0.6
  • 包括新的数据库和准入控制器
  • 各种改进和错误修复

要将部署升级到此最新版本，请参阅“在 Kubernetes 上升级 Redis Enterprise 集群 （REC）”。

注意：
如果您在以前的版本上运行主动-主动 （CRBD） 数据库，则此时不要升级到 6.0.6-6。目前正在调查的升级过程存在问题 （RED43635）。有关更多信息和支持，请联系 Redis 支持。

图像

  • Redis 企业版 - redislabs/redis：6.0.6-6 或 redislabs/redis：6.0.6-6.rhel7-openshift
  • 运算符 - redislabs/operator：6.0.6-6 或 redislabs/operator：6.0.6-6.rhel7
  • 服务主机 - redislabs/k8s-controller：6.0.6-6 或 redislabs/k8s-controller：6.0.6-6.rhel7

新增功能和改进

  • Database controller - 运算符中的新数据库控制器提供了创建 以及通过自定义资源 （RED36516） 管理 Redis Enterprise 集群上的数据库。

  • 准入控制器 - 运算符中的新准入控制器提供 数据库自定义资源 （RED36458）。

  • Pod 容忍度 - 支持指定节点污点的 Redis Enterprise 集群节点 Pod 容忍度 已添加到集群 CR 中（参见 podTolerations）（RED33069）。

  • Pod 注释 - 支持指定 Redis Enterprise 集群节点 Pod 注释 添加到集群 CR 中（参见 podAnnotations）（RED35613）。

  • Kubernetes 版本 - 添加了对 Kubernetes 1.17 的支持，并且不再支持 1.9 和 1.10 版本（以前已弃用）（RED41049）。

  • 改进的 OLM 体验 - OLM （OperatorHub） 中的整体用户体验和文档已得到改进 （RED37008）。

  • Resource limits - 资源限制已添加到建议的 Operator 配置 （RED39572）。

  • 添加了 LoadBalancer 服务类型 - 该LoadBalancer值已添加到databaseServiceType选项servicesRiggerSpec（RED43215）：

    servicesRiggerSpec:
   databaseServiceType: LoadBalancer

Important fixes

  • Service creation failure causes cluster setup failure (RED37197)
  • UI service update failure (RED37198)
  • Error shown in OLM deployment: "The field status.state is invalid" (RED40278)
  • OLM: StatefulSet not listed as an object owned by the Redis Enterprise Cluster (RED39296)
  • Setting extraLabels in the cluster CR did not label pods on OpenShift (RED39763)
  • log_collector failed to get the pods logs when a namespace wasn't given (RED39292)
  • Role and RoleBinding created or updated using an existing ServiceAccount in REC spec (RED42912)

Known limitations

  • CrashLoopBackOff pod status and cluster recovery - When a pod status is CrashLoopBackOff and we run the cluster recovery, the process will not complete. The solution is to delete the crashing pods manually and recovery process will continue (RED33713).

  • Active-Active (CRDB) - limitation on cluster name length - 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. Cluster names must be limited to 20 characters or less (RED25871).

  • Active-Active (CRDB) service broker cleanup - The service broker doesn't clean up database service bindings in case of failures. These bindings must be removed manually (RED25825).

  • Service broker deployment error - The service broker deployment results in an error when two types of service naming schemes are set. Choosing one of the methods will resolve this error (redis-port is the recommended default) (RED25547).

  • Cluster spec invalid errors not reported - A cluster CR specification error is not reported if two or more invalid CR resources are updated in sequence (RED25542).

  • Unreachable cluster does not produce an error - When a cluster is in an unreachable state the state is still running instead of being reported as an error (RED32805).

  • Readiness probe ignores rladmin failure - STS Readiness probe doesn't mark a node as not ready when rladmin status nodes fails (RED39300).

  • Missing permission for role - The redis-enterprise-operator role is missing permission on replicasets (RED39002).

  • Openshift 3.11 doesn't support DockerHub private registry - Openshift 3.11 doesn't support DockerHub private registry. This is a known OpenShift issue and not addressable by Redis Enterprise for Kubernetes (RED38579).

  • Possible DNS conflicts within cluster nodes - DNS conflicts are possible between the cluster mdns_server and the K8s DNS. This only impacts DNS resolution from within cluster node and while using the full fqdn *.cluster.local (RED37462).

  • 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).

  • 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.

  • Cluster name is limited on OpenShift via OLM - In OLM-deployed operators, the deployment of the cluster will fail if the name is not "rec". When the operator is deployed via the OLM, the security context constraints (scc) is bound to a specific service account name (i.e., "rec"). Naming the cluster "rec" resolves the issue (RED39825).

Coming Soon

The following lists features, fixes and changes the Redis team is currently investing in:

  • 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:

    • Redis Enterprise - A UBI (RHEL 7) base image will replace the Ubuntu and the RHEL7 base images
    • Operator - An Image built from scratch containing the Golang executable will replace the Ubuntu and the RHEL7 base images
    • Services Rigger - A UBI (RHEL 7) base image will replace the Ubuntu and the RHEL7 base images

  • 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.

  • Additional Redis Enterprise Database configuration options in the Database Controller - We're currently investing in the following additional capabilities of the Database Controller:

    • Support for loading database modules
    • Support for setting up Alerts, expressed as K8s events
    • Support for configuring database backup options
    • Support for Kubernetes 1.18
    • Support for Rancher K8s distribution
RATE THIS PAGE
Back to top ↑