Deploy mutiple operators, some with AdvancedStatefulset=true, which means use AdvancedStatefulset, some use Kubernetes built-in Statefulset.
Switch between these operators by changing the labels of TidbCluster.
What did you expect to see?
Because different operators use different Statefulsets, it should not be able to switch between them.
What did you see instead?
When tidb-controller-manager taked over TidbCluster after labels are matched with label selector, it will create AdvancedStatefulset or built-in StatefulSet according to the feature , which may lead to two different kind of Statefulset exist at the same time, but the new Statefulset can't create any Pod, because Pod names are being used.
Bug Report
What did you do?
What did you expect to see? Because different operators use different Statefulsets, it should not be able to switch between them.
What did you see instead? When
tidb-controller-manager
taked over TidbCluster after labels are matched with label selector, it will create AdvancedStatefulset or built-in StatefulSet according to the feature , which may lead to two different kind of Statefulset exist at the same time, but the new Statefulset can't create any Pod, because Pod names are being used.