kubernetes
/
community
mirror of https://github.com/kubernetes/community.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
community/sig-node/annual-report-2022.md

12 KiB
Raw Blame History

2022 Annual Report: SIG Node

Current initiatives

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

    • Dockershim removal has big effect on community, 3rd party tools vendors and end users.
    • With CRI v1alpha2 removal we set the minimal compatible Containerd version. This is continuous trend as we require newer and newer dependencies.
    • Cgroups v2 GA opens up possibility for new features, but sets the minimal bar for dependencies again.
    • Cgroups v1 deprecation is on horizon.
    • No perma beta progress - keep removing and/or promoting old features. For example, DynamicKubeletConfig removed, various resource managers GA'd.
    • User namespaces for stateless pods entered alpha. It is a very old feature request.
    • Evented PLEG - working on minimization of kubelet overhead at bigger scale.
    • DRA was introduced which opens up more device integration scenarios.

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

    • Keep working on CI stability and overall reliability of SIG Node components.
    • Refactoring E2E Node Tests to run against multiple cloud providers more easily.
    • Infra rehosting: new image registry and working on e2e tests on AWS.

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

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)

    • Node Problem Detector is not very active and has small participation.
    • In general all areas are well covered with reviewers and approvers. However community would benefit to have clearer ownership of areas defined someplace. Ideas (https://github.com/kubernetes/community/issues/7234):
      • Add more people to subdirectories as approvers
      • Split more clearly between approvers and reviewers

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

    • Active PRs and weekly changes of PRs at weekly SIG meetings.
    • Untriaged PRs, bugs - via CI group bug triage.
    • It will be great to have a PR full-cycle metrics to get insights into time to review and time to approve as well as number of iterations.

  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?

    • No, current CONTRIBUTING.md is not adequately covers the getting started experience for the new contributors.
    • Ideas for improvements: https://github.com/kubernetes/community/issues/7223
    • Also we need clearer code organization documentation for Kubernetes. This is not specific to SIG Node, but due to size, SIG Node group would likely benefit the most from it.

  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?

    • We published the SIG Node contributor ladder that details requirements for reviewers/approvers.

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

    • The group has contributors from multiple companies/affiliations.
    • 19 companies made 1+ contributions over the last year.

  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?

    • Drive dockershim deprecation and report back issues. We still see the adoption not being very fast. It will be great to see more 3rd party tools vendors helping with migration.
    • We have another potential deprecation - cgroupv1 upcoming. It will likely be less impactful, but may need support.
    • Need more feedback from end users on various deprecations and a new features.
      • Can we publish surveys and check on features usage from end users?

Membership

  • Primary slack channel member count: 3570 (#sig-node)
  • Primary mailing list member count: 840
  • Primary meeting attendee count (estimated, if needed): 30 (last numbers: 35, 22, 22, 26, 33, 36, 26, 31)
  • Primary meeting participant count (estimated, if needed): 10 (estimated based on # of agenda items)
  • Unique reviewers for SIG-owned packages: 78
  • Unique approvers for SIG-owned packages: 58

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:

Continuing:

  • Multitenancy
  • Policy
  • Structured Logging

Operational

Operational tasks in sig-governance.md: