You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice if there was a way in the Operator to define two separate sets of replicas. One for read-write usage, and one for read-only. While these would all be replicas, part of a single shard, and technically all be read-write (from what I understand), the operator could help here be placing specific read-only labels on the CHI that are for Select queries. Then a separate Kubernetes Service resource that only points to those CHI only could be used.
I know this a simple explanation, and gets more complex with multiple shards. There are some ways to do this in the existing operator, but a nice interface in the CRD would be great.
The text was updated successfully, but these errors were encountered:
It would be nice if there was a way in the Operator to define two separate sets of replicas. One for read-write usage, and one for read-only. While these would all be replicas, part of a single shard, and technically all be read-write (from what I understand), the operator could help here be placing specific read-only labels on the CHI that are for Select queries. Then a separate Kubernetes Service resource that only points to those CHI only could be used.
I know this a simple explanation, and gets more complex with multiple shards. There are some ways to do this in the existing operator, but a nice interface in the CRD would be great.
The text was updated successfully, but these errors were encountered: