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
Is your improvement request related to a problem? Please describe.
Currently [kubeblocks 0.9] OpsRequest of Switchover don't support Sharding API, the logic in Switchover didn't consider ShardingSpecs at all. So that those clusters using ShardingSpecs (like redis-cluster) have no chance to do Switchover using OpsRequest.
If this is a new function, please describe the motivation and goals.
Let those clusters using ShardingSpecs can also do Switchover using OpsRequest.
Describe the solution you'd like
Finding Component labels app.kubernetes.io/instance and apps.kubeblocks.io/sharding-name corresponding the cluster and shard.
Finding ComponentDefinition from Component's Spec.CompDef, now we can know the correct ComponentSwitchover
A little adjustment in Switchover's Job name and message in OpsRequest.status.condition to make all fine.
Describe alternatives you've considered
The current solution can not support switchover multiple instance in different shard components. To support this I think we would better update the OpsRequest.Switchover struct.
Additional context
No.
The text was updated successfully, but these errors were encountered:
Is your improvement request related to a problem? Please describe.
Currently [kubeblocks 0.9] OpsRequest of Switchover don't support Sharding API, the logic in Switchover didn't consider
ShardingSpecs
at all. So that those clusters usingShardingSpecs
(likeredis-cluster
) have no chance to do Switchover using OpsRequest.If this is a new function, please describe the motivation and goals.
Let those clusters using
ShardingSpecs
can also do Switchover using OpsRequest.Describe the solution you'd like
app.kubernetes.io/instance
andapps.kubeblocks.io/sharding-name
corresponding the cluster and shard.Spec.CompDef
, now we can know the correctComponentSwitchover
OpsRequest.status.condition
to make all fine.Describe alternatives you've considered
The current solution can not support switchover multiple instance in different shard components. To support this I think we would better update the
OpsRequest.Switchover
struct.Additional context
No.
The text was updated successfully, but these errors were encountered: