Skip to content

Latest commit

 

History

History
128 lines (92 loc) · 6.58 KB

annual-report-2021.md

File metadata and controls

128 lines (92 loc) · 6.58 KB
Raw

2021 Annual Report: SIG Scalability

Current initiatives

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

    • We helped validating scalability and reliability impact of many features across whole year.
    • We have started testing scalability of large services (1000+ pods).

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

    • We've improved testing framework and infrastructure, for example:
      • Added support for modules in our tests
      • Started measuring availability of api-server
      • Added support for measuring cilium propagation delay, dns latency

  3. KEP work in 2021:

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)

    • Each subproject could benefit from additional hands. However, the Scalability Test Frameworks and Scalability and Performance tests and validation are the ones where we can grow contributors - the other require both very deep and wide understanding of Kubernetes before making reasonable contributions.

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

    • We care mostly about metrics for our main repository perf-tests. We measure them through devstats. We keep track of number of reviewers, opened issues and PRs merged.

  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?

    • Yes, CONTRIBUTING.md points to maintained list of issues with label good first issue.

  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 don't have any special requirements for reviewers/approvers, but most of core areas of sig-scalability required deep and wide understanding of Kubernetes.

  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?

    • End users usually come with questions about scalability, they rarely want to contribute.

Membership

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

Include any other ways you measure group membership

Subprojects

New in 2021:

  • None

Retired in 2021:

  • None

Continuing:

Working groups

New in 2021:

  • None

Retired in 2021:

  • None

Continuing:

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 2021 are linked from README.md and updated/uploaded if needed
  • Did you have community-wide updates in 2021 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: - Kubecon NA 2021