Update sig-multicluster as owning SIG

kubernetes · Sep 20, 2022 · d12f495 · d12f495
1 parent 4ef81bc
commit d12f495
Show file tree

Hide file tree

Showing 3 changed files with 11 additions and 3 deletions.
diff --git a/keps/prod-readiness/sig-multicluster/3335.yaml b/keps/prod-readiness/sig-multicluster/3335.yaml
@@ -0,0 +1,3 @@
+kep-number: 3335
+alpha:
+  approver: "TBD"
diff --git a/...sig-apps/3335-statefulset-slice/README.md → ...icluster/3335-statefulset-slice/README.md b/...sig-apps/3335-statefulset-slice/README.md → ...icluster/3335-statefulset-slice/README.md
@@ -572,7 +572,8 @@ Any change of default behavior may be surprising to users or break existing
 automations, so be extremely careful here.
 -->
 
-No, if the new field `replicaStartOrdinal` is unset, StatefulSet will retain existing behavior.
+No, if the new StatefulSet field `.spec.replicaStartOrdinal` is unset,
+StatefulSet will retain existing behavior.
 
 ###### Can the feature be disabled once it has been enabled (i.e. can we roll back the enablement)?
 
@@ -610,7 +611,10 @@ You can take a look at one potential example of such test in:
 https://github.com/kubernetes/kubernetes/pull/97058/files#diff-7826f7adbc1996a05ab52e3f5f02429e94b68ce6bce0dc534d1be636154fded3R246-R282
 -->
 
-TBD
+Additional e2e tests will be added when targeting the Beta stage. These will
+validate the behavior of the cluster when enabled and disabled and ensure that
+existing behavior (eg: not specifying the new `replicaStartOrdinal` API) is
+preserved.
 
 ### Rollout, Upgrade and Rollback Planning
 

diff --git a/.../sig-apps/3335-statefulset-slice/kep.yaml → ...ticluster/3335-statefulset-slice/kep.yaml b/.../sig-apps/3335-statefulset-slice/kep.yaml → ...ticluster/3335-statefulset-slice/kep.yaml
@@ -2,8 +2,9 @@ title: StatefulSet Slice
 kep-number: 3335
 authors:
   - "@pwschuurman"
-owning-sig: sig-apps
+owning-sig: sig-multicluster
 participating-sigs:
+  - sig-apps
   - sig-storage
 status: provisional
 creation-date: 2022-06-02