The default priority of localization for dynamic scheduling is 1000(the highest), which is not flexible

[abstractmj]

when migrate third-party workload(like openkruise https://openkruise.io/zh/docs/user-manuals/advancedstatefulset) to clusternet, we may need to implements certain controller logic to override the default localization. the default priority 1000 make this difficult;

[dixudx]

@abstractmj The default localization with highest priority 1000 is created based on the scheduling results. This object is only created when the scheduling strategy is Dividing. This design helps make sure the clusternet-created localization object for changing replicas can work as desired.

For your case, I think we may introduce a new field in Localization to indicate this localization could override clusternet-created localizations with the same priority.

[abstractmj]

sounds reasonable

@abstractmj The default localization with highest priority 1000 is created based on the scheduling results. This object is only created when the scheduling strategy is Dividing. This design helps make sure the clusternet-created localization object for changing replicas can work as desired.

For your case, I think we may introduce a new field in Localization to indicate this localization could override clusternet-created localizations with the same priority.

sounds reasonable