Skip to content

Latest commit

 

History

History
125 lines (87 loc) · 8.12 KB

annual-report-2021.md

File metadata and controls

125 lines (87 loc) · 8.12 KB
Raw

2021 Annual Report: SIG Network

Current initiatives

  1. What work did the SIG do this year that should be highlighted?
  1. What initiatives are you working on that aren't being tracked in KEPs?

  1. KEP work in 2021:

  • v1alpha2 highlights:
    • Transitioned to new gateway.networking.k8s.io API group to reflect its status as an official Kubernetes API.
    • GEP-724: Simpler Route-Gateway binding.
    • GEP-709: Safe cross namespace references.
    • GEP-713: Policy attachment.
  • Other notable initiatives:

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)
  • kube-dns
  • external-dns
  • ingress-nginx
    • A good community was assembled, and now we have folks (including F5) giving some support in Slack and issues.
    • Bi weekly meetings for issue and PRs prioritization, with a regular attendance of 6 participants.
    • The development cadence is slow. Only 2 or 3 developers are actually maintaining the code, which brings the main concern of GatewayAPI being released and Ingress NGINX (which is an official subproject) not supporting it.
    • Three CVEs has been discovered in the last year, and they have been fixed raising the alert on the need to actually split control plane and data plane. We are planning do a first split to make it easier to support GatewayAPI, and later join forces with KPNG to use similar approach in Ingress NGINX
  1. What metrics/community health stats does your group care about and/or measure?

Not currently monitoring metrics or health statistics.

  1. 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?

We do not have a SIG specific CONTRIBUTING.md

  1. 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]?

There are no special requirements.

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

Yes - we have long-term as well as one-time contributors from a variety of companies.

  1. 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?

Could always use additional code and KEP reviewers, and maintainers for understaffed subprojects as mentioned above.

Membership

  • Primary slack channel member count: 6667
  • Primary mailing list member count: 1181
  • Primary meeting attendee count (estimated, if needed): 20-30
  • Primary meeting participant count (estimated, if needed): 5-10
  • Unique reviewers for SIG-owned packages: 29
  • Unique approvers for SIG-owned packages: 29

Subprojects

New in $2021:

Continuing:

Working groups

New in 2021:

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: