2021 Annual Report: SIG CLI
What work did the SIG do this year that should be highlighted?
- kubectl events alpha command.
- KRM Functions subproject started.
- New changes to leadership.
- Started a new monthly Kustomize bug scrub.
- Upgraded the version of Kustomize that ships with kubectl.
- Implemented native Go shell completions.
- Replicated donated kubectl.io and kustomize.io to the project.
- IBM donated the Kui project.
What initiatives are you working on that aren't being tracked in KEPs?
KEP work in 2021 (1.x, 1.y, 1.z):
- KEP-555 - Server-side apply - 1.22.stable
- KEP-1441 - kubectl debug - 1.20.beta, continued to evolve the beta through the year
- KEP-859 - kubectl command metadata in http request headers - 1.22.beta
- KEP-1440 - kubectl events - 1.23.alpha
- KEP-2227 - Default container annotation to be used by kubectl - 1.21.alpha
What areas and/or subprojects does your group need the most help with? Any areas with 2 or fewer OWNERs? (link to more details)
- Optimizing kubectl memory usage.
- Kustomize only has two maintainers.
- Our docs, which are joint for Kustomize and Kubectl, need some love. They are built off cli-experimental, are outdated and need SEO improvements. The sites aren't in the first several pages of Google results for "kustomize docs" / "kubectl docs". The donated kustomize.io and kubectl.io sites/domains need to be integrated as well.
What metrics/community health stats does your group care about and/or measure?
- Open untriaged issues and PRs.
- New reviewers and approvers added.
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 this document is out of date and difficult to maintain. We need to update it and model it after some other groups.
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’re working with SIG-Apps on starting a monthly review club, details to be announced soon.
Does the group have contributors from multiple companies/affiliations?
- Yes all of the leads are from different companies and we see a spread of contributions from other companies. That said we would love to see further investment.
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?
- Kustomize is in need of new maintainers. Ideally folks that depend on it daily and able to jump right in.
- kubectl is a large tool and we need new folks to stick around and learn its different pieces.
- Primary slack channel member count: 2014
- Primary mailing list member count: 329
- Primary meeting attendee count (estimated, if needed): 10+
- Primary meeting participant count (estimated, if needed): 6
- Unique reviewers for SIG-owned packages: 9
- Unique approvers for SIG-owned packages: 13
Include any other ways you measure group membership
New in 2021:
- Open sourced "terminal as notebook" support. Example: https://playground.guidebooks.dev/
- 1500 -> 2100 stars
- User study of user preference for kubectl versus web consoles with @algebrot (Cora Coleman). Summary of findings:
We found that among a survey of 60 cloud developers (beginner, intermediate, expert), all strongly prefer using the CLI modality for completing CRUD and debugging tasks and only the intermediates and experts prefer using a different tool modality (web console) for monitoring tasks. Similarly we observed strong preference for the CLI among four developers that completed a task using the CLI and the web console
- Steady growth with 42 new plugins added
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: