We are currently experiencing significant stability issues with our KubeBlocks-managed Redis Cluster deployment. In particular, a Kubernetes worker-node failure or failover event can leave the Redis Cluster in an unstable state, and in several cases it does not recover automatically.
We understand that deploying a beta release in production introduces additional operational risk and would normally not be our preferred approach. However, the current 1.0.2 release is not providing the required reliability for our failure scenarios, so we are evaluating the 1.1.0 beta as a possible remediation.
Before proceeding, we would appreciate your recommendations on the upgrade path and any known risks, prerequisites, or validation steps specific to upgrading an existing Redis Cluster from KubeBlocks 1.0.2 to 1.1.0 beta.
Our goal is to validate the beta thoroughly in a production-like environment before considering a controlled production rollout.
We are currently experiencing significant stability issues with our KubeBlocks-managed Redis Cluster deployment. In particular, a Kubernetes worker-node failure or failover event can leave the Redis Cluster in an unstable state, and in several cases it does not recover automatically.
We understand that deploying a beta release in production introduces additional operational risk and would normally not be our preferred approach. However, the current 1.0.2 release is not providing the required reliability for our failure scenarios, so we are evaluating the 1.1.0 beta as a possible remediation.
Before proceeding, we would appreciate your recommendations on the upgrade path and any known risks, prerequisites, or validation steps specific to upgrading an existing Redis Cluster from KubeBlocks 1.0.2 to 1.1.0 beta.
Our goal is to validate the beta thoroughly in a production-like environment before considering a controlled production rollout.