Update the manual test for update/rollback

Author: sanposhiho

keps/sig-scheduling/3022-min-domains-in-pod-topology-spread/README.md

@@ -383,18 +383,23 @@ are missing a bunch of machinery and tooling and can't do that now.
 Yes. The behavior is changed as expected.
 
 Test scenario:
-1. start kube-apiserver where `MinDomains` feature is enabled. 
+1. start kube-apiserver v1.24 where `MinDomains` feature is disabled. 
 2. create three nodes and pods spread across nodes as 2/2/1
 3. create new Pod that has a TopologySpreadConstraints: maxSkew is 1, topologyKey is `kubernetes.io/hostname`, and minDomains is 4 (larger than the number of domains (= 3)).
-4. the Pod created in (3) isn't scheduled because of `MinDomain`.
+4. the Pod created in (3) is scheduled because `MinDomain` is disabled.
 5. delete the Pod created in (3).
-6. recreate kube-apiserver where `MinDomains` feature is disabled.
+6. recreate kube-apiserver v1.25 where `MinDomains` feature is enabled.
 7. create the same Pod as (3).
-8. the Pod created in (7) is scheduled because `MinDomain` is disabled.
+8. the Pod created in (7) isn't scheduled because `MinDomain` is enabled and minDomains is larger than the number of domains (= 3)).
 9. delete the Pod created in (7).
-10. recreate kube-apiserver where `MinDomains` feature is enabled.
+10. recreate kube-apiserver v1.24 where `MinDomains` feature is disabled.
 11. create the same Pod as (3).
-12. the Pod created in (11) isn't scheduled because of `MinDomain`.
+12. the Pod created in (11) is scheduled because `MinDomain` is disabled.
+13. delete the Pod created in (11).
+14. recreate kube-apiserver v1.25 where `MinDomains` feature is enabled.
+15. create the same Pod as (3).
+16. the Pod created in (15) isn't scheduled because `MinDomain` is enabled and minDomains is larger than the number of domains (= 3)).
+17. delete the Pod created in (15).
 
 ###### Is the rollout accompanied by any deprecations and/or removals of features, APIs, fields of API types, flags, etc.?