New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replica set with same names(id's) for redis-enterprise-operator in different namespaces #174
Comments
Hi, I have just seen this on a customer deployment, and while I found it strange, I am not sure it would cause an issue. You will probably notice this for other replicasets as well. |
@laurentdroin 1.16.7 We have lot of rs running in cluster no other rs have identical id's |
@saiharshitachava What "flavor" of k8s is it? Openshift? Rancher? GKE? |
Its open source cluster |
I was looking into it and it's possible that the ID used comes from the "pod-template-hash". And so it's possible that if different RS have the same contents, they will have the same ID. I am checking this. |
sure @laurentdroin please update the thread if you find something |
From https://kubernetes.io/docs/concepts/workloads/controllers/_print/
and
So it should be all good. |
In my case, the "RANDOM-STRING" seems to be the pod template hash, and not a random number using that hash as the seed so I am still not completely sure what's going on. |
We have this rec installed on our kube cluster in two different namespaces but when we the replica set name of redis-enterprise-operator deployment..the rs names are same even the ID's ..IS this by design?
The text was updated successfully, but these errors were encountered: