tongdun / td-redis-operator Goto Github PK

测试步骤：
1、创建redis集群；
2、向redis集群写入一些数据；
3、重启部分pod，新重启的pod里，会被判定为有槽位信息（podInCluster函数），那么这些pod就不会被加入集群；

重启pod的redis相关日志如下：

1:M 25 Jul 2023 02:28:25.269 * DB loaded from disk: 0.000 seconds
1:M 25 Jul 2023 02:28:25.269 # I have keys for unassigned slot 3300. Taking responsibility for it.
1:M 25 Jul 2023 02:28:25.272 * Ready to accept connections

虽然nodes.conf是未被持久化的，但启动后，还是会被redis给写入槽位数据：

# cat /home/admin/redis/nodes.conf 
9ee910e301fef3ba741011d2e472379daa262f9a :6379@16379 myself,master - 0 0 0 connected 3300
vars currentEpoch 0 lastVoteEpoch 0

使用命令

kubectl apply -f https://raw.githubusercontent.com/tongdun/td-redis-operator/main/cr/redis_cluster.yaml

会默认安装，对内存要求还挺高的，一直处于Pending状态。

如果修改redis_cluster.yaml文件，将proxyimage去掉，会报错，安装不了，改成“”空字符串，是没有安装了。
但是连redis-cluster-trump这个Service的Endpoints都没有了……，说明Operator那里出问题了。

请问下你们代理是自研的吗，是否有相关说明和部署文档

_{Sent from PPHub}

Hello
when adding a repo to my helmm I have this issue, perhaps it needs a name for the version 0.1.0 for the operator

Thanks a lot
index.go:346: skipping loading invalid entry for chart "td-redis-operator" "0.1.0" from https://tongdun.github.io/td-redis-operator/charts/td-redis-operator: validation: chart.metadata.name is required

报错信息如下

Could not connect to Redis at sentinel-standby-crawler-redis-2.sentinel-standby-crawler-redis.redis.svc.cluster.local:26379: Name or service not known
2023-12-22T14:42:53.236708068+08:00 Could not connect to Redis at sentinel-standby-crawler-redis-2.sentinel-standby-crawler-redis.redis.svc.cluster.local:26379: Name or service not known
2023-12-22T14:42:53.246455920+08:00 Could not connect to Redis at sentinel-standby-crawler-redis-2.sentinel-standby-crawler-redis.redis.svc.cluster.local:26379: Name or service not known
2023-12-22T14:42:53.312395104+08:00 Could not connect to Redis at sentinel-standby-crawler-redis-2.sentinel-standby-crawler-redis.redis.svc.cluster.local:26379: Name or service not known
2023-12-22T14:42:54.336460067+08:00 Could not connect to Redis at sentinel-standby-crawler-redis-2.sentinel-standby-crawler-redis.redis.svc.cluster.local:26379: Name or service not known
2023-12-22T14:42:55.356507794+08:00 Could not connect to Redis at sentinel-standby-crawler-redis-2.sentinel-standby-crawler-redis.redis.svc.cluster.local:26379: Name or service not known
2023-12-22T14:42:56.411673398+08:00 /usr/local/bin/docker-entrypoint.sh: line 12: [: =: unary operator expected

哪里有设置db数量的配置 现在连接上去 一个db都没

目前各个镜像是策略是always，在离线环境并且没有镜像库时安装时会导致找不到镜像。

操作，想部署主备：
kubectl apply -f deploy.yaml
kubectl apply -f redis_standby.yaml

[root@localhost td-redis]# kubectl get all -n redis
NAME READY STATUS RESTARTS AGE
pod/operator-7785578894-swjwg 1/1 Running 0 15h
pod/redis-standby-tom-0 1/2 Running 60 (15m ago) 15h
pod/sentinel-standby-tom-0 1/1 Running 171 (43s ago) 15h
pod/sentinel-standby-tom-1 1/1 Running 175 (41s ago) 15h
pod/sentinel-standby-tom-2 1/1 Running 173 (39s ago) 15h

NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/redis-standby-tom ClusterIP 10.96.120.210 6379/TCP 15h
service/sentinel-standby-tom ClusterIP 10.97.94.185 26379/TCP 15h

NAME READY UP-TO-DATE AVAILABLE AGE
deployment.apps/operator 1/1 1 1 15h

NAME DESIRED CURRENT READY AGE
replicaset.apps/operator-7785578894 1 1 1 15h

NAME READY AGE
statefulset.apps/redis-standby-tom 0/2 15h
statefulset.apps/sentinel-standby-tom 3/3 15h

现有代码中，重启redis的pod后，在createRedisCluster函数中，podsNotinCluster中的pod逐个向podsInCluster的pod去meet，从而再加入集群。
但是，如果原redis集群中，所有pod同时重启后，podsInCluster中pod的个数为0，不能再meet，也就无法恢复集群了。
请问这种情况，需要如何处理？

假如外网访问具体ingress映射到哪个服务上，还有内部访问方式是servername+namespace.svc这种方式访问？

Hello,

where can i find the docker images used in this project
tongduncloud/redis-cluster for example
And what's the difference between official images ?

Thanks a lot

有响应的部署维护文档吗

无法拉取镜像？

如题。

1. 我pull了master的代码。执行./hack/update-codegen.sh没有成功。
2. 另外，我执行make命令，发现只是执行了go generate，查看makefile，默认的targe命中了codegen，建议增加一个alltarget。

二进制部署在物理主机上面可以不呀