Merge branch 'kubernetes:master' into archive-meeting-notes

This commit is contained in:
Simon Fogliato 2025-01-16 10:47:44 -08:00 committed by GitHub
commit c7e933d40b
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
52 changed files with 2286 additions and 35 deletions

View File

@ -23,7 +23,7 @@ The [charter](https://git.k8s.io/steering/charter.md) defines the scope and gove
* Benjamin Elder (**[@BenTheElder](https://github.com/BenTheElder)**), Google
* Antonio Ojea (**[@aojea](https://github.com/aojea)**), Google
* Stephen Augustus (**[@justaugustus](https://github.com/justaugustus)**), Cisco
* Stephen Augustus (**[@justaugustus](https://github.com/justaugustus)**), Bloomberg L.P.
* Paco Xu 徐俊杰 (**[@pacoxu](https://github.com/pacoxu)**), DaoCloud
* Patrick Ohly (**[@pohly](https://github.com/pohly)**), Intel
* Sascha Grunert (**[@saschagrunert](https://github.com/saschagrunert)**), Red Hat

View File

@ -240,20 +240,22 @@ usergroups:
long_name: Cluster API Release Team
description: Members of the Cluster API Release Team
members:
- adilGhaffarDev
- AttyXY
- blind3dd
- cahillsf
- chandankumar4
- jayesh-srivastava
- pravarag
- rajankumary2k
- SD-13
- cprivitere
- hackeramitkumar
- mboersma
- mbrow137
- pratik-mahalle
- ramessesii2
- RansherSingh
- serngawy
- sivchari
- shecodesmagic
- sreeram-venkitesh
- Sunnatillo
- tasdikrahman
- tormath1
- varshasuryawanshi
- vishalanarase
- wendy-ha18
- name: kcp-devs
long_name: kcp Development Team

View File

@ -21,6 +21,7 @@ users:
aravindputrevu: U1G27SDU6
asmacdo: UNVH7RY9J
Atharva-Shinde: U028J67T478
AttyXY: U07KSK513NW
AvineshTripathi: U029U44P26B
bai: U4XAULHL3
Bart Farrell: U01DZM7PJDT
@ -29,6 +30,7 @@ users:
benoitf: UCQC3DNUA
bentheelder: U1P7T516X
bhumijgupta: U022JUBM3B4
blind3dd: UC7GPBQB1
briandealwis: UAZKM38JV
bubblemelon: U7K9C643G
byako: U03GZBD4J4C
@ -53,6 +55,7 @@ users:
cji: U5YSRC21J
clubanderson: U0462LN24QJ
cpanato: U8DFY4TTK
cprivitere: UEXCRF7EK
csams: U02B6A9GF55
Dave Smith-Uchida: UDZDED8G2
david-martin: ULMJ41U73
@ -164,6 +167,8 @@ users:
maysunfaisal: U01DEHK2YUB
mbbroberg: U18JTHMDY
mbianchidev: UU1JM5G5A
mboersma: U5PL62ULA
mbrow137: U07HN4TUNKS
mcbenjemaa: UF111SQ4U
meatballhat: U01QEKCBTBM
mehabhalodiya: U024HPAQDC1
@ -210,6 +215,7 @@ users:
pnbrown: U011JJTQVGF
pohly: U91901TMF
prajyot-parab: U02MVRCN8CX
pratik-mahalle: U06P66FAHPU
pravarag: UFA5V59J5
prietyc123: U01D4MBLM52
Priyankasaggu11929: U012EE74CU8
@ -219,7 +225,9 @@ users:
r-lawton: U019CNHR2E6
rajankumary2k: U011YM87GQK
rajula96reddy: U7K9EK1HC
ramessesii2: U0359S5LUDR
ramrodo: UU74ZC2RX
RansherSingh: U05MZREAE2Y
rashmigottipati: U013T1DD3PW
razashahid107: U05FB1L2YM8
reylejano: U01GDNJL5MW
@ -248,6 +256,7 @@ users:
sethmccombs: U92LLUZ8A
sgtcodfish: U01PQ8N3PM1
shamus: US7EUUBK8
shecodesmagic: U0592U4JQA3
shipra101: U06MJ9TT031
shubham-pampattiwar: U01QW84HBBN
simplytunde: UAY1NBYHE
@ -292,6 +301,7 @@ users:
Vyom-Yadav: U03658QBE1K
vzhukovs: U030TR1FG85
wallrj: U1ZMERJF7
wendy-ha18: U072Q1ZPVA7
willie-yao: U024EME7SQK
wilsonehusin: U0100068GF2
wurbanski: URX7CMK97

View File

@ -102,11 +102,13 @@ against the kubernetes/org repo, as above.
- Members can do `/lgtm` on open PRs.
- They can be assigned to issues and PRs, and people can ask members for reviews with a `/cc @username`.
- Tests can be run against their PRs automatically. No `/ok-to-test` needed.
- Members can do `/ok-to-test` for PRs that have a `needs-ok-to-test` label, and use commands like `/close` to close PRs as well.
- Members can do `/ok-to-test` for PRs that have a `needs-ok-to-test` label, and use commands like `/close` to close issues or PRs as well.
**Note:** members who frequently contribute code are expected to proactively
**Note:** Members who frequently contribute code are expected to proactively
perform code reviews and work towards becoming a primary *reviewer* for the
subproject that they are active in.
subproject that they are active in. Members who contribute to the Kubernetes documentation
can participate in the [pull request wrangler program](https://kubernetes.io/docs/contribute/participate/pr-wranglers/)
to cultivate a habit of [reviewing for approvers and reviewers](https://kubernetes.io/docs/contribute/review/for-approvers/).
## Reviewer
@ -127,7 +129,7 @@ addition to the assigned reviewers.
The following apply to the part of codebase for which one would be a reviewer in
an [OWNERS] file (for repos using the bot).
- member for at least 3 months
- Member for at least 3 months
- Primary reviewer for at least 5 PRs to the codebase
- Reviewed or merged at least 20 substantial PRs to the codebase
- Knowledgeable about the codebase

View File

@ -188,10 +188,10 @@ Image configuration files can further influence how FOCUS and SKIP match test ca
For example:
```sh
--focus="\[NodeFeature:.+\]" --skip="\[Flaky\]|\[Serial\]"
--focus="\[Feature:.+\]" --skip="\[Flaky\]|\[Serial\]"
```
runs all e2e tests labeled `"[NodeFeature:*]"` and will skip any tests labeled `"[Flaky]"` or `"[Serial]"`.
runs all e2e tests labeled `"[Feature:*]"` and will skip any tests labeled `"[Flaky]"` or `"[Serial]"`.
Two example e2e tests that match this expression are:
* https://github.com/kubernetes/kubernetes/blob/0e2220b4462130ae8a22ed657e8979f7844e22c1/test/e2e_node/security_context_test.go#L155
@ -235,7 +235,7 @@ To run a particular e2e test, simply pass the Grinkgo `It` string to the `--focu
For example, suppose we have the following test case: https://github.com/kubernetes/kubernetes/blob/0e2220b4462130ae8a22ed657e8979f7844e22c1/test/e2e_node/security_context_test.go#L175. We could select this test case by adding the argument:
```sh
--focus="should not show its pid in the non-hostpid containers \[NodeFeature:HostAccess\]"
--focus="should not show its pid in the non-hostpid containers \[Feature:HostAccess\]"
```
## Run all tests related to a feature
@ -243,7 +243,7 @@ For example, suppose we have the following test case: https://github.com/kuberne
In contrast, to run all node e2e tests related to the "HostAccess" feature one could run:
```sh
--focus="\[NodeFeature:HostAccess\]"
--focus="\[Feature:HostAccess\]"
```
## Run tests continually until they fail

View File

@ -0,0 +1,3 @@
approvers:
- jberkus
- soltysh

View File

@ -0,0 +1,6 @@
-------------------------------------------------------------
name: Christoph Blecker
ID: cblecker
-------------------------------------------------------------
# Christoph Blecker

View File

@ -0,0 +1,6 @@
-------------------------------------------------------------
name: Carlos Tadeu Panato Jr
ID: cpanato
-------------------------------------------------------------
# Carlos Tadeu Panato Jr

View File

@ -0,0 +1,6 @@
-------------------------------------------------------------
name: Davanum Srinivas
ID: dims
-------------------------------------------------------------
# Davanum Srinivas

View File

@ -0,0 +1,6 @@
-------------------------------------------------------------
name: Nikhita Raghunath
ID: nikhita
-------------------------------------------------------------
# Nikhita Raghunath

View File

@ -0,0 +1,13 @@
name: 2025 Kubernetes CNCF Governing Board Election
organization: Kubernetes
start_datetime: 2025-01-08 00:00:01
end_datetime: 2025-01-26 11:59:59
no_winners: 1
allow_no_opinion: False
delete_after: True
election_officers:
- soltysh
- jberkus
eligibility: Eligibility is limited to the [current Steering Committee Members](https://github.com/kubernetes/steering/tree/main?tab=readme-ov-file#members)
exception_description: No exception requests accepted for the GB election.
exception_due: 2025-01-26 00:00:01

View File

@ -0,0 +1,3 @@
# Vote for the Kubernetes CNCF GB Seat
Please complete your voting by the end of 1/26/2025.

View File

@ -0,0 +1,8 @@
eligible_voters:
- BenTheElder
- aojea
- justaugustus
- pacoxu
- pohly
- saschagrunert
- soltysh

View File

@ -78,7 +78,7 @@ drop GitHub issue templates into the `generator/generated/` directory.
You can generate the issues from these templates by running:
```bash
for i in $(ls -1 generator/generated/*.md); do hub issue create -F $i && rm $i; done
for i in $(ls -1 generator/generated/*.md); do gh issue create --repo kubernetes/community --title="$(head -n 1 $i)" --body-file $i && rm $i; done
```
You may run into rate limiting issues, which is why this command removes the

View File

@ -16,8 +16,8 @@ Actions for the chair/organizer of the community group:
Once all the above items are complete, this issue may be `/close`'d
Key dates:
- Initial PR to communtiy repo should be opened by May 1, {{now.UTC.Year}}
- PR should be reviewed and merged by May 22, {{now.UTC.Year}}
- Initial PR to community repo should be opened by February 14, {{now.UTC.Year}}
- PR should be reviewed and merged by February 28, {{now.UTC.Year}}
More detailed information on the annual reports process is available [here](https://git.k8s.io/community/committee-steering/governance/annual-reports.md).

View File

@ -54,11 +54,10 @@
## [Subprojects](https://git.k8s.io/community/{{.Dir}}#subprojects)
{{- define "subprojects" -}}
{{- $owningSIG := .Dir -}}
{{- if .New}}
**New in {{lastYear}}:**{{range .New}}
- [{{.}}](https://git.k8s.io/community/{{ $owningSIG }}#{{.}})
- {{.}}
{{- end}}
{{- end}}
@ -114,4 +113,4 @@ Operational tasks in [sig-governance.md]:
[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md
[README.md]: https://git.k8s.io/community/{{.Dir}}/README.md
[sigs.yaml]: https://git.k8s.io/community/sigs.yaml
[devel]: https://git.k8s.io/community/contributors/devel/README.md
[devel]: https://git.k8s.io/community/contributors/devel/README.md

View File

@ -0,0 +1,98 @@
# 2024 Annual Report: SIG API Machinery
## Current initiatives and Project Health
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
-->
2. Are there any areas and/or subprojects that your group needs help with (e.g. fewer than 2 active OWNERS)?
3. Did you have community-wide updates in 2024 (e.g. KubeCon talks)?
<!--
Examples include links to email, slides, or recordings.
-->
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.
-->
<!--
- Alpha
- [3962 - Mutating Admission Policies](https://github.com/kubernetes/enhancements/tree/master/keps/sig-api-machinery/3962-mutating-admission-policies) - v1.32
- [4222 - CBOR Serializer](https://github.com/kubernetes/enhancements/tree/master/keps/sig-api-machinery/4222-cbor-serializer) - v1.32
- [4346 - Add Informer Metrics](https://github.com/kubernetes/enhancements/tree/master/keps/sig-api-machinery/4346-informer-metrics) - v1.30
- [4355 - Coordinated Leader Election](https://github.com/kubernetes/enhancements/tree/master/keps/sig-api-machinery/4355-coordinated-leader-election) - v1.31
- [4460 - Enable per-request Read/Write Deadline](https://github.com/kubernetes/enhancements/tree/master/keps/sig-api-machinery/4460-per-request-deadline) - v1.31
- Beta
- [2339 - StorageVersion API for HA API servers](https://github.com/kubernetes/enhancements/tree/master/keps/sig-api-machinery/2339-storageversion-api-for-ha-api-servers) - v1.30
- [2340 - Consistent Reads from Cache](https://github.com/kubernetes/enhancements/tree/master/keps/sig-api-machinery/2340-Consistent-reads-from-cache) - v1.31
- [3157 - Allow informers for getting a stream of data instead of chunking](https://github.com/kubernetes/enhancements/tree/master/keps/sig-api-machinery/3157-watch-list) - v1.32
- [4008 - CRD Validation Ratcheting](https://github.com/kubernetes/enhancements/tree/master/keps/sig-api-machinery/4008-crd-ratcheting) - v1.30
- [4192 - Move Storage Version Migrator in-tree](https://github.com/kubernetes/enhancements/tree/master/keps/sig-api-machinery/4192-svm-in-tree) - v1.32
- [4568 - Resilient watchcache initialization](https://github.com/kubernetes/enhancements/tree/master/keps/sig-api-machinery/4568-resilient-watchcache-initialization) - v1.31
- Stable
- [3352 - Aggregated Discovery](https://github.com/kubernetes/enhancements/tree/master/keps/sig-api-machinery/3352-aggregated-discovery) - v1.30
- [3488 - CEL for Admission Control](https://github.com/kubernetes/enhancements/tree/master/keps/sig-api-machinery/3488-cel-admission-control) - 1.30
- [3716 - Admission Webhook Match Conditions](https://github.com/kubernetes/enhancements/tree/master/keps/sig-api-machinery/3716-admission-webhook-match-conditions) - v1.30
- [4006 - Transition from SPDY to Websockets](https://github.com/kubernetes/enhancements/tree/master/keps/sig-api-machinery/4006-transition-spdy-to-websockets) - v1.32
- [4020 - Unknown Version Interoperability Proxy](https://github.com/kubernetes/enhancements/tree/master/keps/sig-api-machinery/4020-unknown-version-interoperability-proxy) - v1.30
- [4358 - Custom Resource Field Selectors](https://github.com/kubernetes/enhancements/tree/master/keps/sig-api-machinery/4358-custom-resource-field-selectors) - v1.32
- [4420 - Retry Generate Name](https://github.com/kubernetes/enhancements/tree/master/keps/sig-api-machinery/4420-retry-generate-name) - v1.32 -->
## [Subprojects](https://git.k8s.io/community/sig-api-machinery#subprojects)
**Continuing:**
- cel-admission-webhook
- component-base
- control-plane-features
- idl-schema-client-pipeline
- json
- kubernetes-clients
- server-api-aggregation
- server-binaries
- server-crd
- server-frameworks
- server-sdk
- universal-machinery
- yaml
## [Working groups](https://git.k8s.io/community/sig-api-machinery#working-groups)
**Retired in 2024:**
- API Expression
**Continuing:**
- Structured Logging
## 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
- [ ] Meeting notes and recordings for 2024 are linked from [README.md] and updated/uploaded if needed
[CONTRIBUTING.md]: https://git.k8s.io/community/sig-api-machinery/CONTRIBUTING.md
[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md
[README.md]: https://git.k8s.io/community/sig-api-machinery/README.md
[sigs.yaml]: https://git.k8s.io/community/sigs.yaml
[devel]: https://git.k8s.io/community/contributors/devel/README.md

View File

@ -0,0 +1,87 @@
# 2024 Annual Report: SIG Apps
## Current initiatives and Project Health
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
-->
2. Are there any areas and/or subprojects that your group needs help with (e.g. fewer than 2 active OWNERS)?
3. Did you have community-wide updates in 2024 (e.g. KubeCon talks)?
<!--
Examples include links to email, slides, or recordings.
-->
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.
-->
<!--
- Alpha
- [3973 - Consider Terminating Pods in Deployments](https://github.com/kubernetes/enhancements/tree/master/keps/sig-apps/3973-consider-terminating-pods-deployment) - v1.32
- [4443 - More granular Job failure reasons for PodFailurePolicy](https://github.com/kubernetes/enhancements/tree/master/keps/sig-apps/4443-configurable-pod-failure-policy-reasons) - v1.31
- Beta
- [3998 - Job success/completion policy](https://github.com/kubernetes/enhancements/tree/master/keps/sig-apps/3998-job-success-completion-policy) - v1.31
- [4368 - Job API managed-by label](https://github.com/kubernetes/enhancements/tree/master/keps/sig-apps/4368-support-managed-by-for-batch-jobs) - v1.32
- Stable
- [1847 - Auto delete PVCs created by StatefulSet](https://github.com/kubernetes/enhancements/tree/master/keps/sig-apps/1847-autoremove-statefulset-pvcs) - v1.32
- [2185 - Random Pod Selection on ReplicaSet Downscale](https://github.com/kubernetes/enhancements/tree/master/keps/sig-apps/2185-random-pod-select-on-replicaset-downscale) - v1.31
- [3017 - Pod Healthy Policy for PDB](https://github.com/kubernetes/enhancements/tree/master/keps/sig-apps/3017-pod-healthy-policy-for-pdb) - v1.31
- [3329 - Retriable and non-retriable Pod failures for Jobs](https://github.com/kubernetes/enhancements/tree/master/keps/sig-apps/3329-retriable-and-non-retriable-failures) - v1.31
- [3335 - StatefulSet Slice](https://github.com/kubernetes/enhancements/tree/master/keps/sig-apps/3335-statefulset-slice) - v1.31
- [3715 - Elastic Indexed Job](https://github.com/kubernetes/enhancements/tree/master/keps/sig-apps/3715-elastic-indexed-job) - v1.31
- [4017 - Pod Index Label](https://github.com/kubernetes/enhancements/tree/master/keps/sig-apps/4017-pod-index-label) - v1.32
- [4026 - Add job creation timestamp to job annotations](https://github.com/kubernetes/enhancements/tree/master/keps/sig-apps/4026-crojob-scheduled-timestamp-annotation) - v1.32 -->
## [Subprojects](https://git.k8s.io/community/sig-apps#subprojects)
**New in 2024:**
- kjob
**Continuing:**
- application
- examples
- execution-hook
- kompose
- workloads-api
## [Working groups](https://git.k8s.io/community/sig-apps#working-groups)
**New in 2024:**
- Serving
**Continuing:**
- Batch
- Data Protection
## 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
- [ ] Meeting notes and recordings for 2024 are linked from [README.md] and updated/uploaded if needed
[CONTRIBUTING.md]: https://git.k8s.io/community/sig-apps/CONTRIBUTING.md
[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md
[README.md]: https://git.k8s.io/community/sig-apps/README.md
[sigs.yaml]: https://git.k8s.io/community/sigs.yaml
[devel]: https://git.k8s.io/community/contributors/devel/README.md

View File

@ -0,0 +1,82 @@
# 2024 Annual Report: SIG Architecture
## Current initiatives and Project Health
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
-->
2. Are there any areas and/or subprojects that your group needs help with (e.g. fewer than 2 active OWNERS)?
3. Did you have community-wide updates in 2024 (e.g. KubeCon talks)?
<!--
Examples include links to email, slides, or recordings.
-->
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.
-->
<!--
- Beta
- [4330 - Compatibility Versions](https://github.com/kubernetes/enhancements/tree/master/keps/sig-architecture/4330-compatibility-versions) - v1.32
- Stable
- [4402 - Go workspaces for k/k](https://github.com/kubernetes/enhancements/tree/master/keps/sig-architecture/4402-go-workspaces) - v1.30 -->
## [Subprojects](https://git.k8s.io/community/sig-architecture#subprojects)
**New in 2024:**
- apisnoop
- wg-device-management
- wg-serving
**Continuing:**
- architecture-and-api-governance
- code-organization
- conformance-definition
- enhancements
- production-readiness
## [Working groups](https://git.k8s.io/community/sig-architecture#working-groups)
**New in 2024:**
- Device Management
- Serving
**Retired in 2024:**
- API Expression
**Continuing:**
- LTS
- Policy
- Structured Logging
## 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
- [ ] Meeting notes and recordings for 2024 are linked from [README.md] and updated/uploaded if needed
[CONTRIBUTING.md]: https://git.k8s.io/community/sig-architecture/CONTRIBUTING.md
[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md
[README.md]: https://git.k8s.io/community/sig-architecture/README.md
[sigs.yaml]: https://git.k8s.io/community/sigs.yaml
[devel]: https://git.k8s.io/community/contributors/devel/README.md

View File

@ -0,0 +1,87 @@
# 2024 Annual Report: SIG Auth
## Current initiatives and Project Health
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
-->
2. Are there any areas and/or subprojects that your group needs help with (e.g. fewer than 2 active OWNERS)?
3. Did you have community-wide updates in 2024 (e.g. KubeCon talks)?
<!--
Examples include links to email, slides, or recordings.
-->
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.
-->
<!--
- Alpha
- [3926 - Handling undecryptable resources](https://github.com/kubernetes/enhancements/tree/master/keps/sig-auth/3926-handling-undecryptable-resources) - v1.32
- [4317 - Pod Certificates](https://github.com/kubernetes/enhancements/tree/master/keps/sig-auth/4317-pod-certificates) - v1.32
- [740 - Support external signing of service account tokens](https://github.com/kubernetes/enhancements/tree/master/keps/sig-auth/740-service-account-external-signing) - v1.32
- Beta
- [3331 - Structured authentication config](https://github.com/kubernetes/enhancements/tree/master/keps/sig-auth/3331-structured-authentication-configuration) - v1.30
- [4601 - Authorize with Selectors](https://github.com/kubernetes/enhancements/tree/master/keps/sig-auth/4601-authorize-with-selectors) - v1.32
- [4633 - Only allow anonymous auth for configured endpoints](https://github.com/kubernetes/enhancements/tree/master/keps/sig-auth/4633-anonymous-auth-configurable-endpoints) - v1.32
- Stable
- [2799 - Reduction of Secret-based Service Account Tokens](https://github.com/kubernetes/enhancements/tree/master/keps/sig-auth/2799-reduction-of-secret-based-service-account-token) - v1.30
- [3221 - Structured Authorization Configuration](https://github.com/kubernetes/enhancements/tree/master/keps/sig-auth/3221-structured-authorization-configuration) - v1.32
- [4193 - bound service account token improvements](https://github.com/kubernetes/enhancements/tree/master/keps/sig-auth/4193-bound-service-account-token-improvements) - v1.32 -->
## [Subprojects](https://git.k8s.io/community/sig-auth#subprojects)
**New in 2024:**
- secrets-store-sync-controller
**Continuing:**
- audit-logging
- authenticators
- authorizers
- certificates
- encryption-at-rest
- hierarchical-namespace-controller
- node-identity-and-isolation
- policy-management
- secrets-store-csi-driver
- service-accounts
- sig-auth-tools
## [Working groups](https://git.k8s.io/community/sig-auth#working-groups)
**Continuing:**
- Policy
## 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
- [ ] Meeting notes and recordings for 2024 are linked from [README.md] and updated/uploaded if needed
[CONTRIBUTING.md]: https://git.k8s.io/community/sig-auth/CONTRIBUTING.md
[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md
[README.md]: https://git.k8s.io/community/sig-auth/README.md
[sigs.yaml]: https://git.k8s.io/community/sigs.yaml
[devel]: https://git.k8s.io/community/contributors/devel/README.md

View File

@ -0,0 +1,72 @@
# 2024 Annual Report: SIG Autoscaling
## Current initiatives and Project Health
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
-->
2. Are there any areas and/or subprojects that your group needs help with (e.g. fewer than 2 active OWNERS)?
3. Did you have community-wide updates in 2024 (e.g. KubeCon talks)?
<!--
Examples include links to email, slides, or recordings.
-->
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.
-->
<!--
- Stable
- [1610 - Container Resource based Autoscaling](https://github.com/kubernetes/enhancements/tree/master/keps/sig-autoscaling/1610-container-resource-autoscaling) - v1.30 -->
## [Subprojects](https://git.k8s.io/community/sig-autoscaling#subprojects)
**Continuing:**
- addon-resizer
- cluster-autoscaler
- horizontal-pod-autoscaler
- karpenter
- vertical-pod-autoscaler
## [Working groups](https://git.k8s.io/community/sig-autoscaling#working-groups)
**New in 2024:**
- Device Management
- Serving
**Continuing:**
- Batch
## 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
- [ ] Meeting notes and recordings for 2024 are linked from [README.md] and updated/uploaded if needed
[CONTRIBUTING.md]: https://git.k8s.io/community/sig-autoscaling/CONTRIBUTING.md
[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md
[README.md]: https://git.k8s.io/community/sig-autoscaling/README.md
[sigs.yaml]: https://git.k8s.io/community/sigs.yaml
[devel]: https://git.k8s.io/community/contributors/devel/README.md

View File

@ -0,0 +1,78 @@
# 2024 Annual Report: SIG CLI
## Current initiatives and Project Health
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
-->
2. Are there any areas and/or subprojects that your group needs help with (e.g. fewer than 2 active OWNERS)?
3. Did you have community-wide updates in 2024 (e.g. KubeCon talks)?
<!--
Examples include links to email, slides, or recordings.
-->
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.
-->
<!--
- Alpha
- [3104 - Introduce kuberc](https://github.com/kubernetes/enhancements/tree/master/keps/sig-cli/3104-introduce-kuberc) - v1.32
- Stable
- [1441 - kubectl debug](https://github.com/kubernetes/enhancements/tree/master/keps/sig-cli/1441-kubectl-debug) - v1.30
- [3638 - Improve kubectl plugin resolution for non-shadowing subcommands](https://github.com/kubernetes/enhancements/tree/master/keps/sig-cli/3638-kubectl-plugin-subcommands) - v1.30
- [3805 - Kubectl Server-Side Apply by default](https://github.com/kubernetes/enhancements/tree/master/keps/sig-cli/3805-ssa-default) - v1.32
- [3895 - Interactive(-i) flag to kubectl delete for user confirmation](https://github.com/kubernetes/enhancements/tree/master/keps/sig-cli/3895-kubectl-delete-interactivity) - v1.30
- [4292 - Custom profiling support in kubectl debug command](https://github.com/kubernetes/enhancements/tree/master/keps/sig-cli/4292-kubectl-debug-custom-profile) - 1.32 -->
## [Subprojects](https://git.k8s.io/community/sig-cli#subprojects)
**Continuing:**
- cli-experimental
- cli-sdk
- cli-utils
- krew
- krew-index
- krm-functions
- kubectl
- kubectl-validate
- kui
- kustomize
## [Working groups](https://git.k8s.io/community/sig-cli#working-groups)
## 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
- [ ] Meeting notes and recordings for 2024 are linked from [README.md] and updated/uploaded if needed
[CONTRIBUTING.md]: https://git.k8s.io/community/sig-cli/CONTRIBUTING.md
[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md
[README.md]: https://git.k8s.io/community/sig-cli/README.md
[sigs.yaml]: https://git.k8s.io/community/sigs.yaml
[devel]: https://git.k8s.io/community/contributors/devel/README.md

View File

@ -0,0 +1,78 @@
# 2024 Annual Report: SIG Cloud Provider
## Current initiatives and Project Health
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
-->
2. Are there any areas and/or subprojects that your group needs help with (e.g. fewer than 2 active OWNERS)?
3. Did you have community-wide updates in 2024 (e.g. KubeCon talks)?
<!--
Examples include links to email, slides, or recordings.
-->
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.
-->
<!--
- Stable
- [2395 - Removing In-Tree Cloud Providers](https://github.com/kubernetes/enhancements/tree/master/keps/sig-cloud-provider/2395-removing-in-tree-cloud-providers) - v1.31 -->
## [Subprojects](https://git.k8s.io/community/sig-cloud-provider#subprojects)
**Retired in 2024:**
- provider-baiducloud
**Continuing:**
- cloud-provider-extraction-migration
- kubernetes-cloud-provider
- provider-alibaba-cloud
- provider-aws
- provider-azure
- provider-equinix-metal
- provider-gcp
- provider-huaweicloud
- provider-ibmcloud
- provider-oci
- provider-openstack
- provider-vsphere
## [Working groups](https://git.k8s.io/community/sig-cloud-provider#working-groups)
**Continuing:**
- Structured Logging
## 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
- [ ] Meeting notes and recordings for 2024 are linked from [README.md] and updated/uploaded if needed
[CONTRIBUTING.md]: https://git.k8s.io/community/sig-cloud-provider/CONTRIBUTING.md
[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md
[README.md]: https://git.k8s.io/community/sig-cloud-provider/README.md
[sigs.yaml]: https://git.k8s.io/community/sigs.yaml
[devel]: https://git.k8s.io/community/contributors/devel/README.md

View File

@ -0,0 +1,92 @@
# 2024 Annual Report: SIG Cluster Lifecycle
## Current initiatives and Project Health
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
-->
2. Are there any areas and/or subprojects that your group needs help with (e.g. fewer than 2 active OWNERS)?
3. Did you have community-wide updates in 2024 (e.g. KubeCon talks)?
<!--
Examples include links to email, slides, or recordings.
-->
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.
-->
<!--
- Alpha
- [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
-->
## [Subprojects](https://git.k8s.io/community/sig-cluster-lifecycle#subprojects)
**New in 2024:**
- karpenter-provider-cluster-api
**Retired in 2024:**
- etcdadm
- cluster-api-provider-nested
**Continuing:**
- cluster-addons
- cluster-api
- cluster-api-addon-provider-helm
- cluster-api-ipam-provider-in-cluster
- cluster-api-operator
- cluster-api-provider-aws
- cluster-api-provider-azure
- cluster-api-provider-cloudstack
- cluster-api-provider-digitalocean
- cluster-api-provider-gcp
- cluster-api-provider-ibmcloud
- cluster-api-provider-kubemark
- cluster-api-provider-kubevirt
- cluster-api-provider-openstack
- cluster-api-provider-packet
- cluster-api-provider-vsphere
- image-builder
- kOps
- kubeadm
- kubespray
- minikube
## [Working groups](https://git.k8s.io/community/sig-cluster-lifecycle#working-groups)
**New in 2024:**
- etcd Operator
**Continuing:**
- LTS
## 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
- [ ] Meeting notes and recordings for 2024 are linked from [README.md] and updated/uploaded if needed
[CONTRIBUTING.md]: https://git.k8s.io/community/sig-cluster-lifecycle/CONTRIBUTING.md
[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md
[README.md]: https://git.k8s.io/community/sig-cluster-lifecycle/README.md
[sigs.yaml]: https://git.k8s.io/community/sigs.yaml
[devel]: https://git.k8s.io/community/contributors/devel/README.md

View File

@ -0,0 +1,71 @@
# 2024 Annual Report: SIG Contributor Experience
## Current initiatives and Project Health
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
-->
2. Are there any areas and/or subprojects that your group needs help with (e.g. fewer than 2 active OWNERS)?
3. Did you have community-wide updates in 2024 (e.g. KubeCon talks)?
<!--
Examples include links to email, slides, or recordings.
-->
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.
-->
<!--
-->
## [Subprojects](https://git.k8s.io/community/sig-contributor-experience#subprojects)
**Continuing:**
- community
- community-management
- contributor-comms
- contributors-documentation
- devstats
- elections
- events
- github-management
- mentoring
- sigs-github-actions
- slack-infra
## [Working groups](https://git.k8s.io/community/sig-contributor-experience#working-groups)
## 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
- [ ] Meeting notes and recordings for 2024 are linked from [README.md] and updated/uploaded if needed
[CONTRIBUTING.md]: https://git.k8s.io/community/sig-contributor-experience/CONTRIBUTING.md
[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md
[README.md]: https://git.k8s.io/community/sig-contributor-experience/README.md
[sigs.yaml]: https://git.k8s.io/community/sigs.yaml
[devel]: https://git.k8s.io/community/contributors/devel/README.md

View File

@ -0,0 +1,64 @@
# 2024 Annual Report: SIG Docs
## Current initiatives and Project Health
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
-->
2. Are there any areas and/or subprojects that your group needs help with (e.g. fewer than 2 active OWNERS)?
3. Did you have community-wide updates in 2024 (e.g. KubeCon talks)?
<!--
Examples include links to email, slides, or recordings.
-->
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.
-->
<!--
-->
## [Subprojects](https://git.k8s.io/community/sig-docs#subprojects)
**Continuing:**
- kubernetes-blog
- localization
- reference-docs
- website
## [Working groups](https://git.k8s.io/community/sig-docs#working-groups)
## 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
- [ ] Meeting notes and recordings for 2024 are linked from [README.md] and updated/uploaded if needed
[CONTRIBUTING.md]: https://git.k8s.io/community/sig-docs/CONTRIBUTING.md
[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md
[README.md]: https://git.k8s.io/community/sig-docs/README.md
[sigs.yaml]: https://git.k8s.io/community/sigs.yaml
[devel]: https://git.k8s.io/community/contributors/devel/README.md

View File

@ -0,0 +1,81 @@
# 2024 Annual Report: SIG etcd
## Current initiatives and Project Health
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
-->
2. Are there any areas and/or subprojects that your group needs help with (e.g. fewer than 2 active OWNERS)?
3. Did you have community-wide updates in 2024 (e.g. KubeCon talks)?
<!--
Examples include links to email, slides, or recordings.
-->
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.
-->
<!--
-->
## [Subprojects](https://git.k8s.io/community/sig-etcd#subprojects)
**New in 2024:**
- auger
- etcd-manager
**Continuing:**
- bbolt
- cetcd
- dbtester
- discovery.etcd.io
- discoveryserver
- etcd
- etcd-play
- etcdlabs
- gofail
- govanityurls
- jetcd
- maintainers
- protodoc
- raft
- website
- zetcd
## [Working groups](https://git.k8s.io/community/sig-etcd#working-groups)
**New in 2024:**
- etcd Operator
## 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
- [ ] Meeting notes and recordings for 2024 are linked from [README.md] and updated/uploaded if needed
[CONTRIBUTING.md]: https://git.k8s.io/community/sig-etcd/CONTRIBUTING.md
[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md
[README.md]: https://git.k8s.io/community/sig-etcd/README.md
[sigs.yaml]: https://git.k8s.io/community/sigs.yaml
[devel]: https://git.k8s.io/community/contributors/devel/README.md

View File

@ -0,0 +1,84 @@
# 2024 Annual Report: SIG Instrumentation
## Current initiatives and Project Health
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
-->
2. Are there any areas and/or subprojects that your group needs help with (e.g. fewer than 2 active OWNERS)?
3. Did you have community-wide updates in 2024 (e.g. KubeCon talks)?
<!--
Examples include links to email, slides, or recordings.
-->
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.
-->
<!--
- Alpha
- [4827 - Component Statusz](https://github.com/kubernetes/enhancements/tree/master/keps/sig-instrumentation/4827-component-statusz) - v1.32
- [4828 - Component Flagz](https://github.com/kubernetes/enhancements/tree/master/keps/sig-instrumentation/4828-component-flagz) - v1.32
- Beta
- [3077 - Contextual logging](https://github.com/kubernetes/enhancements/tree/master/keps/sig-instrumentation/3077-contextual-logging) - v1.30
- Stable
- [2305 - Dynamic Cardinality Enforcement](https://github.com/kubernetes/enhancements/tree/master/keps/sig-instrumentation/2305-metrics-cardinality-enforcement) - v1.30
- [647 - APIServer Tracing](https://github.com/kubernetes/enhancements/tree/master/keps/sig-instrumentation/647-apiserver-tracing) - v1.30 -->
## [Subprojects](https://git.k8s.io/community/sig-instrumentation#subprojects)
**Continuing:**
- custom-metrics-apiserver
- instrumentation
- instrumentation-addons
- instrumentation-tools
- klog
- kube-state-metrics
- metric-stability-framework
- metrics
- metrics-server
- prometheus-adapter
- structured-logging
- usage-metrics-collector
## [Working groups](https://git.k8s.io/community/sig-instrumentation#working-groups)
**New in 2024:**
- Serving
**Continuing:**
- Structured Logging
## 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
- [ ] Meeting notes and recordings for 2024 are linked from [README.md] and updated/uploaded if needed
[CONTRIBUTING.md]: https://git.k8s.io/community/sig-instrumentation/CONTRIBUTING.md
[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md
[README.md]: https://git.k8s.io/community/sig-instrumentation/README.md
[sigs.yaml]: https://git.k8s.io/community/sigs.yaml
[devel]: https://git.k8s.io/community/contributors/devel/README.md

View File

@ -0,0 +1,68 @@
# 2024 Annual Report: SIG K8s Infra
## Current initiatives and Project Health
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
-->
2. Are there any areas and/or subprojects that your group needs help with (e.g. fewer than 2 active OWNERS)?
3. Did you have community-wide updates in 2024 (e.g. KubeCon talks)?
<!--
Examples include links to email, slides, or recordings.
-->
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.
-->
<!--
-->
## [Subprojects](https://git.k8s.io/community/sig-k8s-infra#subprojects)
**Continuing:**
- community-images
- k8s-infra-dns
- k8s-infra-groups
- k8s.io
- porche
- registry.k8s.io
## [Working groups](https://git.k8s.io/community/sig-k8s-infra#working-groups)
**Continuing:**
- LTS
## 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
- [ ] Meeting notes and recordings for 2024 are linked from [README.md] and updated/uploaded if needed
[CONTRIBUTING.md]: https://git.k8s.io/community/sig-k8s-infra/CONTRIBUTING.md
[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md
[README.md]: https://git.k8s.io/community/sig-k8s-infra/README.md
[sigs.yaml]: https://git.k8s.io/community/sigs.yaml
[devel]: https://git.k8s.io/community/contributors/devel/README.md

View File

@ -48,7 +48,7 @@ When the need arises, a [new SIG can be created](sig-wg-lifecycle.md)
|[Multicluster](sig-multicluster/README.md)|[multicluster](https://github.com/kubernetes/kubernetes/labels/sig%2Fmulticluster)|* [Jeremy Olmsted-Thompson](https://github.com/jeremyot), Google<br>* [Stephen Kitt](https://github.com/skitt), Red Hat<br>|* [Slack](https://kubernetes.slack.com/messages/sig-multicluster)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-multicluster)|* Regular SIG Meeting: [Tuesdays at 9:30 PT (Pacific Time) (bi-weekly)](https://zoom.us/my/k8s.mc)<br>
|[Network](sig-network/README.md)|[network](https://github.com/kubernetes/kubernetes/labels/sig%2Fnetwork)|* [Michael Zappa](https://github.com/mikezappa87), Microsoft<br>* [Shane Utt](https://github.com/shaneutt), Red Hat<br>* [Tim Hockin](https://github.com/thockin), Google<br>|* [Slack](https://kubernetes.slack.com/messages/sig-network)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-network)|* Gateway API Meeting (Americas): [Mondays at 15:00 PT (Pacific Time) (weekly)](https://zoom.us/j/441530404)<br>* Gateway API Meeting (Europe): [Tuesday (starting September 10th 2024)s at 08:00 PT (Pacific Time) (monthly)](https://zoom.us/j/441530404)<br>* Network Policy API Meeting: [Tuesdays at 9:00 PT (Pacific Time) (bi-weekly)](https://zoom.us/j/96264742248)<br>* SIG Network Ingress NGINX Meeting: [Thursdays at 8:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/98377891310)<br>* SIG Network Meeting: [Thursdays at 09:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/361123509)<br>* SIG Network Multi-Network Meeting: [Wednesdays at 08:00 PT (Pacific Time) (weekly)](https://zoom.us/j/95680858961?pwd=M1c2TTdMZHpMUUtIYXRpbjRobkNJZz09)<br>
|[Node](sig-node/README.md)|[node](https://github.com/kubernetes/kubernetes/labels/sig%2Fnode)|* [Sergey Kanzhelev](https://github.com/SergeyKanzhelev), Google<br>* [Peter Hunt](https://github.com/haircommander), Red Hat<br>* [Mrunal Patel](https://github.com/mrunalp), Red Hat<br>|* [Slack](https://kubernetes.slack.com/messages/sig-node)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-node)|* Main SIG Meeting: [Tuesdays at 10:00 PT (Pacific Time) (weekly)](https://zoom.us/j/4799874685)<br>* Weekly CI/Triage Meeting: [Wednesdays at 10:00 PT (Pacific Time) (weekly)](https://zoom.us/j/4799874685)<br>
|[Release](sig-release/README.md)|[release](https://github.com/kubernetes/kubernetes/labels/sig%2Frelease)|* [Jeremy Rickard](https://github.com/jeremyrickard), Microsoft<br>* [Stephen Augustus](https://github.com/justaugustus), Cisco<br>* [Sascha Grunert](https://github.com/saschagrunert), Red Hat<br>|* [Slack](https://kubernetes.slack.com/messages/sig-release)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-release)|* Regular SIG Meeting APAC/EU Oriented Time: [Tuesdays at 14:30 UTC (biweekly)](https://zoom.us/j/327142148?pwd=RE9aZWtCc0hhOWs4ZTdXZ0hBM0ROdz09)<br>* Regular SIG Meeting US Oriented Time: [Tuesdays at 17:00 UTC (biweekly)](https://zoom.us/j/327142148?pwd=RE9aZWtCc0hhOWs4ZTdXZ0hBM0ROdz09)<br>
|[Release](sig-release/README.md)|[release](https://github.com/kubernetes/kubernetes/labels/sig%2Frelease)|* [Jeremy Rickard](https://github.com/jeremyrickard), Microsoft<br>* [Stephen Augustus](https://github.com/justaugustus), Bloomberg L.P.<br>* [Sascha Grunert](https://github.com/saschagrunert), Red Hat<br>|* [Slack](https://kubernetes.slack.com/messages/sig-release)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-release)|* Regular SIG Meeting APAC/EU Oriented Time: [Tuesdays at 14:30 UTC (biweekly)](https://zoom.us/j/327142148?pwd=RE9aZWtCc0hhOWs4ZTdXZ0hBM0ROdz09)<br>* Regular SIG Meeting US Oriented Time: [Tuesdays at 17:00 UTC (biweekly)](https://zoom.us/j/327142148?pwd=RE9aZWtCc0hhOWs4ZTdXZ0hBM0ROdz09)<br>
|[Scalability](sig-scalability/README.md)|[scalability](https://github.com/kubernetes/kubernetes/labels/sig%2Fscalability)|* [Marcel Zieba](https://github.com/marseel), Isovalent<br>* [Shyam Jeedigunta](https://github.com/shyamjvs), Amazon<br>|* [Slack](https://kubernetes.slack.com/messages/sig-scalability)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-scale)|* Regular SIG Meeting: [Thursdays at 10:30 PT (Pacific Time) (bi-weekly ([upcoming meeting dates](#upcoming-meeting-dates)))](https://zoom.us/j/94252896018?pwd=cTlMMlBoTHZqUEdjRm9VY2NWNUg5dz09)<br>
|[Scheduling](sig-scheduling/README.md)|[scheduling](https://github.com/kubernetes/kubernetes/labels/sig%2Fscheduling)|* [Wei Huang](https://github.com/Huang-Wei), Apple<br>* [Abdullah Gharaibeh](https://github.com/ahg-g), Google<br>|* [Slack](https://kubernetes.slack.com/messages/sig-scheduling)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-scheduling)|* biweekly meeting (NA & Europe): [Thursdays at 17:00 UTC (biweekly starting Thursday June 7, 2018)](https://zoom.us/j/841218129)<br>* descheduler biweekly meeting Europe time: [Tuesdays at 14:30 CET (biweekly starting Tuesday Feb 27, 2024)](https://zoom.us/j/841218129)<br>* descheduler biweekly meeting North America time: [Tuesdays at 19:30 CET (biweekly starting Tuesday March 12, 2024)](https://zoom.us/j/841218129)<br>
|[Security](sig-security/README.md)|[security](https://github.com/kubernetes/kubernetes/labels/sig%2Fsecurity)|* [Ian Coldwater](https://github.com/IanColdwater), Docker<br>* [Cailyn Edwards](https://github.com/cailyn-codes), Okta<br>* [Tabitha Sable](https://github.com/tabbysable), Datadog<br>|* [Slack](https://kubernetes.slack.com/messages/sig-security)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-security)|* Regular SIG Meeting: [Fridays at 8:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/9934z1184192?pwd=L25Tc0ZOL3FqU09KNERlTU12dFhTQT09)<br>
@ -68,7 +68,7 @@ When the need arises, a [new SIG can be created](sig-wg-lifecycle.md)
|[LTS](wg-lts/README.md)|[lts](https://github.com/kubernetes/kubernetes/labels/wg%2Flts)|* Architecture<br>* Cluster Lifecycle<br>* K8s Infra<br>* Release<br>* Security<br>* Testing<br>|* [Jeremy Rickard](https://github.com/jeremyrickard), Microsoft<br>* [Jordan Liggitt](https://github.com/liggitt), Google<br>* [Micah Hausler](https://github.com/micahhausler), Amazon<br>|* [Slack](https://kubernetes.slack.com/messages/wg-lts)<br>* [Mailing List](https://groups.google.com/a/kubernetes.io/g/wg-lts)|* Regular WG Meeting: [Tuesdays at 07:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/92480197536?pwd=dmtSMGJRQmNYYTIyZkFlQ25JRngrdz09)<br>
|[Policy](wg-policy/README.md)|[policy](https://github.com/kubernetes/kubernetes/labels/wg%2Fpolicy)|* Architecture<br>* Auth<br>* Multicluster<br>* Network<br>* Node<br>* Scheduling<br>* Storage<br>|* [Jim Bugwadia](https://github.com/JimBugwadia), Kyverno/Nirmata<br>* [Poonam Lamba](https://github.com/poonam-lamba), Google<br>* [Andy Suderman](https://github.com/sudermanjr), Fairwinds<br>|* [Slack](https://kubernetes.slack.com/messages/wg-policy)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-wg-policy)|* Regular WG Meeting: [Wednesdays at 8:00 PT (Pacific Time) (semimonthly)](https://zoom.us/j/7375677271)<br>
|[Serving](wg-serving/README.md)|[serving](https://github.com/kubernetes/kubernetes/labels/wg%2Fserving)|* Apps<br>* Architecture<br>* Autoscaling<br>* Instrumentation<br>* Network<br>* Node<br>* Scheduling<br>* Storage<br>|* [Eduardo Arango](https://github.com/ArangoGutierrez), NVIDIA<br>* [Jiaxin Shan](https://github.com/Jeffwan), Bytedance<br>* [Sergey Kanzhelev](https://github.com/SergeyKanzhelev), Google<br>* [Yuan Tang](https://github.com/terrytangyuan), Red Hat<br>|* [Slack](https://kubernetes.slack.com/messages/wg-serving)<br>* [Mailing List](https://groups.google.com/a/kubernetes.io/g/wg-serving)|* WG Serving Weekly Meeting ([calendar](https://calendar.google.com/calendar/embed?src=e896b769743f3877edfab2d4c6a14132b2aa53287021e9bbf113cab676da54ba%40group.calendar.google.com)): [Wednesdays at 9:00 PT (Pacific Time) (weekly)](https://zoom.us/j/92615874244?pwd=VGhxZlJjRTNRWTZIS0dQV2MrZUJ5dz09)<br>
|[Structured Logging](wg-structured-logging/README.md)|[structured-logging](https://github.com/kubernetes/kubernetes/labels/wg%2Fstructured-logging)|* API Machinery<br>* Architecture<br>* Cloud Provider<br>* Instrumentation<br>* Network<br>* Node<br>* Scheduling<br>* Storage<br>|* [Mengjiao Liu](https://github.com/mengjiao-liu), DaoCloud<br>* [Patrick Ohly](https://github.com/pohly), Intel<br>|* [Slack](https://kubernetes.slack.com/messages/wg-structured-logging)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-wg-structured-logging)|
|[Structured Logging](wg-structured-logging/README.md)|[structured-logging](https://github.com/kubernetes/kubernetes/labels/wg%2Fstructured-logging)|* API Machinery<br>* Architecture<br>* Cloud Provider<br>* Instrumentation<br>* Network<br>* Node<br>* Scheduling<br>* Storage<br>|* [Mengjiao Liu](https://github.com/mengjiao-liu), Independent<br>* [Patrick Ohly](https://github.com/pohly), Intel<br>|* [Slack](https://kubernetes.slack.com/messages/wg-structured-logging)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-wg-structured-logging)|
### Committees
@ -76,7 +76,7 @@ When the need arises, a [new SIG can be created](sig-wg-lifecycle.md)
|------|--------|---------|---------|
|[Code of Conduct](committee-code-of-conduct/README.md)|[code-of-conduct](https://github.com/kubernetes/kubernetes/labels/committee%2Fcode-of-conduct)|* [Ana Margarita Medina](https://github.com/AnaMMedina21), Lightstep<br>* [Danielle Lancashire](https://github.com/endocrimes), Independent<br>* [Hilliary Lipsig](https://github.com/hlipsig), Red Hat<br>* [Jeremy Rickard](https://github.com/jeremyrickard), Microsoft<br>* [Xander Grzywinski](https://github.com/salaxander), Defense Unicorns<br>|* [Slack](https://kubernetes.slack.com/messages/code-of-conduct)<br>* [Private Mailing List](conduct@kubernetes.io)
|[Security Response](committee-security-response/README.md)|[security-response](https://github.com/kubernetes/kubernetes/labels/committee%2Fsecurity-response)|* [Sri Saran Balaji](https://github.com/SaranBalaji90), Amazon<br>* [CJ Cullen](https://github.com/cjcullen), Google<br>* [Craig Ingram](https://github.com/cji), Google<br>* [Mo Khan](https://github.com/enj), Microsoft<br>* [Joel Smith](https://github.com/joelsmith), Red Hat<br>* [Micah Hausler](https://github.com/micahhausler), Amazon<br>* [Rita Zhang](https://github.com/ritazh), Microsoft<br>* [Tabitha Sable](https://github.com/tabbysable), Datadog<br>|* [Private Mailing List](security@kubernetes.io)
|[Steering](committee-steering/README.md)|[steering](https://github.com/kubernetes/kubernetes/labels/committee%2Fsteering)|* [Benjamin Elder](https://github.com/BenTheElder), Google<br>* [Antonio Ojea](https://github.com/aojea), Google<br>* [Stephen Augustus](https://github.com/justaugustus), Cisco<br>* [Paco Xu 徐俊杰](https://github.com/pacoxu), DaoCloud<br>* [Patrick Ohly](https://github.com/pohly), Intel<br>* [Sascha Grunert](https://github.com/saschagrunert), Red Hat<br>* [Maciej Szulik](https://github.com/soltysh), Defense Unicorns<br>|* [Slack](https://kubernetes.slack.com/messages/steering-committee)<br>* [Mailing List](https://groups.google.com/a/kubernetes.io/forum/#!forum/steering)<br>* [Private Mailing List](steering-private@kubernetes.io)
|[Steering](committee-steering/README.md)|[steering](https://github.com/kubernetes/kubernetes/labels/committee%2Fsteering)|* [Benjamin Elder](https://github.com/BenTheElder), Google<br>* [Antonio Ojea](https://github.com/aojea), Google<br>* [Stephen Augustus](https://github.com/justaugustus), Bloomberg L.P.<br>* [Paco Xu 徐俊杰](https://github.com/pacoxu), DaoCloud<br>* [Patrick Ohly](https://github.com/pohly), Intel<br>* [Sascha Grunert](https://github.com/saschagrunert), Red Hat<br>* [Maciej Szulik](https://github.com/soltysh), Defense Unicorns<br>|* [Slack](https://kubernetes.slack.com/messages/steering-committee)<br>* [Mailing List](https://groups.google.com/a/kubernetes.io/forum/#!forum/steering)<br>* [Private Mailing List](steering-private@kubernetes.io)
<!-- BEGIN CUSTOM CONTENT -->
<!-- END CUSTOM CONTENT -->

View File

@ -0,0 +1,69 @@
# 2024 Annual Report: SIG Multicluster
## Current initiatives and Project Health
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
-->
2. Are there any areas and/or subprojects that your group needs help with (e.g. fewer than 2 active OWNERS)?
3. Did you have community-wide updates in 2024 (e.g. KubeCon talks)?
<!--
Examples include links to email, slides, or recordings.
-->
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.
-->
<!--
-->
## [Subprojects](https://git.k8s.io/community/sig-multicluster#subprojects)
**Continuing:**
- about-api
- cluster-inventory-api
- mcs-api
- sig-multicluster-site
- work-api
## [Working groups](https://git.k8s.io/community/sig-multicluster#working-groups)
**Retired in 2024:**
- IoT Edge
**Continuing:**
- Policy
## 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
- [ ] Meeting notes and recordings for 2024 are linked from [README.md] and updated/uploaded if needed
[CONTRIBUTING.md]: https://git.k8s.io/community/sig-multicluster/CONTRIBUTING.md
[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md
[README.md]: https://git.k8s.io/community/sig-multicluster/README.md
[sigs.yaml]: https://git.k8s.io/community/sigs.yaml
[devel]: https://git.k8s.io/community/contributors/devel/README.md

View File

@ -0,0 +1,99 @@
# 2024 Annual Report: SIG Network
## Current initiatives and Project Health
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
-->
2. Are there any areas and/or subprojects that your group needs help with (e.g. fewer than 2 active OWNERS)?
3. Did you have community-wide updates in 2024 (e.g. KubeCon talks)?
<!--
Examples include links to email, slides, or recordings.
-->
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.
-->
<!--
- Alpha
- [4427 - Relaxed DNS search string validation](https://github.com/kubernetes/enhancements/tree/master/keps/sig-network/4427-relaxed-dns-search-validation) - v1.32
- [784 - Kube Proxy component configuration updates and graduation](https://github.com/kubernetes/enhancements/tree/master/keps/sig-network/784-kube-proxy-component-config) - v1.32
- Beta
- [1880 - Multiple Service CIDRs](https://github.com/kubernetes/enhancements/tree/master/keps/sig-network/1880-multiple-service-cidrs) - v1.31
- [3866 - Add an nftables-based kube-proxy backend](https://github.com/kubernetes/enhancements/tree/master/keps/sig-network/3866-nftables-proxy) - v1.31
- [4444 - Traffic Distribution for Services](https://github.com/kubernetes/enhancements/tree/master/keps/sig-network/4444-service-traffic-distribution) - v1.31
- Stable
- [1860 - Make Kubernetes aware of the load balancer behaviour](https://github.com/kubernetes/enhancements/tree/master/keps/sig-network/1860-kube-proxy-IP-node-binding) - v1.32
- [2433 - Topology Aware Hints](https://github.com/kubernetes/enhancements/tree/master/keps/sig-network/2433-topology-aware-hints) - v1.30
- [2681 - Field status.hostIPs added for Pod](https://github.com/kubernetes/enhancements/tree/master/keps/sig-network/2681-pod-host-ip) - v1.30
- [3458 - Remove transient node predicates from KCCM's service controller](https://github.com/kubernetes/enhancements/tree/master/keps/sig-network/3458-remove-transient-node-predicates-from-service-controller) - v1.30
- [3705 - Cloud Dual-Stack --node-ip Handling](https://github.com/kubernetes/enhancements/tree/master/keps/sig-network/3705-cloud-node-ips) - v1.30
- [3836 - Kube-proxy improved ingress connectivity reliability](https://github.com/kubernetes/enhancements/tree/master/keps/sig-network/3836-kube-proxy-improved-ingress-connectivity-reliability) - v1.31 -->
## [Subprojects](https://git.k8s.io/community/sig-network#subprojects)
**New in 2024:**
- gateway-api-inference-extension
- ingate
- knftables
- multi-network
- node-ipam-controller
**Retired in 2024:**
- kpng
**Continuing:**
- cluster-proportional-autoscaler
- cluster-proportional-vertical-autoscaler
- external-dns
- gateway-api
- ingress
- iptables-wrappers
- kube-dns
- network-policy
- pod-networking
## [Working groups](https://git.k8s.io/community/sig-network#working-groups)
**New in 2024:**
- Device Management
- Serving
**Retired in 2024:**
- IoT Edge
**Continuing:**
- Policy
- Structured Logging
## 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
- [ ] Meeting notes and recordings for 2024 are linked from [README.md] and updated/uploaded if needed
[CONTRIBUTING.md]: https://git.k8s.io/community/sig-network/CONTRIBUTING.md
[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md
[README.md]: https://git.k8s.io/community/sig-network/README.md
[sigs.yaml]: https://git.k8s.io/community/sigs.yaml
[devel]: https://git.k8s.io/community/contributors/devel/README.md

View File

@ -0,0 +1,123 @@
# 2024 Annual Report: SIG Node
## Current initiatives and Project Health
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
-->
2. Are there any areas and/or subprojects that your group needs help with (e.g. fewer than 2 active OWNERS)?
3. Did you have community-wide updates in 2024 (e.g. KubeCon talks)?
<!--
Examples include links to email, slides, or recordings.
-->
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.
-->
<!--
- Alpha
- [2535 - Ensure Secret Pulled Images](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/2535-ensure-secret-pulled-images) - v1.32
- [2837 - KEP Template](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/2837-pod-level-resource-spec) - v1.32
- [2862 - Fine grained Kubelet API authorization](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/2862-fine-grained-kubelet-authz) - v1.32
- [3288 - Split Stdout and Stderr Log Stream of Container](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/3288-separate-stdout-from-stderr) - v1.32
- [3619 - Fine grained SupplementalGroups control](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/3619-supplemental-groups-policy) - v1.31
- [4205 - PSI based Node Conditions](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/4205-psi-metric) - v1.32
- [4438 - Restarting sidecar containers during Pod termination](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/4438-container-restart-termination) - v1.32
- [4540 - Add CPUManager policy option to restrict reservedSystemCPUs to system daemons and interrupt processing](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/4540-strict-cpu-reservation) - v1.32
- [4580 - Deprecate & remove Kubelet RunOnce mode](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/4580-deprecate-kubelet-runonce) - v1.31
- [4603 - Tune Crashloop Backoff](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/4603-tune-crashloopbackoff) - v1.32
- [4680 - Add Resource Health Status to the Pod Status for Device Plugin and DRA](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/4680-add-resource-health-to-pod-status) - v1.31
- [4800 - Split UnCoreCache Toplogy Awareness in CPU Manager](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/4800-cpumanager-split-uncorecache) - v1.32
- [4815 - DRA Partitionable Devices](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/4815-dra-partitionable-devices) - v1.32
- [4817 - Resource Claim Status With Possible Standardized Network Interface Data](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/4817-resource-claim-device-status) - v1.32
- [4818 - Allow zero value for Sleep Action of PreStop Hook](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/4818-allow-zero-value-for-sleep-action-of-prestop-hook) - v1.32
- Beta
- [1029 - Quotas for Ephemeral Storage](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/1029-ephemeral-storage-quotas) - 1.31
- [127 - Support User Namespaces](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/127-user-namespaces) - v1.30
- [1287 - In-place Update of Pod Resources](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/1287-in-place-update-pod-resources) - v1.32
- [2008 - Forensic Container Checkpointing](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/2008-forensic-container-checkpointing) - v1.30
- [2400 - Node system swap support](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/2400-node-swap) - v1.30
- [3857 - Recursive read-only mounts](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/3857-rro-mounts) - v1.31
- [3983 - Add support for a kubelet drop-in configuration directory](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/3983-drop-in-configuration) - v1.31
- [4033 - Discover cgroup driver from CRI](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/4033-group-driver-detection-over-cri) - v1.31
- [4176 - New CPUManager Static Policy which spread hyperthreads across physical CPUs to better utilize CPU Cache](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/4176-cpumanager-spread-cpus-preferred-policy) - v1.31
- [4191 - Split Image Filesystem](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/4191-split-image-filesystem) - v1.31
- [4210 - ImageMaximumGCAge in Kubelet](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/4210-max-image-gc-age) - v1.30
- [4216 - Image pull per runtime class](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/4216-image-pull-per-runtime-class) - v1.31
- [4265 - Add ProcMount option](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/4265-proc-mount) - v1.31
- [4369 - Allow special characters environment variable](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/4369-allow-special-characters-environment-variable) - v1.32
- [4381 - DRA Structured Parameters](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/4381-dra-structured-parameters) - v1.32
- [4639 - OCI objects as VolumeSource](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/4639-oci-volume-source) - v1.32
- Stable
- [1769 - Memory Manager](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/1769-memory-manager) - v1.32
- [1967 - Size memory backed volumes](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/1967-size-memory-backed-volumes) - v1.32
- [24 - Add AppArmor Support](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/24-apparmor) - v1.31
- [3545 - Improved multi-numa alignment in Topology Manager](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/3545-improved-multi-numa-alignment) - v1.32
- [3673 - Kubelet limit of Parallel Image Pulls](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/3673-kubelet-parallel-image-pull-limit) - v1.32
- [3960 - Pod lifecycle sleep action](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/3960-pod-lifecycle-sleep-action) - v1.32
- [4009 - Add CDI devices to device plugin API](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/4009-add-cdi-devices-to-device-plugin-api) - v1.31
- [4188 - New kubelet gRPC API with endpoint returning local pods information](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/4188-kubelet-pod-readiness-api) - v1.31
- [4569 - Move cgroup v1 in maintenance mode](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/4569-cgroup-v1-maintenance-mode) - v1.31
- [4622 - New TopologyManager Policy which configure the value of maxAllowableNUMANodes](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/4622-topologymanager-max-allowable-numa-nodes) - v1.32 -->
## [Subprojects](https://git.k8s.io/community/sig-node#subprojects)
**New in 2024:**
- cri-client
**Continuing:**
- ci-testing
- cri-api
- cri-tools
- kernel-module-management
- kubelet
- node-api
- node-feature-discovery
- node-problem-detector
- resource-management
- security-profiles-operator
## [Working groups](https://git.k8s.io/community/sig-node#working-groups)
**New in 2024:**
- Device Management
- Serving
**Continuing:**
- Batch
- Policy
- Structured Logging
## 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
- [ ] Meeting notes and recordings for 2024 are linked from [README.md] and updated/uploaded if needed
[CONTRIBUTING.md]: https://git.k8s.io/community/sig-node/CONTRIBUTING.md
[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md
[README.md]: https://git.k8s.io/community/sig-node/README.md
[sigs.yaml]: https://git.k8s.io/community/sigs.yaml
[devel]: https://git.k8s.io/community/contributors/devel/README.md

View File

@ -27,7 +27,7 @@ The [charter](charter.md) defines the scope and governance of the Release Specia
The Chairs of the SIG run operations and processes governing the SIG.
* Jeremy Rickard (**[@jeremyrickard](https://github.com/jeremyrickard)**), Microsoft
* Stephen Augustus (**[@justaugustus](https://github.com/justaugustus)**), Cisco
* Stephen Augustus (**[@justaugustus](https://github.com/justaugustus)**), Bloomberg L.P.
* Sascha Grunert (**[@saschagrunert](https://github.com/saschagrunert)**), Red Hat
### Technical Leads

View File

@ -0,0 +1,65 @@
# 2024 Annual Report: SIG Release
## Current initiatives and Project Health
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
-->
2. Are there any areas and/or subprojects that your group needs help with (e.g. fewer than 2 active OWNERS)?
3. Did you have community-wide updates in 2024 (e.g. KubeCon talks)?
<!--
Examples include links to email, slides, or recordings.
-->
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.
-->
<!--
-->
## [Subprojects](https://git.k8s.io/community/sig-release#subprojects)
**Continuing:**
- Release Engineering
- Release Team
- SIG Release Process Documentation
## [Working groups](https://git.k8s.io/community/sig-release#working-groups)
**Continuing:**
- LTS
## 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
- [ ] Meeting notes and recordings for 2024 are linked from [README.md] and updated/uploaded if needed
[CONTRIBUTING.md]: https://git.k8s.io/community/sig-release/CONTRIBUTING.md
[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md
[README.md]: https://git.k8s.io/community/sig-release/README.md
[sigs.yaml]: https://git.k8s.io/community/sigs.yaml
[devel]: https://git.k8s.io/community/contributors/devel/README.md

View File

@ -0,0 +1,65 @@
# 2024 Annual Report: SIG Scalability
## Current initiatives and Project Health
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
-->
2. Are there any areas and/or subprojects that your group needs help with (e.g. fewer than 2 active OWNERS)?
3. Did you have community-wide updates in 2024 (e.g. KubeCon talks)?
<!--
Examples include links to email, slides, or recordings.
-->
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.
-->
<!--
-->
## [Subprojects](https://git.k8s.io/community/sig-scalability#subprojects)
**Continuing:**
- kubernetes-scalability-and-performance-tests-and-validation
- kubernetes-scalability-bottlenecks-detection
- kubernetes-scalability-definition
- kubernetes-scalability-governance
- kubernetes-scalability-test-frameworks
## [Working groups](https://git.k8s.io/community/sig-scalability#working-groups)
## 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
- [ ] Meeting notes and recordings for 2024 are linked from [README.md] and updated/uploaded if needed
[CONTRIBUTING.md]: https://git.k8s.io/community/sig-scalability/CONTRIBUTING.md
[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md
[README.md]: https://git.k8s.io/community/sig-scalability/README.md
[sigs.yaml]: https://git.k8s.io/community/sigs.yaml
[devel]: https://git.k8s.io/community/contributors/devel/README.md

View File

@ -0,0 +1,84 @@
# 2024 Annual Report: SIG Scheduling
## Current initiatives and Project Health
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
-->
2. Are there any areas and/or subprojects that your group needs help with (e.g. fewer than 2 active OWNERS)?
3. Did you have community-wide updates in 2024 (e.g. KubeCon talks)?
<!--
Examples include links to email, slides, or recordings.
-->
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.
-->
<!--
- Alpha
- [4816 - DRA Prioritized List](https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/4816-dra-prioritized-list) - v1.32
- [4832 - Asynchronous Preemption](https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/4832-async-preemption) - v1.32
- Beta
- [3633 - Introduce MatchLabelKeys and MismatchLabelKeys to PodAffinity and PodAntiAffinity](https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/3633-matchlabelkeys-to-podaffinity) - v1.31
- Stable
- [3022 - Tuning the number of domains in PodTopologySpread](https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/3022-min-domains-in-pod-topology-spread) - v1.30
- [3521 - Pod Scheduling Readiness](https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/3521-pod-scheduling-readiness) - v1.30
- [3838 - Pod Mutable Scheduling Directives](https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/3838-pod-mutable-scheduling-directives) - v1.30 -->
## [Subprojects](https://git.k8s.io/community/sig-scheduling#subprojects)
**Continuing:**
- cluster-capacity
- descheduler
- kube-scheduler-simulator
- kube-scheduler-wasm-extension
- kueue
- kwok
- scheduler
- scheduler-plugins
## [Working groups](https://git.k8s.io/community/sig-scheduling#working-groups)
**New in 2024:**
- Device Management
- Serving
**Continuing:**
- Batch
- Policy
- Structured Logging
## 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
- [ ] Meeting notes and recordings for 2024 are linked from [README.md] and updated/uploaded if needed
[CONTRIBUTING.md]: https://git.k8s.io/community/sig-scheduling/CONTRIBUTING.md
[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md
[README.md]: https://git.k8s.io/community/sig-scheduling/README.md
[sigs.yaml]: https://git.k8s.io/community/sigs.yaml
[devel]: https://git.k8s.io/community/contributors/devel/README.md

View File

@ -0,0 +1,67 @@
# 2024 Annual Report: SIG Security
## Current initiatives and Project Health
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
-->
2. Are there any areas and/or subprojects that your group needs help with (e.g. fewer than 2 active OWNERS)?
3. Did you have community-wide updates in 2024 (e.g. KubeCon talks)?
<!--
Examples include links to email, slides, or recordings.
-->
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.
-->
<!--
-->
## [Subprojects](https://git.k8s.io/community/sig-security#subprojects)
**Continuing:**
- security-assessments
- security-audit
- security-docs
- security-tooling
- sig-security
## [Working groups](https://git.k8s.io/community/sig-security#working-groups)
**Continuing:**
- LTS
## 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
- [ ] Meeting notes and recordings for 2024 are linked from [README.md] and updated/uploaded if needed
[CONTRIBUTING.md]: https://git.k8s.io/community/sig-security/CONTRIBUTING.md
[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md
[README.md]: https://git.k8s.io/community/sig-security/README.md
[sigs.yaml]: https://git.k8s.io/community/sigs.yaml
[devel]: https://git.k8s.io/community/contributors/devel/README.md

View File

@ -0,0 +1,89 @@
# 2024 Annual Report: SIG Storage
## Current initiatives and Project Health
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
-->
2. Are there any areas and/or subprojects that your group needs help with (e.g. fewer than 2 active OWNERS)?
3. Did you have community-wide updates in 2024 (e.g. KubeCon talks)?
<!--
Examples include links to email, slides, or recordings.
-->
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.
-->
<!--
- Alpha
- [3314 - KEP Template](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/3314-csi-changed-block-tracking) - v1.32
- [4049 - Storage Capacity Scoring of Nodes for Dynamic Provisioning](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/4049-storage-capacity-scoring-of-nodes-for-dynamic-provisioning) - v1.32
- Beta
- [1790 - Recover from volume expansion failure](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/1790-recover-resize-failure) - v1.32
- [2644 - Honor Persistent Volume Reclaim Policy](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/2644-honor-pv-reclaim-policy) - v1.31
- [3476 - Volume Group Snapshot](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/3476-volume-group-snapshot) - v1.32
- [3751 - Kubernetes Volume Provisioned IO](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/3751-volume-attributes-class) - v1.31
- Stable
- [3141 - Prevent unauthorised volume mode conversion](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/3141-prevent-volume-mode-conversion) - v1.30
- [3756 - Robust VolumeManager reconstruction after kubelet restart](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/3756-volume-reconstruction) - v1.30
- [3762 - PersistentVolume last phase transition time](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/3762-persistent-volume-last-phase-transition-time) - v1.31 -->
## [Subprojects](https://git.k8s.io/community/sig-storage#subprojects)
**New in 2024:**
- external-snapshot-metadata
**Continuing:**
- external-storage
- git-sync
- gluster-provisioner
- kubernetes-cosi
- kubernetes-csi
- mount-utils
- nfs-provisioner
- volume-populators
- volumes
## [Working groups](https://git.k8s.io/community/sig-storage#working-groups)
**New in 2024:**
- Serving
**Continuing:**
- Data Protection
- Policy
- Structured Logging
## 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
- [ ] Meeting notes and recordings for 2024 are linked from [README.md] and updated/uploaded if needed
[CONTRIBUTING.md]: https://git.k8s.io/community/sig-storage/CONTRIBUTING.md
[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md
[README.md]: https://git.k8s.io/community/sig-storage/README.md
[sigs.yaml]: https://git.k8s.io/community/sigs.yaml
[devel]: https://git.k8s.io/community/contributors/devel/README.md

View File

@ -0,0 +1,74 @@
# 2024 Annual Report: SIG Testing
## Current initiatives and Project Health
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
-->
2. Are there any areas and/or subprojects that your group needs help with (e.g. fewer than 2 active OWNERS)?
3. Did you have community-wide updates in 2024 (e.g. KubeCon talks)?
<!--
Examples include links to email, slides, or recordings.
-->
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.
-->
<!--
-->
## [Subprojects](https://git.k8s.io/community/sig-testing#subprojects)
**New in 2024:**
- hydrophone
- testgrid
**Continuing:**
- Cloud Provider for KIND
- boskos
- e2e-framework
- kind
- kubetest2
- prow
- sig-testing
- test-infra
- testing-commons
## [Working groups](https://git.k8s.io/community/sig-testing#working-groups)
**Continuing:**
- LTS
## 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
- [ ] Meeting notes and recordings for 2024 are linked from [README.md] and updated/uploaded if needed
[CONTRIBUTING.md]: https://git.k8s.io/community/sig-testing/CONTRIBUTING.md
[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md
[README.md]: https://git.k8s.io/community/sig-testing/README.md
[sigs.yaml]: https://git.k8s.io/community/sigs.yaml
[devel]: https://git.k8s.io/community/contributors/devel/README.md

View File

@ -0,0 +1,61 @@
# 2024 Annual Report: SIG UI
## Current initiatives and Project Health
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
-->
2. Are there any areas and/or subprojects that your group needs help with (e.g. fewer than 2 active OWNERS)?
3. Did you have community-wide updates in 2024 (e.g. KubeCon talks)?
<!--
Examples include links to email, slides, or recordings.
-->
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.
-->
<!--
-->
## [Subprojects](https://git.k8s.io/community/sig-ui#subprojects)
**Continuing:**
- dashboard
## [Working groups](https://git.k8s.io/community/sig-ui#working-groups)
## 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
- [ ] Meeting notes and recordings for 2024 are linked from [README.md] and updated/uploaded if needed
[CONTRIBUTING.md]: https://git.k8s.io/community/sig-ui/CONTRIBUTING.md
[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md
[README.md]: https://git.k8s.io/community/sig-ui/README.md
[sigs.yaml]: https://git.k8s.io/community/sigs.yaml
[devel]: https://git.k8s.io/community/contributors/devel/README.md

View File

@ -0,0 +1,71 @@
# 2024 Annual Report: SIG Windows
## Current initiatives and Project Health
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
-->
2. Are there any areas and/or subprojects that your group needs help with (e.g. fewer than 2 active OWNERS)?
3. Did you have community-wide updates in 2024 (e.g. KubeCon talks)?
<!--
Examples include links to email, slides, or recordings.
-->
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.
-->
<!--
- Alpha
- [4802 - Windows Graceful Node Shutdown](https://github.com/kubernetes/enhancements/tree/master/keps/sig-windows/4802-windows-node-shutdown) - v1.32
- [4885 - Windows CPU and Memory Affinity](https://github.com/kubernetes/enhancements/tree/master/keps/sig-windows/4885-windows-cpu-and-memory-affinity) - v1.32
- Beta
- [2258 - Node log query](https://github.com/kubernetes/enhancements/tree/master/keps/sig-windows/2258-node-log-query) - v1.30
-->
## [Subprojects](https://git.k8s.io/community/sig-windows#subprojects)
**Continuing:**
- windows-gmsa
- windows-operational-readiness
- windows-samples
- windows-service-proxy
- windows-testing
- windows-tools
## [Working groups](https://git.k8s.io/community/sig-windows#working-groups)
## 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
- [ ] Meeting notes and recordings for 2024 are linked from [README.md] and updated/uploaded if needed
[CONTRIBUTING.md]: https://git.k8s.io/community/sig-windows/CONTRIBUTING.md
[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md
[README.md]: https://git.k8s.io/community/sig-windows/README.md
[sigs.yaml]: https://git.k8s.io/community/sigs.yaml
[devel]: https://git.k8s.io/community/contributors/devel/README.md

View File

@ -2019,7 +2019,6 @@ sigs:
liaison:
github: justaugustus
name: Stephen Augustus
company: Cisco
subprojects:
- name: community-images
description: kubectl plugin used to highlight images pulled from community-owned
@ -2533,7 +2532,7 @@ sigs:
email: jeremy.r.rickard@gmail.com
- github: justaugustus
name: Stephen Augustus
company: Cisco
company: Bloomberg L.P.
email: k8s@auggie.dev
- github: saschagrunert
name: Sascha Grunert
@ -2889,12 +2888,15 @@ sigs:
- github: IanColdwater
name: Ian Coldwater
company: Docker
email: ian@coldwater.io
- github: cailyn-codes
name: Cailyn Edwards
company: Okta
email: cailyn-codes@gmail.com
- github: tabbysable
name: Tabitha Sable
company: Datadog
email: tabitha.c.sable@gmail.com
meetings:
- description: Regular SIG Meeting
day: Friday
@ -2963,16 +2965,20 @@ sigs:
- github: saad-ali
name: Saad Ali
company: Google
email: saadali@google.com
- github: xing-yang
name: Xing Yang
company: VMware
email: xingyang105@gmail.com
tech_leads:
- github: jsafrane
name: Jan Šafránek
company: Red Hat
email: jsafrane@redhat.com
- github: msau42
name: Michelle Au
company: Google
email: msau@google.com
emeritus_leads:
- github: childsb
name: Bradley Childs
@ -3718,8 +3724,8 @@ workinggroups:
chairs:
- github: mengjiao-liu
name: Mengjiao Liu
company: DaoCloud
email: mengjiao.liu@daocloud.io
company: Independent
email: liumengjiao.dev@gmail.com
- github: pohly
name: Patrick Ohly
company: Intel
@ -3880,7 +3886,7 @@ committees:
email: antonio.ojea.garcia@gmail.com
- github: justaugustus
name: Stephen Augustus
company: Cisco
company: Bloomberg L.P.
email: k8s@auggie.dev
- github: pacoxu
name: Paco Xu 徐俊杰

View File

@ -0,0 +1,34 @@
# 2024 Annual Report: WG Batch
## Current initiatives and Project Health
1. What work did the WG do this year that should be highlighted?
<!--
Some example items that might be worth highlighting:
- artifacts
- reports
- white papers
- work not tracked in KEPs
-->
2. Are there any areas and/or subprojects that your group needs help with (e.g. fewer than 2 active OWNERS)?
## Operational
Operational tasks in [wg-governance.md]:
- [ ] [README.md] reviewed for accuracy and updated if needed
- [ ] WG leaders 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
- [ ] Updates provided to sponsoring SIGs in 2024
- [$sig-name](https://git.k8s.io/community/$sig-id/)
- links to email, meeting notes, slides, or recordings, etc
- [$sig-name](https://git.k8s.io/community/$sig-id/)
- links to email, meeting notes, slides, or recordings, etc
-
[wg-governance.md]: https://git.k8s.io/community/committee-steering/governance/wg-governance.md
[README.md]: https://git.k8s.io/community/wg-batch/README.md
[sigs.yaml]: https://git.k8s.io/community/sigs.yaml

View File

@ -0,0 +1,34 @@
# 2024 Annual Report: WG Data Protection
## Current initiatives and Project Health
1. What work did the WG do this year that should be highlighted?
<!--
Some example items that might be worth highlighting:
- artifacts
- reports
- white papers
- work not tracked in KEPs
-->
2. Are there any areas and/or subprojects that your group needs help with (e.g. fewer than 2 active OWNERS)?
## Operational
Operational tasks in [wg-governance.md]:
- [ ] [README.md] reviewed for accuracy and updated if needed
- [ ] WG leaders 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
- [ ] Updates provided to sponsoring SIGs in 2024
- [$sig-name](https://git.k8s.io/community/$sig-id/)
- links to email, meeting notes, slides, or recordings, etc
- [$sig-name](https://git.k8s.io/community/$sig-id/)
- links to email, meeting notes, slides, or recordings, etc
-
[wg-governance.md]: https://git.k8s.io/community/committee-steering/governance/wg-governance.md
[README.md]: https://git.k8s.io/community/wg-data-protection/README.md
[sigs.yaml]: https://git.k8s.io/community/sigs.yaml

View File

@ -0,0 +1,34 @@
# 2024 Annual Report: WG Device Management
## Current initiatives and Project Health
1. What work did the WG do this year that should be highlighted?
<!--
Some example items that might be worth highlighting:
- artifacts
- reports
- white papers
- work not tracked in KEPs
-->
2. Are there any areas and/or subprojects that your group needs help with (e.g. fewer than 2 active OWNERS)?
## Operational
Operational tasks in [wg-governance.md]:
- [ ] [README.md] reviewed for accuracy and updated if needed
- [ ] WG leaders 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
- [ ] Updates provided to sponsoring SIGs in 2024
- [$sig-name](https://git.k8s.io/community/$sig-id/)
- links to email, meeting notes, slides, or recordings, etc
- [$sig-name](https://git.k8s.io/community/$sig-id/)
- links to email, meeting notes, slides, or recordings, etc
-
[wg-governance.md]: https://git.k8s.io/community/committee-steering/governance/wg-governance.md
[README.md]: https://git.k8s.io/community/wg-device-management/README.md
[sigs.yaml]: https://git.k8s.io/community/sigs.yaml

View File

@ -0,0 +1,34 @@
# 2024 Annual Report: WG etcd Operator
## Current initiatives and Project Health
1. What work did the WG do this year that should be highlighted?
<!--
Some example items that might be worth highlighting:
- artifacts
- reports
- white papers
- work not tracked in KEPs
-->
2. Are there any areas and/or subprojects that your group needs help with (e.g. fewer than 2 active OWNERS)?
## Operational
Operational tasks in [wg-governance.md]:
- [ ] [README.md] reviewed for accuracy and updated if needed
- [ ] WG leaders 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
- [ ] Updates provided to sponsoring SIGs in 2024
- [$sig-name](https://git.k8s.io/community/$sig-id/)
- links to email, meeting notes, slides, or recordings, etc
- [$sig-name](https://git.k8s.io/community/$sig-id/)
- links to email, meeting notes, slides, or recordings, etc
-
[wg-governance.md]: https://git.k8s.io/community/committee-steering/governance/wg-governance.md
[README.md]: https://git.k8s.io/community/wg-etcd-operator/README.md
[sigs.yaml]: https://git.k8s.io/community/sigs.yaml

View File

@ -0,0 +1,34 @@
# 2024 Annual Report: WG LTS
## Current initiatives and Project Health
1. What work did the WG do this year that should be highlighted?
<!--
Some example items that might be worth highlighting:
- artifacts
- reports
- white papers
- work not tracked in KEPs
-->
2. Are there any areas and/or subprojects that your group needs help with (e.g. fewer than 2 active OWNERS)?
## Operational
Operational tasks in [wg-governance.md]:
- [ ] [README.md] reviewed for accuracy and updated if needed
- [ ] WG leaders 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
- [ ] Updates provided to sponsoring SIGs in 2024
- [$sig-name](https://git.k8s.io/community/$sig-id/)
- links to email, meeting notes, slides, or recordings, etc
- [$sig-name](https://git.k8s.io/community/$sig-id/)
- links to email, meeting notes, slides, or recordings, etc
-
[wg-governance.md]: https://git.k8s.io/community/committee-steering/governance/wg-governance.md
[README.md]: https://git.k8s.io/community/wg-lts/README.md
[sigs.yaml]: https://git.k8s.io/community/sigs.yaml

View File

@ -0,0 +1,34 @@
# 2024 Annual Report: WG Policy
## Current initiatives and Project Health
1. What work did the WG do this year that should be highlighted?
<!--
Some example items that might be worth highlighting:
- artifacts
- reports
- white papers
- work not tracked in KEPs
-->
2. Are there any areas and/or subprojects that your group needs help with (e.g. fewer than 2 active OWNERS)?
## Operational
Operational tasks in [wg-governance.md]:
- [ ] [README.md] reviewed for accuracy and updated if needed
- [ ] WG leaders 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
- [ ] Updates provided to sponsoring SIGs in 2024
- [$sig-name](https://git.k8s.io/community/$sig-id/)
- links to email, meeting notes, slides, or recordings, etc
- [$sig-name](https://git.k8s.io/community/$sig-id/)
- links to email, meeting notes, slides, or recordings, etc
-
[wg-governance.md]: https://git.k8s.io/community/committee-steering/governance/wg-governance.md
[README.md]: https://git.k8s.io/community/wg-policy/README.md
[sigs.yaml]: https://git.k8s.io/community/sigs.yaml

View File

@ -0,0 +1,34 @@
# 2024 Annual Report: WG Serving
## Current initiatives and Project Health
1. What work did the WG do this year that should be highlighted?
<!--
Some example items that might be worth highlighting:
- artifacts
- reports
- white papers
- work not tracked in KEPs
-->
2. Are there any areas and/or subprojects that your group needs help with (e.g. fewer than 2 active OWNERS)?
## Operational
Operational tasks in [wg-governance.md]:
- [ ] [README.md] reviewed for accuracy and updated if needed
- [ ] WG leaders 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
- [ ] Updates provided to sponsoring SIGs in 2024
- [$sig-name](https://git.k8s.io/community/$sig-id/)
- links to email, meeting notes, slides, or recordings, etc
- [$sig-name](https://git.k8s.io/community/$sig-id/)
- links to email, meeting notes, slides, or recordings, etc
-
[wg-governance.md]: https://git.k8s.io/community/committee-steering/governance/wg-governance.md
[README.md]: https://git.k8s.io/community/wg-serving/README.md
[sigs.yaml]: https://git.k8s.io/community/sigs.yaml

View File

@ -26,7 +26,7 @@ The [charter](charter.md) defines the scope and governance of the Structured Log
## Organizers
* Mengjiao Liu (**[@mengjiao-liu](https://github.com/mengjiao-liu)**), DaoCloud
* Mengjiao Liu (**[@mengjiao-liu](https://github.com/mengjiao-liu)**), Independent
* Patrick Ohly (**[@pohly](https://github.com/pohly)**), Intel
## Contact

View File

@ -0,0 +1,34 @@
# 2024 Annual Report: WG Structured Logging
## Current initiatives and Project Health
1. What work did the WG do this year that should be highlighted?
<!--
Some example items that might be worth highlighting:
- artifacts
- reports
- white papers
- work not tracked in KEPs
-->
2. Are there any areas and/or subprojects that your group needs help with (e.g. fewer than 2 active OWNERS)?
## Operational
Operational tasks in [wg-governance.md]:
- [ ] [README.md] reviewed for accuracy and updated if needed
- [ ] WG leaders 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
- [ ] Updates provided to sponsoring SIGs in 2024
- [$sig-name](https://git.k8s.io/community/$sig-id/)
- links to email, meeting notes, slides, or recordings, etc
- [$sig-name](https://git.k8s.io/community/$sig-id/)
- links to email, meeting notes, slides, or recordings, etc
-
[wg-governance.md]: https://git.k8s.io/community/committee-steering/governance/wg-governance.md
[README.md]: https://git.k8s.io/community/wg-structured-logging/README.md
[sigs.yaml]: https://git.k8s.io/community/sigs.yaml