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
Currently all pods in a component share the same podTemplate and volumeClaimTemplate, and restricted by the current design(one RSM mapping to one StatefulSet), it's impossible to remove pod with ordinal less than the biggest one. but there are scenarios need to break these constraints:
in a primary-secondary cluster, the secondary pod should be configured with less CPU or memory resources for cost saving.
in a raft-based cluster, the logger pod should be configured with less storage resource for cost saving.
some outer system that interacting with KubeBlocks has its own update strategy and needs the capability to apply it to the low-level pod directly.
A reasonable design to overcome these drawbacks is mapping RSM's one replica to one StatefulSet, and provides API field(s) in RSM, Component and Cluster to configure each replica separately.
Another design is managing pods and pvcs directly to allow separate configuration.
The text was updated successfully, but these errors were encountered:
Currently all pods in a component share the same
podTemplate
andvolumeClaimTemplate
, and restricted by the current design(one RSM mapping to one StatefulSet), it's impossible to remove pod with ordinal less than the biggest one. but there are scenarios need to break these constraints:A reasonable design to overcome these drawbacks is mapping RSM's one replica to one StatefulSet, and provides API field(s) in RSM, Component and Cluster to configure each replica separately.
Another design is managing pods and pvcs directly to allow separate configuration.
The text was updated successfully, but these errors were encountered: