Skip to content

Commit 56acf3d

Browse files
authored
Merge branch 'kubernetes:master' into patch-1
2 parents 483ec83 + 1a04118 commit 56acf3d

File tree

15 files changed

+266
-39
lines changed

15 files changed

+266
-39
lines changed

communication/slack-config/channels.yaml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -428,6 +428,7 @@ channels:
428428
- name: rancher
429429
- name: random
430430
archived: true
431+
- name: reconcilerio
431432
- name: reddit-mods
432433
- name: riscv
433434
- name: rktnetes

contributors/guide/owners.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -92,10 +92,6 @@ filters:
9292

9393
Instead, set a `.*` key inside `filters` (as shown in the previous example).
9494

95-
**WARNING**: The `approve` plugin [does not currently respect `filters`][test-infra-7690].
96-
Until that is fixed, `filters` should only be used for the `labels` key (as shown in the above example).
97-
98-
9995
#### Emeritus
10096

10197
It is inevitable, but there are times when someone may shift focuses, change jobs or step away from
Lines changed: 58 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,58 @@
1+
-------------------------------------------------------------
2+
name: Kat Cosgrove
3+
ID: katcosgrove
4+
info:
5+
- employer: Dell Technologies
6+
- slack: katcosgrove
7+
-------------------------------------------------------------
8+
9+
10+
## SIGS
11+
12+
- SIG Release
13+
- Release Team Subproject Owner
14+
- v1.30 Release Lead
15+
- v1.29 Docs Lead
16+
- v1.25 Comms Lead
17+
18+
- SIG Docs
19+
- Tech Lead
20+
21+
## What I have done
22+
23+
I joined the Kubernetes project in 2020, handling the fallout of the Dockershim deprecation. I authored multiple blog articles quelling community fears in the wake of the deprecation announcement and ahead of the release that finally removed Dockershim.
24+
25+
I joined the release team in v1.23. During the v1.28 release, I noticed a severe gap in reporting, stepped up to fill in the role so the release would not be delayed, and was awarded [SIG Release Contributor of the Year](https://www.kubernetes.dev/community/awards/2023/#release) for it.
26+
27+
As v1.30 lead, I was the first release lead to manage the merging of CI Signal and Bug Triage into one subteam. I was the first release lead to use the [release team removal guidelines](https://github.com/kubernetes/sig-release/blob/master/release-team/release-team-removal.md), which I co-authored. I also implemented a [Docs Freeze](https://github.com/kubernetes/sig-release/blob/master/releases/release_phases.md#docs-freeze) phase, drastically reducing the workload for SIG Docs and Release Docs.
28+
29+
For my improvements to Release Docs, Release Comms, and the release process overall, I became a Release Team subproject owner and a SIG Docs tech lead and have continued to make significant improvements to the operation of both. My goal has always been to improve the efficiency and operation of the Release Team and the project overall.
30+
31+
## What I'll do
32+
33+
The Release Team is required to efficiently collaborate with all other SIGs and aspects of project leadership, giving me a birds-eye view of the difficulties different aspects of the project face with respect to contributor acquisition and onboarding, contributor retention, and cross-team collaboration.
34+
35+
I have an excellent track record of addressing these issues within the scope of the Release Team, and intend to bring those skills to the project overall to fill gaps in processes that currently make collaborative progress more difficult than necessary.
36+
37+
38+
## Resources About Me
39+
40+
- Some of my talks:
41+
- [Dungeons and Deployments v2: The Clusters of Chaos (KubeCon EU 2024)](https://youtu.be/EWJ6Ih_bQbo?si=XRuQ7zcivfFEoz0L)
42+
- [Dungeons and Deployments: Leveling Up in Kubernetes (KubeCon NA 2023)](https://youtu.be/-CPrDLFM1Aw?si=i-hPLzvFZHg5mAdr)
43+
- [Planning for Maturity: SIG Release’s Revamp for More Stable Kubernetes (KubeCon EU 2024)](https://www.youtube.com/watch?v=UhIXUarNPKc)
44+
- [We Didn’t Start the Fire: Communication Breakdowns and How to Prevent Them (KubeCon EU 2021)](https://www.youtube.com/watch?v=a03Hh1kd6KE)
45+
46+
47+
-Other talks and appearances:
48+
- [The Kubernetes Podcast, v1.30 Uwubernetes](https://www.youtube.com/watch?v=oWIqWPRGXGY)
49+
- [Fly me to the Moon: A Kubernetes Origin Story (KCD UK Keynote)](https://www.youtube.com/watch?v=Pe9V1hG4LUQ)
50+
- [Don’t Panic: Kubernetes and Docker](https://kubernetes.io/blog/2020/12/02/dont-panic-kubernetes-and-docker/)
51+
- [Dockershim: The Historical Context](https://kubernetes.io/blog/2022/05/03/dockershim-historical-context/)
52+
- [Is your cluster ready for v1.24?](https://kubernetes.io/blog/2022/03/31/ready-for-dockershim-removal/)
53+
54+
-About me
55+
- [Nomination](https://github.com/kubernetes/community/issues/8039)
56+
- [GitHub](https://github.com/katcosgrove)
57+
- [LinkedIn](https://linkedin.com/in/katcosgrove)
58+
- [Twitter](https://twitter.com/dixie3flatline)
Lines changed: 38 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,38 @@
1+
-------------------------------------------------------------
2+
name: Natali Vlatko
3+
ID: natalisucks
4+
info:
5+
- employer: Cisco
6+
- slack: Natali
7+
-------------------------------------------------------------
8+
9+
## SIGS
10+
11+
- SIG Docs / Co-Chair
12+
- SIG Auth / Early Issue Triage
13+
- SIG Contributor Experience / Contributor Summit Team
14+
15+
## What I have done
16+
17+
I've served as the Co-chair of SIG Docs since early 2022, with my Kubernetes contribution journey starting in 2020 via SIG Auth. I'm also currently involved with SIG ContribEx, via our bi-annual Contributor Summits. Here are some highlights:
18+
19+
- I led the launch of the official Localization Subproject for Kubernetes, which earned me the [2021 Kubernetes Contributor Award](https://www.kubernetes.dev/community/awards/2021/) for SIG Docs. Kubernetes documentation is now available in 16 different languages, and I'm a sponsor of the Arabic localization, which is currently in progress. I also spearheaded greater recognition of localization contributions for Kubernetes organization membership for new contributors
20+
- I helped launch the regular issue and PR triage sessions for SIG Auth. This triaging helped the SIG organize work on various KEPs, such as [improvements to the Key Management Service (KMS) API](https://kubernetes.io/blog/2022/09/09/kms-v2-improvements/)
21+
- I led the Day of Operations Team for the Kubernetes Contributor Summit NA 2023, and led Communications for the EU 2024 Summit. I’d love to come back and lead the whole damn show in London 2025
22+
- I've actively mentored and sponsored new reviewers and approvers for SIG Docs, and helped build our leadership bench with new Tech Leads
23+
24+
## What I’ll do
25+
26+
My current roles across the project require me to have technical breadth as opposed to depth in a single area, and I believe this'll be a helpful trait as a serving member of the Steering Committee. SIG Docs in particular is a place where contributors and maintainers from all across the project have had to collaborate and find solutions; being involved in efforts such as deprecating our Katacoda tutorials, communicating the Dockershim removal, and upgrading Release Docs processes for better documentation standards in the project, I'm well equipped to work alongside maintainers and contributors alike to help Kubernetes make governance, financial, foundation, and project-wide decisions. My extensive involvement with the CNCF will also serve as useful knowledge and context as part of Steering.
27+
28+
29+
## Resources about me
30+
31+
- Some of my KubeCon/CloudNativeCon talks:
32+
- [Dungeons and Deployments v2: The Clusters of Chaos (KubeCon/CloudNativeCon EU 2024)](https://youtu.be/EWJ6Ih_bQbo?si=XRuQ7zcivfFEoz0L)
33+
- [Dungeons and Deployments: Leveling Up in Kubernetes (KubeCon/CloudNativeCon NA 2023)](https://youtu.be/-CPrDLFM1Aw?si=i-hPLzvFZHg5mAdr)
34+
- [How To Localize Kubernetes Documentation: A Guide For Everyone (KubeCon/CloudNativeCon EU 2023)](https://kccnceu2023.sched.com/event/1HyUP)
35+
- [Contributing to the Kubernetes Website: A Guide For Everyone (KubeCon/CloudNativeCon NA 2022)](https://kccncna2022.sched.com/event/182O1/contributing-to-the-kubernetes-website-a-guide-for-everyone-divya-mohan-rey-lejano-suse-tim-bannister-the-scale-factory-natali-vlatko-wayfair-arsh-sharma-okteto)
36+
- Find me on [GitHub](https://github.com/natalisucks)
37+
- Check out my [LinkedIn](https://www.linkedin.com/in/natalivlatko)
38+
Lines changed: 58 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,58 @@
1+
-------------------------------------------------------------
2+
name: Nabarun Pal
3+
ID: palnabarun
4+
info:
5+
- employer: Broadcom
6+
- slack: palnabarun
7+
-------------------------------------------------------------
8+
9+
## SIGS
10+
11+
- Steering Committee
12+
- Contributor Experience: Chair, GitHub Admin, Community Moderation
13+
- Architecture: Enhancements
14+
15+
Past
16+
- API Machinery: Client Subproject
17+
- Auth: Feature contributor
18+
- Code of Conduct Committee
19+
- Organizing Kubernetes New Contributor Workshops
20+
- Release:
21+
- Release Manager
22+
- Release Team (1.17-1.24, 1.26)
23+
- 1.26 Emeritus Adviser
24+
- 1.24 Branch Manager
25+
- 1.21 Release Lead
26+
- 1.19 Enhancements Lead
27+
28+
## What I have done
29+
30+
In 2019, I got involved with the Kubernetes community through the Python Client. Since then, I have been involved in multiple areas of the project.
31+
32+
Right now, I am serving as a chair for SIG Contributor Experience, where I aim to bridge the needs of our large and varied contributor base with programs that will improve their experience in contributing to Kubernetes. I maintain the Kubernetes GitHub organizations as a GitHub Admin.
33+
34+
I have served the Kubernetes Releases since 2019, with more than nine releases to which I have actively contributed. I was elected to the Kubernetes Code of Conduct Committee, shipped a feature improving configurations of authorizers, maintained the Kubernetes Python client with bug triage, features and release, and co-led multiple Kubernetes New Contributor Workshops in the APAC region, helping new contributors in bootstrapping their journey into the ecosystem.
35+
36+
In the groups I was part of, I made the meetings/processes more sustainable for geographically diverse contributors. One of the examples of such initiatives is asynchronous updates instead of meetings. Over time, I have mentored several contributors to grow up the ladder. Outside of Kubernetes, I am involved with nurturing local community groups and have been instrumental in organizing conferences like PyCon India.
37+
38+
In the past two years, I have served on the Kubernetes Steering Committee, where I actively led initiatives like [introducing Subproject Leads][subproject-leads], [simplifying the Annual Report process][simplify-annual-reports], and enabling the [process for leads to endorse people for travel grants][travel-grants].
39+
40+
## What I'll do
41+
42+
I have seen first-hand the challenges faced by sections of the contributor community in the past 5.5 years that I have been contributing. My active involvement in multiple aspects of the Kubernetes project equips me to form informed opinions on critical areas. Working on those issues in my current term while on the Kubernetes Steering Committee has been an honour. I want to continue working on the rest of those.
43+
44+
- Ensure the practices and processes of the community are sustainable in the long term
45+
- Continue and impart thoughts from my own experience to the community efforts to help part-time contributors working on their own time to contribute to the project sustainably
46+
- Reducing the geographical and linguistic disadvantage of contributors
47+
- Uphold the [values] of the community while dealing with conflicts
48+
49+
## Resources About Me
50+
51+
- About me: [https://nabarun.dev](https://nabarun.dev)
52+
- All Conference Talks: [https://nabarun.dev/speaking/](https://nabarun.dev/speaking/)
53+
- Twitter: [https://twitter.com/theonlynabarun](https://twitter.com/theonlynabarun)
54+
55+
[subproject-leads]: https://github.com/kubernetes/community/pull/7454
56+
[simplify-annual-reports]: https://github.com/kubernetes/community/pull/7717/commits/661d8d820eada8543b7a118c90cb01acffc5b0bf
57+
[travel-grants]: https://groups.google.com/a/kubernetes.io/g/steering/c/sb3NSD-JzNY
58+
[values]: https://github.com/kubernetes/community/blob/master/values.md
Lines changed: 53 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,53 @@
1+
-------------------------------------------------------------
2+
name: Marko Mudrinić
3+
ID: xmudrii
4+
info:
5+
- employer: Kubermatic
6+
- slack: xmudrii
7+
-------------------------------------------------------------
8+
9+
## SIGS
10+
11+
- SIG Release
12+
- Subproject Lead for Release Engineering
13+
- Senior Release Manager
14+
- SIG K8s Infra contributor and maintainer
15+
16+
## What I have done
17+
18+
My Kubernetes journey started in 2018 with [a Summer of Code internship](https://summerofcode.withgoogle.com/archive/2018/projects/5952269212188672), where I implemented a storage layer for aggregated API servers through collaboration with SIG API Machinery.
19+
20+
After the internship, I joined SIG Release where I'm actively contributing for over 6 years, and currently serving as a Subproject Lead for Release Engineering and Senior Release Manager. As a part of SIG Release, I made many impactful changes to the technical and procedural side of the release process, improved our tooling, documentation, and ensured we provide high quality, secure, and reliable releases.
21+
22+
Over the time, I've contributed to different SIGs, such as SIG Cluster Lifecycle, SIG Testing, and SIG K8s Infra.
23+
24+
I joined SIG K8s Infra in 2023 in efforts to reduce and diversify cloud spending. I'm leading a team that maintains a part of the AWS infrastructure used for running CI jobs.
25+
26+
I was leading migration of the packages infrastructure to the community-owned infrastructure hosted at [`pkgs.k8s.io`](https://kubernetes.io/blog/2023/08/15/pkgs-k8s-io-introduction/), solving one of the longest standing problems in the community and SIG Release.
27+
28+
I've received three [Contributor Awards](https://www.kubernetes.dev/community/awards/) for my contributions and impact to the project: [in 2022](https://www.kubernetes.dev/community/awards/2022/) from SIG Release, and [in 2023](https://www.kubernetes.dev/community/awards/2023/) from SIG Release and SIG K8s Infra.
29+
30+
I've been a [CNCF Ambassador](https://www.cncf.io/people/ambassadors/) since November 2023. I was a mentor in the LFX program in the [Term 3: Sept-Nov for the Kubernetes project](https://mentorship.lfx.linuxfoundation.org/project/47f53d22-ff5c-4479-b701-3ca3dbc7df0a).
31+
32+
As of February 2023, I'm a Teaching Associate at the School of Computing, University Union, Belgrade, where I'm teaching Kubernetes and Cloud Native technologies to the final year students.
33+
34+
## What I'll do
35+
36+
Being part of different SIGs for many years taught me a lot about fostering a diverse and sustainable contributor base in many different aspects, and how to mentor and enable contributors to succeed in their roles. I want to provide that experience to the broader Kubernetes project, and it would be my honour to be part of the Steering Committee.
37+
38+
My two most important goals are to ensure the **healthy state** and **sustainability** of the Kubernetes project.
39+
40+
The Steering Committee is **NOT** here to solve technical problems, but to be a liaison between contributors and the CNCF, advocate for the project's needs, and recognize the awesome success of our community members.
41+
42+
I want to make sure that we uphold this, to our goals, vision and values, in an agile, efficient and sustainable manner, while providing support and sponsorship that allow our community members to strive even more. The Kubernetes project is becoming more and more mature, and we need to ensure that our contributors can make an impact, that they're recognized, and to help them to avoid burnout.
43+
44+
## Resources About Me
45+
46+
- [xmudrii.com](https://xmudrii.com)
47+
- [GitHub](https://github.com/xmudrii)
48+
- [LinkedIn](https://linkedin.com/in/xmudrii/)
49+
- [X (Twitter)](https://twitter.com/xmudrii)
50+
- [Talks playlist on YouTube](https://www.youtube.com/playlist?list=PLvNBqHHXyMOBufmiuBrIQvtgOp3smF1Jx)
51+
- My publications on kubernetes.io
52+
- [pkgs.k8s.io: Introducing Kubernetes Community-Owned Package Repositories](https://kubernetes.io/blog/2023/08/15/pkgs-k8s-io-introduction/)
53+
- [Kubernetes Legacy Package Repositories Will Be Frozen On September 13, 2023](https://kubernetes.io/blog/2023/08/31/legacy-package-repository-deprecation/)

elections/steering/2024/voters.yaml

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,8 @@
1414
# 2024-08-01 - Minor correction to fix alpha-sorting of voters list
1515
# 2024-08-20 - Add voters from approved exception requests
1616
# 2024-08-21 - Add voters from approved exception requests
17+
# 2024-08-26 - Add voters from approved exception requests
18+
# 2024-08-28 - Add voters from approved exception requests
1719
#
1820
eligible_voters:
1921
- a-mccarthy
@@ -248,6 +250,7 @@ eligible_voters:
248250
- huww98
249251
- huxcrux
250252
- ialidzhikov
253+
- IanColdwater
251254
- iholder101
252255
- Imtiaz1234
253256
- inductor
@@ -327,6 +330,7 @@ eligible_voters:
327330
- kvaps
328331
- kwiesmueller
329332
- kwilczynski
333+
- lachie83
330334
- laozc
331335
- lauralorenz
332336
- leilajal
@@ -463,6 +467,7 @@ eligible_voters:
463467
- PiotrProkop
464468
- pjbgf
465469
- pmalek
470+
- pnbrown
466471
- pohly
467472
- Prajyot-Parab
468473
- PrasadG193
@@ -475,6 +480,7 @@ eligible_voters:
475480
- pwittrock
476481
- pwschuurman
477482
- qbarrand
483+
- qedrakmar
478484
- qiujian16
479485
- Raffo
480486
- RainbowMango

generator/.gitattributes

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,2 @@
1+
# Always check-out / check-in files with LF line endings.
2+
* text=auto eol=lf

generator/annual-report/sig_report.tmpl

Lines changed: 13 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -14,26 +14,29 @@
1414

1515
2. Are there any areas and/or subprojects that your group needs help with (e.g. fewer than 2 active OWNERS)?
1616

17+
18+
3. Did you have community-wide updates in {{lastYear}} (e.g. KubeCon talks)?
19+
20+
<!--
21+
Examples include links to email, slides, or recordings.
22+
-->
23+
1724
{{$releases := getReleases -}}
1825
{{$owningSIG := .Dir -}}
1926
{{$stagedKeps := filterKEPs $owningSIG $releases -}}
2027
{{$alphaKeps := index $stagedKeps "alpha" -}}
2128
{{$betaKeps := index $stagedKeps "beta" -}}
2229
{{$stableKeps := index $stagedKeps "stable" -}}
30+
4. KEP work in {{lastYear}} ({{$releases.LatestMinusTwo}}, {{$releases.LatestMinusOne}}, {{$releases.Latest}}):
2331
<!--
32+
TODO: Uncomment the following auto-generated list of KEPs, once reviewed & updated for correction.
33+
2434
Note: This list is generated from the KEP metadata in kubernetes/enhancements repository.
2535
If you find any discrepancy in the generated list here, please check the KEP metadata.
2636
Please raise an issue in kubernetes/community, if the KEP metadata is correct but the generated list is incorrect.
2737
-->
2838

29-
3. Did you have community-wide updates in {{lastYear}} (e.g. KubeCon talks)?
30-
31-
<!--
32-
Examples include links to email, slides, or recordings.
33-
-->
34-
35-
4. KEP work in {{lastYear}} ({{$releases.LatestMinusTwo}}, {{$releases.LatestMinusOne}}, {{$releases.Latest}}):
36-
{{if ne (len $alphaKeps) 0}}
39+
<!-- {{if ne (len $alphaKeps) 0}}
3740
- Alpha
3841
{{- range $alphaKeps}}
3942
- [{{.Number}} - {{.Title}}](https://github.com/kubernetes/enhancements/tree/master/keps/{{.OwningSIG}}/{{.Name}}) - {{.Milestone.Alpha -}}
@@ -47,7 +50,7 @@
4750
- Stable
4851
{{- range $stableKeps}}
4952
- [{{.Number}} - {{.Title}}](https://github.com/kubernetes/enhancements/tree/master/keps/{{.OwningSIG}}/{{.Name}}) - {{.Milestone.Stable -}}
50-
{{ end}}{{ end}}
53+
{{ end}}{{ end}} -->
5154

5255
## [Subprojects](https://git.k8s.io/community/{{.Dir}}#subprojects)
5356
{{- define "subprojects" -}}
@@ -111,4 +114,4 @@ Operational tasks in [sig-governance.md]:
111114
[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md
112115
[README.md]: https://git.k8s.io/community/{{.Dir}}/README.md
113116
[sigs.yaml]: https://git.k8s.io/community/sigs.yaml
114-
[devel]: https://git.k8s.io/community/contributors/devel/README.md
117+
[devel]: https://git.k8s.io/community/contributors/devel/README.md

sig-apps/README.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -80,6 +80,10 @@ Application metadata descriptor CRD
8080
- [kubernetes/kompose](https://github.com/kubernetes/kompose/blob/master/OWNERS)
8181
- **Contact:**
8282
- Slack: [#kompose](https://kubernetes.slack.com/messages/kompose)
83+
### llm-instance-gateway
84+
LLM Instance gateway implementation
85+
- **Owners:**
86+
- [kubernetes-sigs/llm-instance-gateway](https://github.com/kubernetes-sigs/llm-instance-gateway/blob/main/OWNERS)
8387
### workloads-api
8488
The core workloads API, which is composed of the CronJob, DaemonSet, Deployment, Job, ReplicaSet, ReplicationController, PodDisruptionBudget and StatefulSet kinds
8589
- **Owners:**

0 commit comments

Comments
 (0)