OT-CONTAINER-KIT / helm-charts

A repository which that will contain helm charts with best and security practices.
https://ot-container-kit.github.io/helm-charts
49 stars 84 forks source link

cluster ends up attempting to form with addresses on k8s and fails in 0.12 charts, but works in 0.10 charts #56

Closed enenum closed 1 year ago

enenum commented 1 year ago

What am I doing - installing the redis-operator/redis-cluster on rke2 on-prem cluster the earlier v0.10 of the setup works fine - is able to find and successfully use pod ip addresses the current 0.12 charts have this problem. I wanted to use 0.12 for the promised ease of setting up persistenceEnabled = no

BTW - how to turn persistence off in 0.10 charts? Is it not supported? Is there another way to affect what ends up in the redis.conf files?

cluster formation fails with this error:

{
  "level": "error",
  "ts": 1670004561.9619787,
  "logger": "controller_redis",
  "msg": "Could not execute command",
  "Request.RedisManager.Namespace": "redis12",
  "Request.RedisManager.Name": "redis-cluster",
  "Command": [
    "redis-cli",
    "--cluster",
    "create",
    "redis-cluster-leader-0.redis-cluster-leader-headless.redis12.svc:6379",
    "redis-cluster-leader-1.redis-cluster-leader-headless.redis12.svc:6379",
    "redis-cluster-leader-2.redis-cluster-leader-headless.redis12.svc:6379",
    "--cluster-yes"
  ],
  "Output": "",
  "Error": "Could not connect to Redis at redis-cluster-leader-2.redis-cluster-leader-headless.redis12.svc:6379: Name does not resolve\n",
  "error": "command terminated with exit code 1",
  "stacktrace": "redis-operator/k8sutils.ExecuteRedisClusterCommand
    /workspace/k8sutils/redis.go:116\nredis-operator/controllers.(*RedisClusterReconciler).Reconcile\n\t/workspace/controllers/rediscluster_controller.go:123
    sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Reconcile
      /go/pkg/mod/sigs.k8s.io/controller-runtime@v0.11.0/pkg/internal/controller/controller.go:114
    sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler
      /go/pkg/mod/sigs.k8s.io/controller-runtime@v0.11.0/pkg/internal/controller/controller.go:311
    sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.11.0/pkg/internal/controller/controller.go:266
    sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2
      /go/pkg/mod/sigs.k8s.io/controller-runtime@v0.11.0/pkg/internal/controller/controller.go:227"
}
iamabhishek-dubey commented 1 year ago

This is not a bug. Please check the clusterVersion of redis. https://github.com/OT-CONTAINER-KIT/helm-charts/blob/main/charts/redis-cluster/values.yaml#L4

biyn-tech commented 1 year ago

I perhaps should have come back with more updates. I got as far as what you have pointed out about the versions. I was able to get clusters to come up with either version.

However I still have issues with v7 coming up successfully in an Istio mesh where I am successfully running the v6. This is clearly a different issue though.