|
12 | 12 | - Governance and leadership changes
|
13 | 13 | -->
|
14 | 14 |
|
| 15 | +- No major SIG level KEPs. |
| 16 | +- No governance or leadership changes. |
| 17 | +- The SIG started participating in the cross-SIG WG etcd operator with SIG etcd. |
| 18 | +- We retired the inactive etcdadm and cluster-api-provider-nested subprojects. |
| 19 | +- kubeadm released v1beta4 and added phase support for `upgrade apply` phases. |
| 20 | +- minikube added support for multi-control plane clusters (HA) and improved the GPU support. |
| 21 | +- CAPI started work on v1beta2 and a new process for cluster Conditions. |
| 22 | +- kOps improved its Azure support and added the `reconcile` command to handle k8s skew issues. |
| 23 | +- kubespray added support for more Linux distributions and exposed more configuration options. |
| 24 | + |
15 | 25 | 2. Are there any areas and/or subprojects that your group needs help with (e.g. fewer than 2 active OWNERS)?
|
16 | 26 |
|
| 27 | +- In 2023 we collected a |
| 28 | +[subproject self-assessment](https://docs.google.com/forms/d/e/1FAIpQLSc0CqmfaOIK4bCbEDhh0qiF5wCHi6Uvy0uR_k8egOtafalpow/viewanalytics), |
| 29 | +which still has a valid list of areas that need help. |
| 30 | + |
| 31 | +The most common areas where we need help are: |
| 32 | +- Contributing to code |
| 33 | +- Reviewing code |
| 34 | + |
| 35 | +Subprojects that might need help with additional OWNERS, in no particular order, |
| 36 | +and maybe an incomplete list: |
| 37 | +- cluster-api |
| 38 | +- cluster-api-addon-provider-helm |
| 39 | +- cluster-api-ipam-provider-in-cluster |
| 40 | +- cluster-api-provider-aws |
| 41 | +- cluster-api-provider-gcp |
| 42 | +- cluster-api-provider-kubemark |
| 43 | +- cluster-api-provider-openstack |
| 44 | +- cluster-api-provider-packet |
| 45 | +- kubeadm |
| 46 | + |
| 47 | +We encourage contributors who are interested in our subprojects to reach out to the |
| 48 | +SIG mailing list or to individual subproject Slack channels. |
17 | 49 |
|
18 | 50 | 3. Did you have community-wide updates in 2024 (e.g. KubeCon talks)?
|
19 | 51 |
|
20 | 52 | <!--
|
21 | 53 | Examples include links to email, slides, or recordings.
|
22 | 54 | -->
|
23 | 55 |
|
| 56 | +KubeCon EU 2024: |
| 57 | +- [how-to-deploy-an-ai-optimized-k8s-cluster-with-kubespray](https://kccnceu2024.sched.com/event/1YhhP/how-to-deploy-an-ai-optimized-k8s-cluster-with-kubespray-kay-yan-daocloud-mohamed-zaian-new-work-se) |
| 58 | + |
| 59 | +KubeCon NA 2024: |
| 60 | +- [luster-api-deep-dive-roadmap-to-api-graduation](https://kccncna2024.sched.com/event/1howc/cluster-api-deep-dive-roadmap-to-api-graduation-christian-schlotter-broadcom-vince-prignano-apple) |
| 61 | +- [bare-metal-kubernetes-with-kops-gathering-community-wisdom](https://kccncna2024.sched.com/event/1howo/bare-metal-kubernetes-with-kops-gathering-community-wisdom-justin-santa-barbara-google-ciprian-hacman-microsoft) |
| 62 | + |
| 63 | +KubeCon China 2024: |
| 64 | +- [kubespray-unleashed-navigating-bare-metal-services](https://kccncossaidevchn2024.sched.com/event/1eYXD/kubespray-unleashed-navigating-bare-metal-services-in-kubernetes-for-llm-and-rag-kubespraydaepnanokubernetesllmreragzhu-ya-lie-shu-kay-yan-daocloud-alan-leung-equinix) |
| 65 | + |
24 | 66 | 4. KEP work in 2024 (v1.30, v1.31, v1.32):
|
25 | 67 | <!--
|
26 | 68 | TODO: Uncomment the following auto-generated list of KEPs, once reviewed & updated for correction.
|
|
30 | 72 | Please raise an issue in kubernetes/community, if the KEP metadata is correct but the generated list is incorrect.
|
31 | 73 | -->
|
32 | 74 |
|
33 |
| -<!-- |
| 75 | +<!-- |
34 | 76 | - Alpha
|
35 | 77 | - [4656 - Add kubelet instance configuration to configure CRI socket for each node](https://github.com/kubernetes/enhancements/tree/master/keps/sig-cluster-lifecycle/4656-add-kubelet-instance-configuration) - v1.32
|
36 | 78 |
|
37 | 79 | -->
|
38 | 80 |
|
| 81 | +While we have a few SIG level KEPs in `kubernetes/enhancements`, kubeadm is the only |
| 82 | +subproject that we have that is part of the Kubernetes release and more actively receives KEPs. |
| 83 | + |
| 84 | +In 2024 there were 2 new kubeadm KEPs: |
| 85 | +- [4471-cp-join-kubelet-local-apiserver](https://github.com/kubernetes/enhancements/tree/master/keps/sig-cluster-lifecycle/kubeadm/4471-cp-join-kubelet-local-apiserver) |
| 86 | +- [4656-add-kubelet-instance-configuration](https://github.com/kubernetes/enhancements/tree/master/keps/sig-cluster-lifecycle/kubeadm/4656-add-kubelet-instance-configuration) |
| 87 | + |
39 | 88 | ## [Subprojects](https://git.k8s.io/community/sig-cluster-lifecycle#subprojects)
|
40 | 89 |
|
41 | 90 |
|
|
77 | 126 | ## Operational
|
78 | 127 |
|
79 | 128 | Operational tasks in [sig-governance.md]:
|
80 |
| -- [ ] [README.md] reviewed for accuracy and updated if needed |
81 |
| -- [ ] [CONTRIBUTING.md] reviewed for accuracy and updated if needed |
82 |
| -- [ ] Other contributing docs (e.g. in devel dir or contributor guide) reviewed for accuracy and updated if needed |
83 |
| -- [ ] Subprojects list and linked OWNERS files in [sigs.yaml] reviewed for accuracy and updated if needed |
84 |
| -- [ ] SIG leaders (chairs, tech leads, and subproject leads) in [sigs.yaml] are accurate and active, and updated if needed |
85 |
| -- [ ] Meeting notes and recordings for 2024 are linked from [README.md] and updated/uploaded if needed |
| 129 | +- [x] [README.md] reviewed for accuracy and updated if needed |
| 130 | +- [x] [CONTRIBUTING.md] reviewed for accuracy and updated if needed |
| 131 | +- [x] Other contributing docs (e.g. in devel dir or contributor guide) reviewed for accuracy and updated if needed |
| 132 | +- [x] Subprojects list and linked OWNERS files in [sigs.yaml] reviewed for accuracy and updated if needed |
| 133 | +- [x] SIG leaders (chairs, tech leads, and subproject leads) in [sigs.yaml] are accurate and active, and updated if needed |
| 134 | +- [x] Meeting notes and recordings for 2024 are linked from [README.md] and updated/uploaded if needed |
86 | 135 |
|
87 | 136 |
|
88 | 137 | [CONTRIBUTING.md]: https://git.k8s.io/community/sig-cluster-lifecycle/CONTRIBUTING.md
|
|
0 commit comments