annual-report-2022.md

2022 Annual Report: SIG Node

Current initiatives

1. What work did the SIG do this year that should be highlighted?

2. What initiatives are you working on that aren't being tracked in KEPs?

3. KEP work in 2022 (v1.24, v1.25, v1.26):

• alpha:
  • 2008 - Forensic Container Checkpointing - v1.25
  • 2371 - cAdvisor-less, CRI-full Container and Pod Stats - v1.26
  • 2535 - Ensure Secret Pulled Images - v1.24
  • 3063 - dynamic resource allocation - v1.26
  • 3085 - Pod networking ready condition - v1.25
  • 3288 - Split Stdout and Stderr Log Stream of Container - v1.25
  • 3327 - CPUManager policy option to align CPUs by Socket instead of by NUMA node - v1.25
  • 3545 - Improved multi-numa alignment in Topology Manager - v1.26
• beta:
  • 2712 - Pod Priority Based Graceful Node Shutdown - v1.24
• stable:
  • 1972 - Kubelet Exec Probe Timeouts - v1.24
  • 2133 - Kubelet Credential Providers - v1.26
  • 2221 - Removing dockershim from kubelet - v1.24
  • 2254 - cgroups v2 - v1.25
  • 277 - Ephemeral Containers - v1.25
  • 3570 - CPU Manager - v1.26
  • 3573 - Device Manager Proposal - v1.26
  • 688 - Pod Overhead - v1.24

Project health

1. What areas and/or subprojects does your group need the most help with? Any areas with 2 or fewer OWNERs? (link to more details)

2. What metrics/community health stats does your group care about and/or measure?

3. Does your CONTRIBUTING.md help new contributors engage with your group specifically by pointing to activities or programs that provide useful context or allow easy participation?

4. If your group has special training, requirements for reviewers/approvers, or processes beyond the general contributor guide, does your CONTRIBUTING.md document those to help existing contributors grow throughout the contributor ladder?

5. Does the group have contributors from multiple companies/affiliations?

6. Are there ways end users/companies can contribute that they currently are not? If one of those ways is more full time support, what would they work on and why?

Membership

• Primary slack channel member count:
• Primary mailing list member count:
• Primary meeting attendee count (estimated, if needed):
• Primary meeting participant count (estimated, if needed):
• Unique reviewers for SIG-owned packages:
• Unique approvers for SIG-owned packages:

Include any other ways you measure group membership

Subprojects

New in 2022:

• ci-testing
• kernel-module-management

Continuing:

• cri-api
• cri-tools
• kubelet
• node-api
• node-feature-discovery
• node-problem-detector
• noderesourcetopology-api
• security-profiles-operator

Working groups

New in 2022:

• Batch

Continuing:

• Multitenancy
• 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 (or created if missing and your contributor steps and experience are different or more in-depth than the documentation listed in the general contributor guide and devel folder.)
• Subprojects list and linked OWNERS files in sigs.yaml reviewed for accuracy and updated if needed
• SIG leaders (chairs, tech leads, and subproject owners) in sigs.yaml are accurate and active, and updated if needed
• Meeting notes and recordings for 2022 are linked from README.md and updated/uploaded if needed
• Did you have community-wide updates in 2022 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: - -