Merge pull request #8331 from skitt/sig-multicluster-annual-report-2024

Add the 2024 SIG-Multicluster report

Author: k8s-ci-robot

sig-multicluster/README.md

@@ -73,52 +73,5 @@ The following [subprojects][subproject-definition] are owned by sig-multicluster
 [subproject-definition]: https://github.com/kubernetes/community/blob/master/governance.md#subprojects
 [working-group-definition]: https://github.com/kubernetes/community/blob/master/governance.md#working-groups
 <!-- BEGIN CUSTOM CONTENT -->
-## Subprojects
 
-### Kubefed
-Control Plane for newer Multicluster-specific APIs. Discussions are ongoing to focus future development on multi-cluster specific Kubernetes APIs rather than a reimplementation of single-cluster Kubernetes APIs.
-
-|  |  |
-| -------------- |:-------|
-| Recommended for Production | Not yet. |
-| General Availability | Beta by 2018-Q4. GA TBD. |
-| Current Level of Activity | Once to twice weekly discussions as part of Kubefed working group (most active SIG-Multicluster members). |
-| Owner(s) | Working Group |
-| Where to find it? | https://github.com/kubernetes-sigs/kubefed |
-| Meeting Agenda | https://docs.google.com/document/d/1v-Kb1pUs3ww_x0MiKtgcyTXCAuZlbVlz4_A9wS3_HXY |
-
-### Cluster Registry
-Common abstraction for a Registry of Clusters that can store per-Cluster metadata and supports Kubernetes label selection. The Cluster Registry can be deployed as a standalone or an aggregated API server and currently provides a Registry of Clusters without any actively reconciling Kubernetes controller. The API design is documented [here](https://git.k8s.io/design-proposals-archive/multicluster/cluster-registry/api-design.md) and is intended to serve as a basis to develop multicluster controllers.
-
-|  |  |
-| -------------- |:-------|
-| Recommended for Production | Not yet. |
-| General Availability | Beta by 2018-Q1, GA by 2018-Q2 (see Project plan for details). |
-| Current Level of Activity | Alpha, active development for Beta and GA milestones. |
-| Owner(s) | [@perotinus](https://github.com/perotinus), [@font](https://github.com/font) |
-| Where to find it? | https://github.com/kubernetes/cluster-registry |
-
-### Kubemci (Kube Multi-cluster Ingress)
-Ability to program Global multicluster load balancers with two deliverables:
-* Standalone CLI tool without a centralized control plane. Allows ingress configurations that span multiple clusters. It needs to be invoked whenever there is a change in the number of clusters (healthchecking is still maintained in the background). Much of this work will be folded back into the next deliverable.
-* Kubernetes style multicluster API and self-healing controller with cluster registry
-
-|  |  |
-| -------------- |:-------|
-| Recommended for Production | Not yet. |
-| General Availability | CLI: Beta by 2018-Q1, Controller: Alpha by 2018-Q1 |
-| Current Level of Activity? | CLI is alpha and team is looking for feedback. Active development is on to bring it to beta. |
-| Owner(s) | [@nikhiljindal](https://github.com/nikhiljindal), [@G-Harmon](https://github.com/G-Harmon) |
-| Where to find it? | https://github.com/GoogleCloudPlatform/k8s-multicluster-ingress |
-
-### Federation v1 (a.k.a. Cluster Federation)
-Control Plane that coordinates configuration across multiple clusters by presenting a subset of the existing single-cluster Kubernetes APIs. Initially released as part of Kubernetes 1.3, Cluster Federation has implemented parts of the existing “single-cluster” Kubernetes API so that they may be used transparently in a multi-cluster fashion. As of Kubernetes 1.9, many of the non-Federated Kubernetes Workloads APIs have moved to GA (Deployments, ReplicaSets, Daemonset, StatefulSet). However, under Federation, these workloads have not reached the maturity of “GA” since they are re-implemented by different federated controllers. The SIG is currently re-thinking how to support Kubernetes APIs in a Federation fashion and this discussion is reflected under Kubefed.
-
-|  |  |
-| -------------- |:-------|
-| Recommended for Production | No. Between Alpha and Beta levels of functionality depending on Kubernetes APIs used. |
-| General Availability | No target set date. |
-| Current Level of Activity | On Hold. See Kubefed. |
-| Owner(s) | [@shashidharatd](https://github.com/shashidharatd) |
-| Where to find it? | Out of main Kubernetes repository as of 1.9 and into its own [kubernetes/federation](https://github.com/kubernetes/federation) repository (kubefed is no longer distributed as part of Kubernetes client tools). Users have to build their own Federation Control Plane and kubefed client tool or wait on [issue #192](https://github.com/kubernetes/federation/issues/192) to be resolved. |
 <!-- END CUSTOM CONTENT -->

sig-multicluster/annual-report-2024.md

@@ -4,39 +4,59 @@
 
 1. What work did the SIG do this year that should be highlighted?
 
-<!--
-   Some example items that might be worth highlighting:
-   - Major KEP advancement
-   - Important initiatives that aren't tracked via KEPs
-   - Paying down significant tech debt
-   - Governance and leadership changes
--->
+Stephen Kitt (@skitt) replaced Paul Morie (@pmorie) as SIG co-chair.
+
+Significant progress was made on graduating KEP 1645 to beta; the only
+remaining item is collapsing the ServiceImport spec and status fields
+to root, https://github.com/kubernetes-sigs/mcs-api/pull/52 or
+https://github.com/kubernetes-sigs/mcs-api/pull/85.
+
+A conformance suite for KEP 1645 has been implemented in
+https://github.com/kubernetes-sigs/mcs-api/tree/master/conformance
+
+CI for the mcs-api repository was revamped, with presubmit jobs added
+to test-infra: https://github.com/kubernetes/test-infra/pull/33393
+
+A lot of discussion happened around ClusterProfile credentials
+storage.
 
 2. Are there any areas and/or subprojects that your group needs help with (e.g. fewer than 2 active OWNERS)?
 
+No.
 
 3. Did you have community-wide updates in 2024 (e.g. KubeCon talks)?
 
-<!--
-  Examples include links to email, slides, or recordings.
--->
+* KubeCon EU
+  - SIG-Multicluster intro & deep dive:
+    https://www.youtube.com/watch?v=ZD2FzR_xFdk
+  - Introducing ClusterInventory and ClusterFeature API:
+    https://www.youtube.com/watch?v=Xt1cuHKjKg8
+* KubeCon China
+  - SIG-Multicluster intro & deep dive:
+    https://www.youtube.com/watch?v=7cqO8t7O7Lk
+  - Developing a standard multi-cluster inventory API:
+    https://www.youtube.com/watch?v=fJi6rIYoUwY
+  - Connecting the dots: towards a unified multi-cluster AI/ML
+    experience: https://www.youtube.com/watch?v=BnC-DrnME0E
+* KubeCon NA
+  - SIG-Multicluster intro & deep dive:
+    https://www.youtube.com/watch?v=6nuCNCK_sdA
+  - One inventory to rule them all: standardizing multicluster
+    management: https://www.youtube.com/watch?v=6c8Rh_vrIA4
 
 4. KEP work in 2024 (v1.30, v1.31, v1.32):
-<!--
-   TODO: Uncomment the following auto-generated list of KEPs, once reviewed & updated for correction.
 
-   Note: This list is generated from the KEP metadata in kubernetes/enhancements repository.
-      If you find any discrepancy in the generated list here, please check the KEP metadata.
-      Please raise an issue in kubernetes/community, if the KEP metadata is correct but the generated list is incorrect.
--->
+Our KEPs aren’t tied to Kubernetes releases. This year saw the
+following work merged:
 
-<!-- 
-
- -->
+* Label sync added to KEP 1645:
+  https://github.com/kubernetes/enhancements/pull/4922
+* KEP 4322 renamed to “ClusterProfile API”
+* Relationship between ClusterProfile, ClusterSet and cluster
+  inventory clarified in KEP 4322
 
 ## [Subprojects](https://git.k8s.io/community/sig-multicluster#subprojects)
 
-
 **Continuing:**
   - about-api
   - cluster-inventory-api
@@ -46,19 +66,16 @@
 
 ## [Working groups](https://git.k8s.io/community/sig-multicluster#working-groups)
 
-**Retired in 2024:**
- - IoT Edge
-**Continuing:**
- - Policy
+None currently. Last year’s annual report was incorrect.
 
 ## Operational
 
 Operational tasks in [sig-governance.md]:
-- [ ] [README.md] reviewed for accuracy and updated if needed
-- [ ] [CONTRIBUTING.md] reviewed for accuracy and updated if needed
-- [ ] Other contributing docs (e.g. in devel dir or contributor guide) reviewed for accuracy and updated if needed
-- [ ] Subprojects list and linked OWNERS files in [sigs.yaml] reviewed for accuracy and updated if needed
-- [ ] SIG leaders (chairs, tech leads, and subproject leads) in [sigs.yaml] are accurate and active, and updated if needed
+- [x] [README.md] reviewed for accuracy and updated if needed
+- [x] [CONTRIBUTING.md] reviewed for accuracy and updated if needed
+- [x] Other contributing docs (e.g. in devel dir or contributor guide) reviewed for accuracy and updated if needed
+- [x] Subprojects list and linked OWNERS files in [sigs.yaml] reviewed for accuracy and updated if needed
+- [x] SIG leaders (chairs, tech leads, and subproject leads) in [sigs.yaml] are accurate and active, and updated if needed
 - [ ] Meeting notes and recordings for 2024 are linked from [README.md] and updated/uploaded if needed