As the fields of policy API expand, there are more and more composite scenarios that require verification.
Though we can disable user misconfiguration at runtime, it is not as effective as blocking user input at the source.
At the same time, users configure fields in the API, but it does not take effect, which also makes users confused.
For example，
SchedulingMode is Duplicate, will not work with replicaStrategy.
ReplicaStrategy is spread, will not work with maxClusters.
Moreover, in the early stages of some features, we can prevent some unpredictable scenarios by limiting its changes.
We will not allow users to make these kinds of modifications until we have fully verified it.
For example, users change replicaStrategy=weighted to binpack.
As the fields of policy API expand, there are more and more composite scenarios that require verification. Though we can disable user misconfiguration at runtime, it is not as effective as blocking user input at the source. At the same time, users configure fields in the API, but it does not take effect, which also makes users confused.
For example， SchedulingMode is Duplicate, will not work with replicaStrategy. ReplicaStrategy is spread, will not work with maxClusters.
Moreover, in the early stages of some features, we can prevent some unpredictable scenarios by limiting its changes. We will not allow users to make these kinds of modifications until we have fully verified it.
For example, users change replicaStrategy=weighted to binpack.