Skip to content

Latest commit

 

History

History
245 lines (208 loc) · 15.6 KB

annual-report-2021.md

File metadata and controls

245 lines (208 loc) · 15.6 KB
Raw

2021 Annual Report: SIG Architecture

Current initiatives

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

    SIG-Architecture operates mostly through its subprojects like conformance, enhancements, code organization and production readiness. The regular SIG meetings have turned into a policy making/adjusting forum and for tackling issues that are across various SIGs. The focus has been to increase reliability, make things stable and document things that we hadn't before. Closing conformance gaps! We haven't had to update architecture very much. Stability improved. increased reliability, Stabilizing, version skews etc have helped the community

    • ecosystem balance shifted from using beta APIs primarily to using stable APIs primarily (1.22+)

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

    • KEP survey for enhancements
    • Working with dependencies to cut down indirect go.sum entries.
    • Updating API conventions by adding documentation

  3. KEP work in 2021 (1.21, 1.22, 1.23):

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)

    • PRR we need to grow more reviewers and approvers
    • API reviews has a pipeline set up with Jordan leading. Need more SIGs to identify additional folks to start learning
    • Conformance, all the easy stuff is done. So we have harder stuff to review, so need additional folks with context to help make progress

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

    • We care about regressions, backports, dependencies across release boundaries
    • We care about the number of enhancements per release along with their timely graduation

  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?

    • yes

  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?

    • We need help across all the subprojects that have well defined, ongoing work with an onboarding guide/doc

Membership

  • Primary slack channel member count: #sig-architecture Slack - 2 519
  • Primary mailing list member count: kubernetes-sig-architecture mailing list - 552 members
  • Primary meeting attendee count (estimated, if needed): ~ 10 - 12
  • Primary meeting participant count (estimated, if needed): ~6 - 8
  • Unique reviewers for SIG-owned packages: 20
  • Unique approvers for SIG-owned packages: 13

Include any other ways you measure group membership

Subprojects

Continuing:

  • Architecture and API Governance
  • Conformance Definition
    • We started 2021 with 128 endpoints remaining without conformance test.(69.13% conformance tested)
    • The current count is 51 endpoints remaining without conformance tests putting us at 87.25% conformance tested.
    • In the last 12 months
      • Tests for 75 endpoints was promoted to conformance
      • 34 Endpoints was promoted to GA with conformance tests
      • No new technical debt was incurred
    • We moved the Conformance Office Hours Meeting from Bi-weekly to monthly in Aug 2021 to reduce the strain on attendee's calendars and increase engagement.
    • At the start of 2021 the tracking of ineligible endpoints for conformance was moved to ineligible_endpoints.yaml file. This allows for more community engagement on the eligibility of endpoints for conformance before any endpoint is added to the endpoint to the Ineligible Endpoints list through pubic pull request.
    • Our target for 2022 is to clean up the last 51 endpoint and then move over to Conformance profiles to further increase the value added by conformance testing.
  • Code Organization
    • Added Snyk based scanning for kubernetes/kubernetes repository
    • Updated license tooling for dependencies to generate a directory tree of licenses instead of a single file
    • Cleaned up go.mod/sum contents and tooling removing a whole lot of transitive dependecies and even a couple of recursive dependencies
    • Added tooling to exclude unwanted dependencies
    • Use new tools like golangci-lint for better code health
  • Enhancements
    • In 2021, the subproject was mainly focused on improving the contributor experience via automation and thoughtful ui/ux changes making visible changes to the KEP process.
    • Major efforts were put into improving tooling on the enhancements repo throughout the year allowing us to automate more validation lessening the burden on individual approvers and resulting in more accurate information reflected in the document. All KEPs were migrated to the new template which now includes a key.yaml file.
    • The team had major contributions authoring and negotiating KEP 2572 - Defining the Kubernetes release cadence.
    • We made progress on the receipts process, but ultimately decided that it was too disruptive for the community as a new UI/UX.
    • The team updated the repository documentation and work was started on a KEP website for easier navigation.
    • New members joined the team: 1 new approver and 2 reviewers were added to the Enhancements Subproject. A new kep tools team with initially 4 reviewers and approvers was created and more recently had an addition of 1 new approver/reviewer. We also had 2 owners transition to become our first Emeritus approvers.
    • We hope to keep improving the KEP process in 2022 and will be conducting a community survey to collect feedback, working on a Process KEP template and other improvements.
    • In 2021, the subproject also started a KEP Reading Club with the intent of creating more awareness around the features being worked on, more familiarity with the KEP process, and potentially connecting aspiring contributors with KEP authors looking for help.
  • Production Readiness

Working groups

TODO: dims to send email to WG asking them to talk to us sync of async

Operational

Operational tasks in sig-governance.md: