-
Notifications
You must be signed in to change notification settings - Fork 5.2k
SIG k8s Infra 2024 annual report #8332
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
k8s-ci-robot
merged 1 commit into
kubernetes:master
from
ameukam:sig-k8s-infra-annual-report
Apr 16, 2025
+35
−19
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -4,24 +4,40 @@ | |
|
||
1. What work did the SIG do this year that should be highlighted? | ||
|
||
- Integration with Microsoft Azure | ||
- Migration of prow.k8s.io to the community Infrastructure | ||
- Requirements for the migration fromg Google GCR to Google Artifact Registry | ||
<!-- | ||
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 | ||
--> | ||
- 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)? | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I can't think of any obvious ones in SIG K8s Infra's direct ownership, we've been pretty good about that. I expect future work will need help but that's hard to define here. |
||
|
||
- Improve our security posture | ||
- Optimize resources consumption | ||
- https://github.com/kubernetes/k8s.io/issues/5127 | ||
- https://github.com/kubernetes/k8s.io/issues/7584 | ||
- https://github.com/kubernetes/k8s.io/issues/4303 | ||
- Observability | ||
|
||
3. Did you have community-wide updates in 2024 (e.g. KubeCon talks)? | ||
|
||
[Kubernetes Infra SIG: Intro and Updates](https://www.youtube.com/watch?v=1-OCYY-OG0A) | ||
|
||
[Intro & Deep Dive Kubernetes Infrastructure](https://www.youtube.com/watch?v=XZlalBACTSg) | ||
|
||
<!-- | ||
Examples include links to email, slides, or recordings. | ||
--> | ||
|
||
4. KEP work in 2024 (v1.30, v1.31, v1.32): | ||
|
||
NONE | ||
|
||
<!-- | ||
TODO: Uncomment the following auto-generated list of KEPs, once reviewed & updated for correction. | ||
|
@@ -30,39 +46,39 @@ | |
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 | ||
|
||
- 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 | ||
|
||
- LTS | ||
|
||
## Operational | ||
|
||
Operational tasks in [sig-governance.md]: | ||
- [ ] [README.md] reviewed for accuracy and updated if needed | ||
|
||
- [x] [README.md] reviewed for accuracy and updated if needed | ||
- [ ] [CONTRIBUTING.md] reviewed for accuracy and updated if needed | ||
- [ ] Other contributing docs (e.g. in devel dir or contributor guide) reviewed for accuracy and updated if needed | ||
- [ ] Subprojects list and linked OWNERS files in [sigs.yaml] reviewed for accuracy and updated if needed | ||
- [ ] SIG leaders (chairs, tech leads, and subproject leads) in [sigs.yaml] are accurate and active, and updated if needed | ||
- [x] Subprojects list and linked OWNERS files in [sigs.yaml] reviewed for accuracy and updated if needed | ||
- [x] SIG leaders (chairs, tech leads, and subproject leads) in [sigs.yaml] are accurate and active, and updated if needed | ||
- [ ] Meeting notes and recordings for 2024 are linked from [README.md] and updated/uploaded if needed | ||
|
||
|
||
[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 |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[basically I think we did a TON here and we're underselling it, added a little more]
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we add that we did the final pieces of the GCR migration?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Was that in 2024? IIRC that extended in 2025? Or we mean finishing the k8s.gcr.io redirect?