Redis-operator per namespace or one for whole cluster?

[kamilpi]

I would like to deploy redisoperator and RedisFailover per namespace. How can I do this? For now each redisoperator trying to manage all RedisFailover.

[jchanam]

Hi @normander,

Exactly, the operator manages every RedisFailover created on the cluster.

Why would you need to have one operator per namespace?

[str1k3r]

actually, I have the same request. I'm having 2 separate environments in the same clusters
dev-* and prod-*
so, would be nice to have (if possible) completely separated instances of all redis components.

[ese]

@str1k3r @normander currently it is not possible run isolated instances of redis-operator controller in the same cluster.

[rhefner1]

Like @str1k3r said, it would be best to roll out new versions of operator to the staging environment (which is just a separate namespace in our cluster) to see if they work as expected and then roll them out to prod.

It also could limit the impact of this issue: #89

[str1k3r]

very useful case. thanks @rhefner1

[kamilpi]

@jchanam How can I delete only redis cluster(statefulset and deployment) per namespace? Right now when I'm doing this, redis-operator recreate statefulset and deployment.

[jchanam]

If you want to delete a deployed RedisFailover, you just have to delete that custom resource:

kubectl -n <namespace> delete redisfailover <rf-name>

The redis operator is always checking the redis failovers deployed are alive and available. That's why, if you delete the statefulsets or the deployments, they appear again.

[github-actions]

This issue is stale because it has been open for 45 days with no activity.

[github-actions]

This issue was closed because it has been inactive for 14 days since being marked as stale.