[Features] Stateless components should support the maxSurge setting for rolling updates.

[groobyming]

What is the user interaction of your feature
At present, ​​KubeBlocks​​ only supports ​​maxUnavailable​​ and ​​partition​​ in the ​​instanceUpdateStrategy​​ for component instances. However, for ​​stateless components​​ (e.g., ​​VictoriaMetrics' VmSelect​​), it is generally recommended to configure ​​maxSurge​​ during updates to ensure ​​service stability​​.

Is your feature request related to a problem? Please describe.
Stateless components do not support the maxSurge configuration.

In previous versions of the documentation, I found that within the clusterDefinition's ClusterComponentDefinition, one could configure the workloadType and then set the maxSurge and maxUnavailable properties under updateStrategy via statelessSpec. However, in later versions, it seems this configuration is no longer supported. Could you clarify why this change was made?

https://kubeblocks.io/docs/release-0_9/user_docs/developer/api-reference/cluster#apps.kubeblocks.io/v1alpha1.StatelessSetSpec

[shanshanying]

hi @groobyming ,

Stateless workload is deprecated and not supported since KB V0.9, and these is no Stateless components in KubeBlocks.
KB focus on managing stateful workloads at the moment. And you question is like "will kubeblocks supports stateless workload in the furture" ?

I wil convert this issue into discussion, and we can discuss in more details.