diff options
52 files changed, 2912 insertions, 245 deletions
diff --git a/OWNERS_ALIASES b/OWNERS_ALIASES index 47493ff4..a110b803 100644 --- a/OWNERS_ALIASES +++ b/OWNERS_ALIASES @@ -66,8 +66,10 @@ aliases: - dcbw - thockin sig-node-leads: + - SergeyKanzhelev - dchen1107 - derekwaynecarr + - mrunalp sig-release-leads: - Verolop - cpanato diff --git a/committee-code-of-conduct/README.md b/committee-code-of-conduct/README.md index 37ae5129..7e7c660c 100644 --- a/committee-code-of-conduct/README.md +++ b/committee-code-of-conduct/README.md @@ -44,7 +44,7 @@ The members and their terms are as follows: ### Term ends on August 23, 2023 - Jeremy Rickard (Microsoft) -- Nabarun Pal (VMware) +- Jason DeTiberus (Cisco) ### Term ends on August 17, 2024 diff --git a/committee-code-of-conduct/transparency-reports/2022-h1.md b/committee-code-of-conduct/transparency-reports/2022-h1.md new file mode 100644 index 00000000..71d85e54 --- /dev/null +++ b/committee-code-of-conduct/transparency-reports/2022-h1.md @@ -0,0 +1,44 @@ +# H1 2022 - Transparency Report +This document is a log of all code of conduct incidents occurring in Kubernetes community spaces. Information is anonymized to protect those involved in incidents. + +### Terms used in these reports +- **Incident report**: An incident report is a description of an action, event or public statement the reporter feels violates the Code of Conduct. For more information, see [Incident Reports](https://github.com/kubernetes/community/blob/master/committee-code-of-conduct/incident-process.md#incident-reports). +- **Conduct action**: A conduct action is any action (restorative or punitive) taken by the Code of Conduct Committee or another body empowered by them (such as a direct action by Slack admins). + +## Kubernetes Code of Conduct Transparency Report for H1 2022 +**Data collection period**: January 1, 2022 - June 30, 2022 + +**Incident report counts** + +| Received Via | This Period | Delta vs Prior Period | +| -------- | -------- | -------- | +| conduct@kubernetes.org | 3 | -5 | +| Slack admins | 61 | +5 | +| GitHub admins | X<sup>1</sup> | X<sup>1</sup> | +| Linux Foundation event staff | 5 | +4 | +| Other avenues | N/A | N/A | + +**Total incidents reported**: 69 + +--- + +**Total conduct incidents** +Incident reports determined to be CoC violations and which resulted in conduct action + + +| Action By | Restorative Action This Period | Delta vs Prior Period | Punitive Action This Period | Delta vs Prior Period | +| -------- | -------- | -------- | -------- | -------- | +| Code of Conduct Committee | 0 | -1 | 0 | N/A | +| Slack Admins | 37 | +2 | 14 | +5 | +| GitHub Admins | X<sup>1</sup> | X<sup>1</sup> | X<sup>1</sup> | X<sup>1</sup> | +| Linux Foundation Staff | 4 | X<sup>2</sup> | 0 | X<sup>2</sup> +| Other avenues | N/A | N/A | N/A | N/A | + +**Total incidents which resulted in conduct action**: 41 + +--- + +**Footnotes:** +<sup>1</sup> Due to a full turnover of the code of conduct committee staff, the collection of data for this report was delayed. As such, the data rention window for GitHub had passed. In the future, we will take steps to prevent this from happening. + +<sup>2</sup> This data was not available in the previous transparency report, therefore there is no delta to report. diff --git a/communication/contributor-comms/role-handbooks/Social-Media.md b/communication/contributor-comms/role-handbooks/Social-Media.md index f1a1b36b..972a545e 100644 --- a/communication/contributor-comms/role-handbooks/Social-Media.md +++ b/communication/contributor-comms/role-handbooks/Social-Media.md @@ -4,7 +4,7 @@ This handbook outlines expectations and responsibilities for Social Media Leads as well as Contributor Comms team members who wish to contribute to social media efforts. -Social Media leads' contributions further the Contributor Comms team's efforts to communicate with contributors on a broad scale through social media. At time of writing, the primary social media channel we communicate through is the [@K8sContributors handle on twitter](https://twitter.com/K8sContributors). +Social Media leads' contributions further the Contributor Comms team's efforts to communicate with contributors on a broad scale through social media. At the time of writing, the primary social media channel we communicate through is the [@K8sContributors handle on twitter](https://twitter.com/K8sContributors). Any Kubernetes contributor can write tweets to be distributed through the twitter handle by utilizing the [kubernetes-sigs/contributor-tweets repo](https://github.com/kubernetes-sigs/contributor-tweets). This repo utilizes the open source [twitter-together](https://github.com/gr2m/twitter-together) project to automate tweeting approved from the @K8sContributor handle. The repo also features automation to convert issues into PRs, to make it easier to create tweets with minimal interaction with Github's PR process. @@ -13,14 +13,14 @@ Do note that tweets targeting the greater Kubernetes community should potentiall ## Minimum Skills and Requirements -- Are a member of the [Kubernetes GitHub Org] +- Are a member of the Kubernetes GitHub Org - Familiar with twitter by either having a personal account or managing another account (brand, oss project, employer, local nonprofit, etc) -- Available to either attend regular Contributor Comms meetings or collaborate asynchronously via the #sig-contribex-comms channelnin the Kubernetes Slack +- Available to either attend regular Contributor Comms meetings or collaborate asynchronously via the #sig-contribex-comms channel in the Kubernetes Slack ### Expected Time Investment Team leads: 3-5 hours per week. -Team members: 1-3 hour per week. +Team members: 1-3 hours per week. ## General Expectations @@ -34,7 +34,7 @@ Team members: 1-3 hour per week. The leader(s) of the social media team will be expected to monitor the @K8sContributors handle. Retweets, replies, and responding to replies appropriately fall under the purview of the social media lead. Time-sensitive tweets should also be handled directly by the team lead. Team leads should coordinate with team members to plan tweets in advance, particularly for large contributor-focused events such as KubeCon or Contributor Summit. -Team members will be expected to keep an eye out for news in need of tweeting. Common sources of such announcements are the k-dev mailing list and the #contributor-comms channel on Slack. Team members can submit less time-sensitive tweets to the [kubernetes-sigs/contributor-tweets repo](https://github.com/kubernetes-sigs/contributor-tweets) for review and tweeting. +Team members will be expected to keep an eye out for news in need of tweeting. Common sources of such announcements are the k-dev mailing list and the #sig-contribex-comms channel on Slack. Team members can submit less time-sensitive tweets to the [kubernetes-sigs/contributor-tweets repo](https://github.com/kubernetes-sigs/contributor-tweets) for review and tweeting. ## Associates Overview (Shadow) @@ -43,4 +43,4 @@ Leads should work with shadows to understand their capacity to take on the needs * Becoming an owner (approver privileges) on the [kubernetes-sigs/contributor-tweets](https://github.com/kubernetes-sigs/contributor-tweets) repo * Watching for new tweet PRs and working with PR creators on scheduling/approving tweets * Watching for new tweet requests and ensuring they get assigned to team members or created directly -* Taking on direct Twitter management +* Taking on direct management of a social media account diff --git a/communication/slack-config/channels.yaml b/communication/slack-config/channels.yaml index 27f9454c..4a995eb7 100644 --- a/communication/slack-config/channels.yaml +++ b/communication/slack-config/channels.yaml @@ -330,6 +330,7 @@ channels: - name: multi-platform - name: mysql-operator - name: nais + - name: nauticus - name: navigator archived: true - name: ncw-staff diff --git a/communication/slack-config/usergroups.yaml b/communication/slack-config/usergroups.yaml index 13617746..85385f01 100644 --- a/communication/slack-config/usergroups.yaml +++ b/communication/slack-config/usergroups.yaml @@ -262,3 +262,21 @@ usergroups: - sbueringer - VibhorChinda - ykakarap + + - name: kcp-devs + long_name: kcp Development Team + description: Active developers of kcp on #kcp-dev + members: + - csams + - davidfestal + - hardys + - jmprusi + - kylape + - ncdc + - nrb + - p0lyn0mial + - pweil- + - s-urbaniak + - stevekuznetsov + - sttts + - vincepri diff --git a/communication/slack-config/users.yaml b/communication/slack-config/users.yaml index 3e87bd2a..b55a4e9f 100644 --- a/communication/slack-config/users.yaml +++ b/communication/slack-config/users.yaml @@ -41,8 +41,10 @@ users: cjcullen: U0ALJAVMF cji: U5YSRC21J cpanato: U8DFY4TTK + csams: U02B6A9GF55 Dave Smith-Uchida: UDZDED8G2 david-martin: ULMJ41U73 + davidfestal: U014B06SVJ9 Debanitrkl: U02149V23EU derekwaynecarr: U0A69N5GQ dharmit: U0APPPEKE @@ -66,6 +68,7 @@ users: gsquared94: U0131C0PJBU guineveresaenger: U4H2QU3DW hackeramitkumar: U045992D532 + hardys: UFMADFMS4 hasheddan: ULLQEF30C Heba: UHE5TSU4W hoegaarden: U7VA4RZS9 @@ -87,6 +90,7 @@ users: jimangel: U4HSVFA5U jlbutler: U0122V3T932 jmccormick2001: UMPLV0G0H + jmprusi: U014TN4HTPB jmrodri: U4KATPQ48 joekr: U02MUT273GA Joel Barker: U014AHSTBPA @@ -106,6 +110,7 @@ users: klihub: U9856A799 klueska: UF3ARH55Y Kunal Kushwaha: UQ14U3NAY + kylape: UEUST4S22 LappleApple: U011C07244F leonardpahlke: U029NBZFV97 liggitt: U0BGPQ6DS @@ -131,11 +136,14 @@ users: munnerz: U0EC03FTN nate-double-u: U01AWL6BD62 nawazkh: U03HJN1C81W + ncdc: U0A4MJ62V nikhita: U2PQHGMLN nkubala: UA90QL2BE + nrb: U7S597E00 nzoueidi: UBU72MWP2 onlydole: U1DD4AZND oscr: U0183J37JUQ + p0lyn0mial: U1Q8CER5M pabloschuhmacher: U01AAGZ06KU palnabarun: UBH9NTMBM paris: U5SB22BBQ @@ -148,6 +156,7 @@ users: prietyc123: U01D4MBLM52 puerco: ULGHLJ7TP PurneswarPrasad: U027CFKVAB0 + pweil-: U0AL6882X r-lawton: U019CNHR2E6 rajula96reddy: U7K9EK1HC rashmigottipati: U013T1DD3PW @@ -157,6 +166,7 @@ users: rnapoles-rh: U01KDAMSWJD robshelly: U01LL4P09SR rtaniwa: U03K27HLHKN + s-urbaniak: U0DT660QM sammy: U8NJFL023 sandipanpanda: U02A47HJ517 saschagrunert: U53SUDBD4 @@ -170,6 +180,8 @@ users: shubham-pampattiwar: U01QW84HBBN simplytunde: UAY1NBYHE Sladyn Nunes: UQ9J177Q8 + stevekuznetsov: U0DUKNE6B + sttts: U0A2VFE8J Sujay Pillai: UBW3N1VGW sumitranr: UCQN13L9H swamymsft: UHU7ZNXH8 @@ -186,6 +198,7 @@ users: varshaprasad96: UK59YP2DA Verolop: U7NNE57PU VibhorChinda: U031EALE91D + vincepri: UCD11GCET vladimirmukhin: UHVSCSD4G vzhukovs: U030TR1FG85 wilsonehusin: U0100068GF2 diff --git a/contributors/devel/running-locally.md b/contributors/devel/running-locally.md index 490f1c20..c3a556cd 100644 --- a/contributors/devel/running-locally.md +++ b/contributors/devel/running-locally.md @@ -71,6 +71,8 @@ Set the endpoint for container runtime e.g. containerd export CONTAINER_RUNTIME_ENDPOINT="unix:///run/containerd/containerd.sock" ``` +Optionally set any other environment variables as needed to change the cluster configuration. The possible options are listed at the top of the `./hack/local-up-cluster.sh` script. + In a separate tab of your terminal, run the following: ```sh @@ -100,7 +102,11 @@ print the commands to run to point kubectl at the local cluster. Your cluster is running, and you want to start running containers! -You can now use any of the cluster/kubectl.sh commands to interact with your local setup. +You can now use any of the cluster/kubectl.sh commands to interact with your local setup after setting your KUBECONFIG + +```sh +export KUBECONFIG=/var/run/kubernetes/admin.kubeconfig +``` ```sh ./cluster/kubectl.sh get pods @@ -112,10 +118,11 @@ You can now use any of the cluster/kubectl.sh commands to interact with your loc While waiting for the provisioning to complete, you can monitor progress in another terminal with these commands. ```sh -docker images -# To watch the process pull the nginx image -docker ps -# To watch all Docker processes. +# containerd +# To list images +ctr --namespace k8s.io image ls +# To list containers +ctr --namespace k8s.io containers ls ``` Once provisioning is complete, you can use the following commands for Kubernetes introspection. @@ -177,7 +184,15 @@ To start the DNS service, you need to set the following variables: ```sh KUBE_ENABLE_CLUSTER_DNS=true KUBE_DNS_SERVER_IP="10.0.0.10" -KUBE_DNS_DOMAIN="cluster.local" +KUBE_DNS_NAME="cluster.local" ``` To know more on DNS service you can check out the [docs](http://kubernetes.io/docs/admin/dns/). + +### All pod fail to start with a cgroups error of `expected cgroupsPath to be of format "slice:prefix:name" for systemd cgroups` + +Your container runtime is using the systemd cgroup driver, but by default `./hack/local-up-cluster.sh` uses cgroupfs. To correct the mismatch, set the `CGROUP_DRIVER` environment variable to systemd as well. + +```sh +export CGROUP_DRIVER=systemd +```
\ No newline at end of file diff --git a/contributors/devel/sig-node/OWNERS b/contributors/devel/sig-node/OWNERS index 2ea840ee..ba75a3cb 100644 --- a/contributors/devel/sig-node/OWNERS +++ b/contributors/devel/sig-node/OWNERS @@ -2,10 +2,8 @@ reviewers: - sig-node-leads - - SergeyKanzhelev approvers: - sig-node-leads - - SergeyKanzhelev emeritus_approvers: - ehashman labels: diff --git a/generator/README.md b/generator/README.md index 787dabd3..6c75e951 100644 --- a/generator/README.md +++ b/generator/README.md @@ -80,9 +80,12 @@ drop GitHub issue templates into the `generator/generated/` directory. You can generate the issues from these templates by running: ```bash -ls -1 generator/generated/*.md | xargs -L1 hub issue create -F +for i in $(ls -1 generator/generated/*.md); do hub issue create -F $i && rm $i; done ``` + You may run into rate limiting issues, which is why this command removes the + files after an issue has been successfully created. + ## Adding custom content diff --git a/generator/annual-report/github_issue.tmpl b/generator/annual-report/github_issue.tmpl index b286e3df..40433612 100644 --- a/generator/annual-report/github_issue.tmpl +++ b/generator/annual-report/github_issue.tmpl @@ -1,7 +1,9 @@ {{lastYear}} Annual Report: {{.Prefix | toUpper}} {{.Name}} Chairs: {{range .Leadership.Chairs}}@{{.GitHub}} {{end}} +{{- if.Contact.Liaison.GitHub}} Liaison: @{{.Contact.Liaison.GitHub}} +{{- end}} Actions for the chair/organizer of the community group: - [ ] Consult your community group to complete draft of report @@ -14,8 +16,8 @@ Actions for the chair/organizer of the community group: Once all the above items are complete, this issue may be `/close`'d Key dates: -- Initial PR to communtiy repo should be opened by February 14, {{now.UTC.Year}} -- PR should be reviewed and merged by March 1st, {{now.UTC.Year}} +- Initial PR to communtiy repo should be opened by March 24th, {{now.UTC.Year}} +- PR should be reviewed and merged by April 7th, {{now.UTC.Year}} More detailed information on the annual reports process is available [here](https://git.k8s.io/community/committee-steering/governance/annual-reports.md). @@ -27,6 +29,7 @@ If you have any questions or concerns about this process, you may reach the Stee - The public mailing list steering@kubernetes.io - The private mailing list steering-private@kubernetes.io for any private or sensitive issues. +/assign {{range .Leadership.Chairs}}@{{.GitHub}} {{end}} /{{.Prefix}} {{.Label}} /committee steering /area annual-reports diff --git a/generator/annual-report/sig_report.tmpl b/generator/annual-report/sig_report.tmpl index 2b9206e9..830c119e 100644 --- a/generator/annual-report/sig_report.tmpl +++ b/generator/annual-report/sig_report.tmpl @@ -16,9 +16,9 @@ {{$releases := getReleases}} {{$owingsig := .Dir}} -3. KEP work in {{lastYear}} (v{{$releases.Latest}}, v{{$releases.LatestMinusOne}}, v{{$releases.LatestMinusTwo}}): +3. KEP work in {{lastYear}} ({{$releases.LatestMinusTwo}}, {{$releases.LatestMinusOne}}, {{$releases.Latest}}): {{- range $stage, $keps := filterKEPs $owingsig $releases}} - {{ $stage }}: + - {{ $stage }}: {{- range $keps}} - [{{.Number}} - {{.Title}}](https://github.com/kubernetes/enhancements/tree/master/keps/{{.OwningSIG}}/{{.Name}}) - {{.LatestMilestone -}} {{ end}} diff --git a/generator/app.go b/generator/app.go index 09986697..9ac82530 100644 --- a/generator/app.go +++ b/generator/app.go @@ -43,6 +43,8 @@ import ( "github.com/go-git/go-git/v5/storage/memory" yaml "gopkg.in/yaml.v3" + + "golang.org/x/mod/semver" ) const ( @@ -104,9 +106,24 @@ func getLastThreeK8sReleases() (Releases, error) { return Releases{}, err } var result Releases - result.Latest = strings.Split(strings.TrimPrefix(*releases[0].TagName, "v"), ".")[0] + "." + strings.Split(strings.TrimPrefix(*releases[0].TagName, "v"), ".")[1] - result.LatestMinusOne = strings.Split(strings.TrimPrefix(*releases[1].TagName, "v"), ".")[0] + "." + strings.Split(strings.TrimPrefix(*releases[1].TagName, "v"), ".")[1] - result.LatestMinusTwo = strings.Split(strings.TrimPrefix(*releases[2].TagName, "v"), ".")[0] + "." + strings.Split(strings.TrimPrefix(*releases[2].TagName, "v"), ".")[1] + for _, release := range releases { + if release.GetPrerelease() || release.GetDraft() { + continue + } + if result.Latest == "" { + result.Latest = semver.MajorMinor(release.GetTagName()) + continue + } + if result.LatestMinusOne == "" { + result.LatestMinusOne = semver.MajorMinor(release.GetTagName()) + continue + } + if result.LatestMinusTwo == "" { + result.LatestMinusTwo = semver.MajorMinor(release.GetTagName()) + break + } + } + return result, nil } @@ -712,7 +729,7 @@ func createAnnualReportIssue(groups []Group, prefix string) error { outputPath := filepath.Join(outputDir, fmt.Sprintf("%s_%s.md", lastYear(), group.Dir)) templatePath := filepath.Join(baseGeneratorDir, templateDir, annualReportIssueTemplate) - if err := writeTemplate(templatePath, outputPath, "markdown", group); err != nil { + if err := writeTemplate(templatePath, outputPath, "", group); err != nil { return err } } @@ -756,7 +773,7 @@ func createAnnualReport(groups []Group, prefix string) error { outputPath := filepath.Join(outputDir, fmt.Sprintf("annual-report-%s.md", lastYear())) templatePath := filepath.Join(baseGeneratorDir, templateDir, templateFile) - if err := writeTemplate(templatePath, outputPath, "markdown", group); err != nil { + if err := writeTemplate(templatePath, outputPath, "", group); err != nil { return err } } @@ -6,6 +6,7 @@ require ( github.com/client9/misspell v0.3.4 github.com/go-git/go-git/v5 v5.2.0 github.com/google/go-github/v32 v32.1.0 + golang.org/x/mod v0.4.0 gopkg.in/yaml.v3 v3.0.0-20200313102051-9f266ea9e77c k8s.io/enhancements v0.0.0-20230113204613-7f681415a001 ) @@ -73,16 +73,21 @@ github.com/xanzy/ssh-agent v0.2.1 h1:TCbipTQL2JiiCprBWx9frJ2eJlCYT00NmctrHxVAr70 github.com/xanzy/ssh-agent v0.2.1/go.mod h1:mLlQY/MoOhWBj+gOGMQkOeiEvkx+8pJSI+0Bx9h2kr4= golang.org/x/crypto v0.0.0-20190219172222-a4c6cb3142f2/go.mod h1:6SG95UA2DQfeDnfUPMdvaQW0Q7yPrPDi9nlGo2tz2b4= golang.org/x/crypto v0.0.0-20190308221718-c2843e01d9a2/go.mod h1:djNgcEr1/C05ACkg1iLfiJU5Ep61QUkGW8qpdssI0+w= +golang.org/x/crypto v0.0.0-20191011191535-87dc89f01550/go.mod h1:yigFU9vqHzYiE8UmvKecakEJjdnWj3jj499lnFckfCI= golang.org/x/crypto v0.0.0-20200302210943-78000ba7a073/go.mod h1:LzIPMQfyMNhhGPhUkYOs5KpL4U8rLKemX1yGLhDgUto= golang.org/x/crypto v0.0.0-20200622213623-75b288015ac9/go.mod h1:LzIPMQfyMNhhGPhUkYOs5KpL4U8rLKemX1yGLhDgUto= golang.org/x/crypto v0.0.0-20201002170205-7f63de1d35b0 h1:hb9wdF1z5waM+dSIICn1l0DkLVDT3hqhhQsDNUmHPRE= golang.org/x/crypto v0.0.0-20201002170205-7f63de1d35b0/go.mod h1:LzIPMQfyMNhhGPhUkYOs5KpL4U8rLKemX1yGLhDgUto= +golang.org/x/mod v0.4.0 h1:8pl+sMODzuvGJkmj2W4kZihvVb5mKm8pB/X44PIQHv8= +golang.org/x/mod v0.4.0/go.mod h1:s0Qsj1ACt9ePp/hMypM3fl4fZqREWJwdYDEqhRiZZUA= golang.org/x/net v0.0.0-20190311183353-d8887717615a/go.mod h1:t9HGtf8HONx5eT2rtn7q6eTqICYqUVnKs3thJo3Qplg= golang.org/x/net v0.0.0-20190404232315-eb5bcb51f2a3/go.mod h1:t9HGtf8HONx5eT2rtn7q6eTqICYqUVnKs3thJo3Qplg= +golang.org/x/net v0.0.0-20190620200207-3b0461eec859/go.mod h1:z5CRVTTTmAJ677TzLLGU+0bjPO0LkuOLi4/5GtJWs/s= golang.org/x/net v0.0.0-20200301022130-244492dfa37a/go.mod h1:z5CRVTTTmAJ677TzLLGU+0bjPO0LkuOLi4/5GtJWs/s= golang.org/x/net v0.0.0-20201224014010-6772e930b67b h1:iFwSg7t5GZmB/Q5TjiEAsdoLDrdJRC1RiF2WhuV29Qw= golang.org/x/net v0.0.0-20201224014010-6772e930b67b/go.mod h1:m0MpNAwzfU5UDzcl9v0D8zg8gWTRqZa9RBIspLL5mdg= golang.org/x/oauth2 v0.0.0-20180821212333-d2e6202438be/go.mod h1:N/0e6XlmueqKjAGxoOufVs8QHGRruUQn6yWY3a++T0U= +golang.org/x/sync v0.0.0-20190423024810-112230192c58/go.mod h1:RxMgew5VJxzue5/jJTE5uejpjVlOe/izrB70Jof72aM= golang.org/x/sys v0.0.0-20190215142949-d0b11bdaac8a/go.mod h1:STP8DvDyc/dI5b8T5hshtkjS+E42TnysNCUPdjciGhY= golang.org/x/sys v0.0.0-20190221075227-b4e8571b14e0/go.mod h1:STP8DvDyc/dI5b8T5hshtkjS+E42TnysNCUPdjciGhY= golang.org/x/sys v0.0.0-20190412213103-97732733099d/go.mod h1:h1NjWce9XRLGQEsW7wpKNCjG9DtNlClVuFLEZdDNbEs= @@ -96,6 +101,9 @@ golang.org/x/text v0.3.2/go.mod h1:bEr9sfX3Q8Zfm5fL9x+3itogRgK3+ptLWKqgva+5dAk= golang.org/x/text v0.3.3 h1:cokOdA+Jmi5PJGXLlLllQSgYigAEfHXJAERHVMaCc2k= golang.org/x/text v0.3.3/go.mod h1:5Zoc/QRtKVWzQhOtBMvqHzDpF6irO9z98xDceosuGiQ= golang.org/x/tools v0.0.0-20180917221912-90fa682c2a6e/go.mod h1:n7NCudcB/nEzxVGmLbDWY5pfWTLqBcC2KZ6jyYvM4mQ= +golang.org/x/tools v0.0.0-20191119224855-298f0cb1881e/go.mod h1:b+2E5dAYhXwXZwtnZ6UAqBI28+e2cm9otk0dWdXHAEo= +golang.org/x/xerrors v0.0.0-20190717185122-a985d3407aa7/go.mod h1:I/5z698sn9Ka8TeJc9MKroUUfqBBauWjQqLJ2OPfmY0= +golang.org/x/xerrors v0.0.0-20191011141410-1b5146add898/go.mod h1:I/5z698sn9Ka8TeJc9MKroUUfqBBauWjQqLJ2OPfmY0= google.golang.org/appengine v1.1.0/go.mod h1:EbEs0AVv82hx2wNQdGPgUI5lhzA/G0D9YwlJXL52JkM= gopkg.in/check.v1 v0.0.0-20161208181325-20d25e280405/go.mod h1:Co6ibVJAznAaIkqp8huTwlJQCZ016jof/cbN4VW5Yz0= gopkg.in/check.v1 v1.0.0-20190902080502-41f04d3bba15/go.mod h1:Co6ibVJAznAaIkqp8huTwlJQCZ016jof/cbN4VW5Yz0= diff --git a/sig-api-machinery/annual-report-2022.md b/sig-api-machinery/annual-report-2022.md new file mode 100644 index 00000000..4beb11de --- /dev/null +++ b/sig-api-machinery/annual-report-2022.md @@ -0,0 +1,126 @@ +# 2022 Annual Report: SIG API Machinery + +## Current initiatives + +1. What work did the SIG do this year that should be highlighted? + + - + - + - + +2. What initiatives are you working on that aren't being tracked in KEPs? + + - + - + - + + + +3. KEP work in 2022 (v1.24, v1.25, v1.26): + - alpha: + - [3156 - HTTP3](https://github.com/kubernetes/enhancements/tree/master/keps/sig-api-machinery/3156-http3) - v1.24 + - beta: + - [1965 - kube-apiserver identity](https://github.com/kubernetes/enhancements/tree/master/keps/sig-api-machinery/1965-kube-apiserver-identity) - v1.26 + - [2876 - CRD Validation Expression Language](https://github.com/kubernetes/enhancements/tree/master/keps/sig-api-machinery/2876-crd-validation-expression-language) - v1.25 + - stable: + - [1164 - Deprecate and remove SelfLink](https://github.com/kubernetes/enhancements/tree/master/keps/sig-api-machinery/1164-remove-selflink) - v1.24 + - [1904 - Efficient watch resumption after kube-apiserver reboot](https://github.com/kubernetes/enhancements/tree/master/keps/sig-api-machinery/1904-efficient-watch-resumption) - v1.24 + + +## 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) + + - + - + - + +2. What metrics/community health stats does your group care about and/or measure? + + - + - + - + +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? + + - + +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? + + - + - + +## Membership + +- Primary slack channel member count: +- Primary mailing list member count: +- Primary meeting attendee count (estimated, if needed): +- Primary meeting participant count (estimated, if needed): +- Unique reviewers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files --> +- Unique approvers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files --> + +Include any other ways you measure group membership + +## [Subprojects](https://git.k8s.io/community/sig-api-machinery#subprojects) + + + +**Continuing:** + + - component-base + - control-plane-features + - idl-schema-client-pipeline + - json + - kubernetes-clients + - server-api-aggregation + - server-binaries + - server-crd + - server-frameworks + - server-sdk + - universal-machinery + - yaml + + +## [Working groups](https://git.k8s.io/community/sig-api-machinery#working-groups) + + +**Continuing:** + + - API Expression + - Multitenancy + - Structured Logging + +## 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 2022 are linked from [README.md] and updated/uploaded if needed +- [ ] Did you have community-wide updates in 2022 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: + - + - + +[CONTRIBUTING.md]: https://git.k8s.io/community/sig-api-machinery/CONTRIBUTING.md +[contributor ladder]: https://git.k8s.io/community/community-membership.md +[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md +[README.md]: https://git.k8s.io/community/sig-api-machinery/README.md +[sigs.yaml]: https://git.k8s.io/community/sigs.yaml +[contributor guide]: https://git.k8s.io/community/contributors/guide/README.md +[devel]: https://git.k8s.io/community/contributors/devel/README.md diff --git a/sig-node/annual-report-2021.md b/sig-apps/annual-report-2022.md index 18384773..f0d752ac 100644 --- a/sig-node/annual-report-2021.md +++ b/sig-apps/annual-report-2022.md @@ -1,4 +1,4 @@ -# 2021 Annual Report: SIG Node +# 2022 Annual Report: SIG Apps ## Current initiatives @@ -14,25 +14,20 @@ - - -3. KEP work in 2021 (1.x, 1.y, 1.z): -<!-- -In future, this will be generated from kubernetes/enhancements kep.yaml files -1. with SIG as owning-sig or in participating-sigs -2. listing 1.x, 1.y, or 1.z in milestones or in latest-milestone ---> - - Stable - - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable - - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable - - Beta - - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta - - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta - - Alpha - - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha - - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha - - Pre-alpha - - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) +3. KEP work in 2022 (v1.24, v1.25, v1.26): + - alpha: + - [2804 - Consolidate Workload controllers life cycle status](https://github.com/kubernetes/enhancements/tree/master/keps/sig-apps/2804-consolidate-workload-controllers-status) - v1.24 + - [961 - Implement maxUnavailable for StatefulSets](https://github.com/kubernetes/enhancements/tree/master/keps/sig-apps/961-maxunavailable-for-statefulset) - v1.24 + - beta: + - [2307 - Job tracking without lingering Pods](https://github.com/kubernetes/enhancements/tree/master/keps/sig-apps/2307-job-tracking-without-lingering-pods) - v1.26 + - [2879 - Track ready Pods in Job status](https://github.com/kubernetes/enhancements/tree/master/keps/sig-apps/2879-ready-pods-job-status) - v1.24 + - stable: + - [2214 - Indexed Job](https://github.com/kubernetes/enhancements/tree/master/keps/sig-apps/2214-indexed-job) - v1.24 + - [2232 - Suspend Job](https://github.com/kubernetes/enhancements/tree/master/keps/sig-apps/2232-suspend-jobs) - v1.24 + - [2599 - minReadySeconds for StatefulSets](https://github.com/kubernetes/enhancements/tree/master/keps/sig-apps/2599-minreadyseconds-for-statefulsets) - v1.25 + ## Project health @@ -80,43 +75,29 @@ In future, this will be generated from kubernetes/enhancements kep.yaml files Include any other ways you measure group membership -## Subprojects +## [Subprojects](https://git.k8s.io/community/sig-apps#subprojects) + -<!-- -In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31 -Manually visible via `git diff HEAD@{$YYYY-01-01} HEAD@{$YYYY-12-31} -- $sig-id/README.md` ---> -New in $YYYY: -- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) -- +**Continuing:** -Retired in $YYYY: -- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) -- + - application + - examples + - execution-hook + - kompose + - workloads-api -Continuing: -- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) -- -## Working groups +## [Working groups](https://git.k8s.io/community/sig-apps#working-groups) -<!-- -In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31 -Manually visible via `git diff HEAD@{$YYYY-01-01} HEAD@{$YYYY-12-31} -- $sig-id/README.md` ---> -New in $YYYY: -- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) -- +**New in 2022:** -Retired in $YYYY: -- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) -- + - Batch -Continuing: -- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) -- +**Continuing:** + + - Data Protection ## Operational @@ -128,16 +109,15 @@ Operational tasks in [sig-governance.md]: 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: +- [ ] Meeting notes and recordings for 2022 are linked from [README.md] and updated/uploaded if needed +- [ ] Did you have community-wide updates in 2022 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: - - -[CONTRIBUTING.md]: https://git.k8s.io/community/sig-node/CONTRIBUTING.md +[CONTRIBUTING.md]: https://git.k8s.io/community/sig-apps/CONTRIBUTING.md [contributor ladder]: https://git.k8s.io/community/community-membership.md [sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md -[README.md]: https://git.k8s.io/community/sig-node/README.md +[README.md]: https://git.k8s.io/community/sig-apps/README.md [sigs.yaml]: https://git.k8s.io/community/sigs.yaml [contributor guide]: https://git.k8s.io/community/contributors/guide/README.md [devel]: https://git.k8s.io/community/contributors/devel/README.md - diff --git a/sig-architecture/annual-report-2022.md b/sig-architecture/annual-report-2022.md new file mode 100644 index 00000000..b5148ac5 --- /dev/null +++ b/sig-architecture/annual-report-2022.md @@ -0,0 +1,114 @@ +# 2022 Annual Report: SIG Architecture + +## Current initiatives + +1. What work did the SIG do this year that should be highlighted? + + - + - + - + +2. What initiatives are you working on that aren't being tracked in KEPs? + + - + - + - + + + +3. KEP work in 2022 (v1.24, v1.25, v1.26): + - stable: + - [3136 - Beta APIs Are Off by Default](https://github.com/kubernetes/enhancements/tree/master/keps/sig-architecture/3136-beta-apis-off-by-default) - v1.24 + + +## 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) + + - + - + - + +2. What metrics/community health stats does your group care about and/or measure? + + - + - + - + +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? + + - + +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? + + - + - + +## Membership + +- Primary slack channel member count: +- Primary mailing list member count: +- Primary meeting attendee count (estimated, if needed): +- Primary meeting participant count (estimated, if needed): +- Unique reviewers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files --> +- Unique approvers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files --> + +Include any other ways you measure group membership + +## [Subprojects](https://git.k8s.io/community/sig-architecture#subprojects) + + + +**Continuing:** + + - architecture-and-api-governance + - code-organization + - conformance-definition + - enhancements + - production-readiness + + +## [Working groups](https://git.k8s.io/community/sig-architecture#working-groups) + + +**Continuing:** + + - API Expression + - Policy + - Reliability + - Structured Logging + +## 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 2022 are linked from [README.md] and updated/uploaded if needed +- [ ] Did you have community-wide updates in 2022 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: + - + - + +[CONTRIBUTING.md]: https://git.k8s.io/community/sig-architecture/CONTRIBUTING.md +[contributor ladder]: https://git.k8s.io/community/community-membership.md +[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md +[README.md]: https://git.k8s.io/community/sig-architecture/README.md +[sigs.yaml]: https://git.k8s.io/community/sigs.yaml +[contributor guide]: https://git.k8s.io/community/contributors/guide/README.md +[devel]: https://git.k8s.io/community/contributors/devel/README.md diff --git a/sig-auth/annual-report-2022.md b/sig-auth/annual-report-2022.md new file mode 100644 index 00000000..4333b59d --- /dev/null +++ b/sig-auth/annual-report-2022.md @@ -0,0 +1,126 @@ +# 2022 Annual Report: SIG Auth + +## Current initiatives + +1. What work did the SIG do this year that should be highlighted? + + - + - + - + +2. What initiatives are you working on that aren't being tracked in KEPs? + + - + - + - + + + +3. KEP work in 2022 (v1.24, v1.25, v1.26): + - alpha: + - [2718 - Client Executable Proxy](https://github.com/kubernetes/enhancements/tree/master/keps/sig-auth/2718-20210511-client-exec-proxy) - v1.26 + - [3130 - KMS Observability](https://github.com/kubernetes/enhancements/tree/master/keps/sig-auth/3130-kms-observability) - v1.24 + - stable: + - [2579 - PSP Replacement Policy](https://github.com/kubernetes/enhancements/tree/master/keps/sig-auth/2579-psp-replacement) - v1.25 + - [2784 - CSR Duration](https://github.com/kubernetes/enhancements/tree/master/keps/sig-auth/2784-csr-duration) - v1.24 + + +## 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) + + - + - + - + +2. What metrics/community health stats does your group care about and/or measure? + + - + - + - + +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? + + - + +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? + + - + - + +## Membership + +- Primary slack channel member count: +- Primary mailing list member count: +- Primary meeting attendee count (estimated, if needed): +- Primary meeting participant count (estimated, if needed): +- Unique reviewers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files --> +- Unique approvers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files --> + +Include any other ways you measure group membership + +## [Subprojects](https://git.k8s.io/community/sig-auth#subprojects) + + + +**New in 2022:** + + - sig-auth-tools + +**Continuing:** + + - audit-logging + - authenticators + - authorizers + - certificates + - encryption-at-rest + - hierarchical-namespace-controller + - multi-tenancy + - node-identity-and-isolation + - policy-management + - secrets-store-csi-driver + - service-accounts + + +## [Working groups](https://git.k8s.io/community/sig-auth#working-groups) + + +**Continuing:** + + - Multitenancy + - Policy + +## 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 2022 are linked from [README.md] and updated/uploaded if needed +- [ ] Did you have community-wide updates in 2022 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: + - + - + +[CONTRIBUTING.md]: https://git.k8s.io/community/sig-auth/CONTRIBUTING.md +[contributor ladder]: https://git.k8s.io/community/community-membership.md +[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md +[README.md]: https://git.k8s.io/community/sig-auth/README.md +[sigs.yaml]: https://git.k8s.io/community/sigs.yaml +[contributor guide]: https://git.k8s.io/community/contributors/guide/README.md +[devel]: https://git.k8s.io/community/contributors/devel/README.md diff --git a/sig-autoscaling/annual-report-2022.md b/sig-autoscaling/annual-report-2022.md new file mode 100644 index 00000000..a26c3284 --- /dev/null +++ b/sig-autoscaling/annual-report-2022.md @@ -0,0 +1,109 @@ +# 2022 Annual Report: SIG Autoscaling + +## Current initiatives + +1. What work did the SIG do this year that should be highlighted? + + - + - + - + +2. What initiatives are you working on that aren't being tracked in KEPs? + + - + - + - + + + +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) + + - + - + - + +2. What metrics/community health stats does your group care about and/or measure? + + - + - + - + +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? + + - + +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? + + - + - + +## Membership + +- Primary slack channel member count: +- Primary mailing list member count: +- Primary meeting attendee count (estimated, if needed): +- Primary meeting participant count (estimated, if needed): +- Unique reviewers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files --> +- Unique approvers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files --> + +Include any other ways you measure group membership + +## [Subprojects](https://git.k8s.io/community/sig-autoscaling#subprojects) + + + +**Continuing:** + + - addon-resizer + - cluster-autoscaler + - horizontal-pod-autoscaler + - scale-client + - vertical-pod-autoscaler + + +## [Working groups](https://git.k8s.io/community/sig-autoscaling#working-groups) + + +**New in 2022:** + + - Batch + +## 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 2022 are linked from [README.md] and updated/uploaded if needed +- [ ] Did you have community-wide updates in 2022 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: + - + - + +[CONTRIBUTING.md]: https://git.k8s.io/community/sig-autoscaling/CONTRIBUTING.md +[contributor ladder]: https://git.k8s.io/community/community-membership.md +[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md +[README.md]: https://git.k8s.io/community/sig-autoscaling/README.md +[sigs.yaml]: https://git.k8s.io/community/sigs.yaml +[contributor guide]: https://git.k8s.io/community/contributors/guide/README.md +[devel]: https://git.k8s.io/community/contributors/devel/README.md diff --git a/sig-cli/annual-report-2022.md b/sig-cli/annual-report-2022.md new file mode 100644 index 00000000..9d5848d4 --- /dev/null +++ b/sig-cli/annual-report-2022.md @@ -0,0 +1,117 @@ +# 2022 Annual Report: SIG CLI + +## Current initiatives + +1. What work did the SIG do this year that should be highlighted? + + - + - + - + +2. What initiatives are you working on that aren't being tracked in KEPs? + + - + - + - + + + +3. KEP work in 2022 (v1.24, v1.25, v1.26): + - alpha: + - [2299 - Kustomize Plugin Composition API](https://github.com/kubernetes/enhancements/tree/master/keps/sig-cli/2299-kustomize-plugin-composition) - v1.24 + - [2551 - kubectl return code normalization](https://github.com/kubernetes/enhancements/tree/master/keps/sig-cli/2551-return-code-normalization) - v1.24 + - [2906 - Kustomize Function Catalog](https://github.com/kubernetes/enhancements/tree/master/keps/sig-cli/2906-kustomize-function-catalog) - v1.24 + - [2953 - Kustomize Plugin Graduation](https://github.com/kubernetes/enhancements/tree/master/keps/sig-cli/2953-kustomize-plugin-graduation) - v1.24 + - [3104 - Introduce kuberc](https://github.com/kubernetes/enhancements/tree/master/keps/sig-cli/3104-introduce-kuberc) - v1.25 + - beta: + - [1441 - kubectl debug](https://github.com/kubernetes/enhancements/tree/master/keps/sig-cli/1441-kubectl-debug) - v1.24 + + +## 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) + + - + - + - + +2. What metrics/community health stats does your group care about and/or measure? + + - + - + - + +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? + + - + +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? + + - + - + +## Membership + +- Primary slack channel member count: +- Primary mailing list member count: +- Primary meeting attendee count (estimated, if needed): +- Primary meeting participant count (estimated, if needed): +- Unique reviewers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files --> +- Unique approvers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files --> + +Include any other ways you measure group membership + +## [Subprojects](https://git.k8s.io/community/sig-cli#subprojects) + + + +**Continuing:** + + - cli-experimental + - cli-sdk + - cli-utils + - krew + - krew-index + - krm-functions + - kubectl + - kui + - kustomize + + +## [Working groups](https://git.k8s.io/community/sig-cli#working-groups) + + +## 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 2022 are linked from [README.md] and updated/uploaded if needed +- [ ] Did you have community-wide updates in 2022 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: + - + - + +[CONTRIBUTING.md]: https://git.k8s.io/community/sig-cli/CONTRIBUTING.md +[contributor ladder]: https://git.k8s.io/community/community-membership.md +[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md +[README.md]: https://git.k8s.io/community/sig-cli/README.md +[sigs.yaml]: https://git.k8s.io/community/sigs.yaml +[contributor guide]: https://git.k8s.io/community/contributors/guide/README.md +[devel]: https://git.k8s.io/community/contributors/devel/README.md diff --git a/sig-cloud-provider/annual-report-2022.md b/sig-cloud-provider/annual-report-2022.md new file mode 100644 index 00000000..33b19b40 --- /dev/null +++ b/sig-cloud-provider/annual-report-2022.md @@ -0,0 +1,124 @@ +# 2022 Annual Report: SIG Cloud Provider + +## Current initiatives + +1. What work did the SIG do this year that should be highlighted? + + - + - + - + +2. What initiatives are you working on that aren't being tracked in KEPs? + + - + - + - + + + +3. KEP work in 2022 (v1.24, v1.25, v1.26): + - alpha: + - [2699 - Add webhook hosting to CCM.](https://github.com/kubernetes/enhancements/tree/master/keps/sig-cloud-provider/2699-add-webhook-hosting-to-ccm) - v1.26 + - stable: + - [1959 - Service Type=LoadBalancer Class Field](https://github.com/kubernetes/enhancements/tree/master/keps/sig-cloud-provider/1959-service-lb-class-field) - v1.24 + - [2436 - Controller Manager Leader Migration](https://github.com/kubernetes/enhancements/tree/master/keps/sig-cloud-provider/2436-controller-manager-leader-migration) - v1.24 + + +## 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) + + - + - + - + +2. What metrics/community health stats does your group care about and/or measure? + + - + - + - + +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? + + - + +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? + + - + - + +## Membership + +- Primary slack channel member count: +- Primary mailing list member count: +- Primary meeting attendee count (estimated, if needed): +- Primary meeting participant count (estimated, if needed): +- Unique reviewers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files --> +- Unique approvers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files --> + +Include any other ways you measure group membership + +## [Subprojects](https://git.k8s.io/community/sig-cloud-provider#subprojects) + + + +**New in 2022:** + + - provider-oci + +**Continuing:** + + - cloud-provider-extraction-migration + - kubernetes-cloud-provider + - provider-alibaba-cloud + - provider-aws + - provider-azure + - provider-baiducloud + - provider-gcp + - provider-huaweicloud + - provider-ibmcloud + - provider-openstack + - provider-vsphere + + +## [Working groups](https://git.k8s.io/community/sig-cloud-provider#working-groups) + + +**Continuing:** + + - Structured Logging + +## 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 2022 are linked from [README.md] and updated/uploaded if needed +- [ ] Did you have community-wide updates in 2022 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: + - + - + +[CONTRIBUTING.md]: https://git.k8s.io/community/sig-cloud-provider/CONTRIBUTING.md +[contributor ladder]: https://git.k8s.io/community/community-membership.md +[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md +[README.md]: https://git.k8s.io/community/sig-cloud-provider/README.md +[sigs.yaml]: https://git.k8s.io/community/sigs.yaml +[contributor guide]: https://git.k8s.io/community/contributors/guide/README.md +[devel]: https://git.k8s.io/community/contributors/devel/README.md diff --git a/sig-cluster-lifecycle/annual-report-2022.md b/sig-cluster-lifecycle/annual-report-2022.md new file mode 100644 index 00000000..8c3efcc0 --- /dev/null +++ b/sig-cluster-lifecycle/annual-report-2022.md @@ -0,0 +1,133 @@ +# 2022 Annual Report: SIG Cluster Lifecycle + +## Current initiatives + +1. What work did the SIG do this year that should be highlighted? + + - + - + - + +2. What initiatives are you working on that aren't being tracked in KEPs? + + - + - + - + + + +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) + + - + - + - + +2. What metrics/community health stats does your group care about and/or measure? + + - + - + - + +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? + + - + +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? + + - + - + +## Membership + +- Primary slack channel member count: +- Primary mailing list member count: +- Primary meeting attendee count (estimated, if needed): +- Primary meeting participant count (estimated, if needed): +- Unique reviewers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files --> +- Unique approvers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files --> + +Include any other ways you measure group membership + +## [Subprojects](https://git.k8s.io/community/sig-cluster-lifecycle#subprojects) + + + +**New in 2022:** + + - cluster-api-operator + - cluster-api-provider-cloudstack + - kOps + +**Retired in 2022:** + + - kops + - kube-up + +**Continuing:** + + - cluster-addons + - cluster-api + - cluster-api-provider-aws + - cluster-api-provider-azure + - cluster-api-provider-digitalocean + - cluster-api-provider-gcp + - cluster-api-provider-ibmcloud + - cluster-api-provider-kubemark + - cluster-api-provider-kubevirt + - cluster-api-provider-nested + - cluster-api-provider-openstack + - cluster-api-provider-packet + - cluster-api-provider-vsphere + - etcdadm + - image-builder + - kubeadm + - kubespray + - minikube + + +## [Working groups](https://git.k8s.io/community/sig-cluster-lifecycle#working-groups) + + +**Continuing:** + + - Reliability + +## 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 2022 are linked from [README.md] and updated/uploaded if needed +- [ ] Did you have community-wide updates in 2022 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: + - + - + +[CONTRIBUTING.md]: https://git.k8s.io/community/sig-cluster-lifecycle/CONTRIBUTING.md +[contributor ladder]: https://git.k8s.io/community/community-membership.md +[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md +[README.md]: https://git.k8s.io/community/sig-cluster-lifecycle/README.md +[sigs.yaml]: https://git.k8s.io/community/sigs.yaml +[contributor guide]: https://git.k8s.io/community/contributors/guide/README.md +[devel]: https://git.k8s.io/community/contributors/devel/README.md diff --git a/sig-contributor-experience/annual-report-2022.md b/sig-contributor-experience/annual-report-2022.md new file mode 100644 index 00000000..77f09e09 --- /dev/null +++ b/sig-contributor-experience/annual-report-2022.md @@ -0,0 +1,113 @@ +# 2022 Annual Report: SIG Contributor Experience + +## Current initiatives + +1. What work did the SIG do this year that should be highlighted? + + - + - + - + +2. What initiatives are you working on that aren't being tracked in KEPs? + + - + - + - + + + +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) + + - + - + - + +2. What metrics/community health stats does your group care about and/or measure? + + - + - + - + +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? + + - + +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? + + - + - + +## Membership + +- Primary slack channel member count: +- Primary mailing list member count: +- Primary meeting attendee count (estimated, if needed): +- Primary meeting participant count (estimated, if needed): +- Unique reviewers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files --> +- Unique approvers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files --> + +Include any other ways you measure group membership + +## [Subprojects](https://git.k8s.io/community/sig-contributor-experience#subprojects) + + + +**New in 2022:** + + - elections + +**Continuing:** + + - community + - community-management + - contributor-comms + - contributors-documentation + - devstats + - events + - github-management + - mentoring + - slack-infra + + +## [Working groups](https://git.k8s.io/community/sig-contributor-experience#working-groups) + + +## 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 2022 are linked from [README.md] and updated/uploaded if needed +- [ ] Did you have community-wide updates in 2022 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: + - + - + +[CONTRIBUTING.md]: https://git.k8s.io/community/sig-contributor-experience/CONTRIBUTING.md +[contributor ladder]: https://git.k8s.io/community/community-membership.md +[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md +[README.md]: https://git.k8s.io/community/sig-contributor-experience/README.md +[sigs.yaml]: https://git.k8s.io/community/sigs.yaml +[contributor guide]: https://git.k8s.io/community/contributors/guide/README.md +[devel]: https://git.k8s.io/community/contributors/devel/README.md diff --git a/sig-docs/annual-report-2022.md b/sig-docs/annual-report-2022.md new file mode 100644 index 00000000..f04b1adc --- /dev/null +++ b/sig-docs/annual-report-2022.md @@ -0,0 +1,107 @@ +# 2022 Annual Report: SIG Docs + +## Current initiatives + +1. What work did the SIG do this year that should be highlighted? + + - + - + - + +2. What initiatives are you working on that aren't being tracked in KEPs? + + - + - + - + + + +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) + + - + - + - + +2. What metrics/community health stats does your group care about and/or measure? + + - + - + - + +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? + + - + +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? + + - + - + +## Membership + +- Primary slack channel member count: +- Primary mailing list member count: +- Primary meeting attendee count (estimated, if needed): +- Primary meeting participant count (estimated, if needed): +- Unique reviewers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files --> +- Unique approvers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files --> + +Include any other ways you measure group membership + +## [Subprojects](https://git.k8s.io/community/sig-docs#subprojects) + + + +**New in 2022:** + + - localization + +**Continuing:** + + - kubernetes-blog + - reference-docs + - website + + +## [Working groups](https://git.k8s.io/community/sig-docs#working-groups) + + +## 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 2022 are linked from [README.md] and updated/uploaded if needed +- [ ] Did you have community-wide updates in 2022 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: + - + - + +[CONTRIBUTING.md]: https://git.k8s.io/community/sig-docs/CONTRIBUTING.md +[contributor ladder]: https://git.k8s.io/community/community-membership.md +[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md +[README.md]: https://git.k8s.io/community/sig-docs/README.md +[sigs.yaml]: https://git.k8s.io/community/sigs.yaml +[contributor guide]: https://git.k8s.io/community/contributors/guide/README.md +[devel]: https://git.k8s.io/community/contributors/devel/README.md diff --git a/sig-instrumentation/annual-report-2022.md b/sig-instrumentation/annual-report-2022.md new file mode 100644 index 00000000..a87128a0 --- /dev/null +++ b/sig-instrumentation/annual-report-2022.md @@ -0,0 +1,121 @@ +# 2022 Annual Report: SIG Instrumentation + +## Current initiatives + +1. What work did the SIG do this year that should be highlighted? + + - + - + - + +2. What initiatives are you working on that aren't being tracked in KEPs? + + - + - + - + + + +3. KEP work in 2022 (v1.24, v1.25, v1.26): + - alpha: + - [2831 - Kubelet OpenTelemetry Tracing](https://github.com/kubernetes/enhancements/tree/master/keps/sig-instrumentation/2831-kubelet-tracing) - v1.25 + - [3077 - Contextual logging](https://github.com/kubernetes/enhancements/tree/master/keps/sig-instrumentation/3077-contextual-logging) - v1.24 + - [3466 - Kubernetes Component Health SLIs](https://github.com/kubernetes/enhancements/tree/master/keps/sig-instrumentation/3466-kubernetes-component-health-slis) - v1.26 + - stable: + - [2845 - Deprecate klog specific flags in Kubernetes components](https://github.com/kubernetes/enhancements/tree/master/keps/sig-instrumentation/2845-deprecate-klog-specific-flags-in-k8s-components) - 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) + + - + - + - + +2. What metrics/community health stats does your group care about and/or measure? + + - + - + - + +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? + + - + +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? + + - + - + +## Membership + +- Primary slack channel member count: +- Primary mailing list member count: +- Primary meeting attendee count (estimated, if needed): +- Primary meeting participant count (estimated, if needed): +- Unique reviewers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files --> +- Unique approvers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files --> + +Include any other ways you measure group membership + +## [Subprojects](https://git.k8s.io/community/sig-instrumentation#subprojects) + + + +**Continuing:** + + - custom-metrics-apiserver + - instrumentation + - instrumentation-addons + - instrumentation-tools + - klog + - kube-state-metrics + - metric-stability-framework + - metrics + - metrics-server + - prometheus-adapter + - structured-logging + + +## [Working groups](https://git.k8s.io/community/sig-instrumentation#working-groups) + + +**Continuing:** + + - Structured Logging + +## 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 2022 are linked from [README.md] and updated/uploaded if needed +- [ ] Did you have community-wide updates in 2022 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: + - + - + +[CONTRIBUTING.md]: https://git.k8s.io/community/sig-instrumentation/CONTRIBUTING.md +[contributor ladder]: https://git.k8s.io/community/community-membership.md +[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md +[README.md]: https://git.k8s.io/community/sig-instrumentation/README.md +[sigs.yaml]: https://git.k8s.io/community/sigs.yaml +[contributor guide]: https://git.k8s.io/community/contributors/guide/README.md +[devel]: https://git.k8s.io/community/contributors/devel/README.md diff --git a/sig-k8s-infra/annual-report-2021.md b/sig-k8s-infra/annual-report-2022.md index 33a8ca6b..13faf15f 100644 --- a/sig-k8s-infra/annual-report-2021.md +++ b/sig-k8s-infra/annual-report-2022.md @@ -1,4 +1,4 @@ -# 2021 Annual Report: SIG K8s Infra +# 2022 Annual Report: SIG K8s Infra ## Current initiatives @@ -14,25 +14,10 @@ - - -3. KEP work in 2021 (1.x, 1.y, 1.z): -<!-- -In future, this will be generated from kubernetes/enhancements kep.yaml files -1. with SIG as owning-sig or in participating-sigs -2. listing 1.x, 1.y, or 1.z in milestones or in latest-milestone ---> - - Stable - - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable - - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable - - Beta - - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta - - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta - - Alpha - - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha - - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha - - Pre-alpha - - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) +3. KEP work in 2022 (v1.24, v1.25, v1.26): + ## Project health @@ -80,43 +65,24 @@ In future, this will be generated from kubernetes/enhancements kep.yaml files Include any other ways you measure group membership -## Subprojects +## [Subprojects](https://git.k8s.io/community/sig-k8s-infra#subprojects) -<!-- -In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31 -Manually visible via `git diff HEAD@{$YYYY-01-01} HEAD@{$YYYY-12-31} -- $sig-id/README.md` ---> -New in $YYYY: -- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) -- -Retired in $YYYY: -- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) -- +**New in 2022:** -Continuing: -- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) -- + - porche + - registry.k8s.io -## Working groups +**Continuing:** -<!-- -In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31 -Manually visible via `git diff HEAD@{$YYYY-01-01} HEAD@{$YYYY-12-31} -- $sig-id/README.md` ---> + - k8s-infra-dns + - k8s-infra-groups + - k8s.io -New in $YYYY: -- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) -- -Retired in $YYYY: -- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) -- +## [Working groups](https://git.k8s.io/community/sig-k8s-infra#working-groups) -Continuing: -- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) -- ## Operational @@ -128,8 +94,8 @@ Operational tasks in [sig-governance.md]: 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: +- [ ] Meeting notes and recordings for 2022 are linked from [README.md] and updated/uploaded if needed +- [ ] Did you have community-wide updates in 2022 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: - - @@ -140,4 +106,3 @@ Operational tasks in [sig-governance.md]: [sigs.yaml]: https://git.k8s.io/community/sigs.yaml [contributor guide]: https://git.k8s.io/community/contributors/guide/README.md [devel]: https://git.k8s.io/community/contributors/devel/README.md - diff --git a/sig-list.md b/sig-list.md index 632823be..1a3f5adb 100644 --- a/sig-list.md +++ b/sig-list.md @@ -45,8 +45,8 @@ When the need arises, a [new SIG can be created](sig-wg-lifecycle.md) |[Instrumentation](sig-instrumentation/README.md)|[instrumentation](https://github.com/kubernetes/kubernetes/labels/sig%2Finstrumentation)|* [Elana Hashman](https://github.com/ehashman), Apple<br>* [Han Kang](https://github.com/logicalhan), Google<br>|* [Slack](https://kubernetes.slack.com/messages/sig-instrumentation)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-instrumentation)|* Regular SIG Meeting: [Thursdays at 9:30 PT (Pacific Time) (biweekly)](https://zoom.us/j/5342565819?pwd=RlVsK21NVnR1dmE3SWZQSXhveHZPdz09)<br>* Regular Triage Meeting: [Thursdays at 9:30 PT (Pacific Time) (biweekly - alternating with regular meeting)](https://zoom.us/j/5342565819?pwd=RlVsK21NVnR1dmE3SWZQSXhveHZPdz09)<br> |[K8s Infra](sig-k8s-infra/README.md)|[k8s-infra](https://github.com/kubernetes/kubernetes/labels/sig%2Fk8s-infra)|* [Arnaud Meukam](https://github.com/ameukam), VMware<br>* [Davanum Srinivas](https://github.com/dims), Amazon Web Services<br>|* [Slack](https://kubernetes.slack.com/messages/sig-k8s-infra)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-k8s-infra)|* Regular SIG Meeting: [Wednesdays at 20:00 UTC (bi-weekly)](https://zoom.us/j/93109963352?pwd=SHJTcFR2bVg1akYxSDREUWQzaldrQT09)<br>* (k8s-infra-dns) Regular SIG Meeting: [Wednesdays at 20:00 UTC (bi-weekly)](https://zoom.us/j/93109963352?pwd=SHJTcFR2bVg1akYxSDREUWQzaldrQT09)<br>* (k8s-infra-groups) Regular SIG Meeting: [Wednesdays at 20:00 UTC (bi-weekly)](https://zoom.us/j/93109963352?pwd=SHJTcFR2bVg1akYxSDREUWQzaldrQT09)<br>* (k8s.io) Regular SIG Meeting: [Wednesdays at 20:00 UTC (bi-weekly)](https://zoom.us/j/93109963352?pwd=SHJTcFR2bVg1akYxSDREUWQzaldrQT09)<br>* (porche) Regular SIG Meeting: [Wednesdays at 20:00 UTC (bi-weekly)](https://zoom.us/j/93109963352?pwd=SHJTcFR2bVg1akYxSDREUWQzaldrQT09)<br>* (registry.k8s.io) Regular SIG Meeting: [Wednesdays at 20:00 UTC (bi-weekly)](https://zoom.us/j/93109963352?pwd=SHJTcFR2bVg1akYxSDREUWQzaldrQT09)<br> |[Multicluster](sig-multicluster/README.md)|[multicluster](https://github.com/kubernetes/kubernetes/labels/sig%2Fmulticluster)|* [Jeremy Olmsted-Thompson](https://github.com/jeremyot), Google<br>* [Paul Morie](https://github.com/pmorie), Apple<br>|* [Slack](https://kubernetes.slack.com/messages/sig-multicluster)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-multicluster)|* Regular SIG Meeting: [Tuesdays at 9:30 PT (Pacific Time) (bi-weekly)](https://zoom.us/my/k8s.mc)<br> -|[Network](sig-network/README.md)|[network](https://github.com/kubernetes/kubernetes/labels/sig%2Fnetwork)|* [Casey Davenport](https://github.com/caseydavenport), Tigera<br>* [Dan Williams](https://github.com/dcbw), Red Hat<br>* [Tim Hockin](https://github.com/thockin), Google<br>|* [Slack](https://kubernetes.slack.com/messages/sig-network)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-network)|* Gateway API GAMMA Meeting (APAC Friendly): [Tuesdays at 15:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/96951309977)<br>* Gateway API GAMMA Meeting (EMEA Friendly): [Tuesdays at 08:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/96951309977)<br>* Gateway API Meeting: [Mondays at 15:00 PT (Pacific Time) (weekly)](https://zoom.us/j/441530404)<br>* Network Policy API Meeting: [Tuesdays at 9:00 PT (Pacific Time) (bi-weekly)](https://zoom.us/j/96264742248)<br>* SIG Network Ingress NGINX Meeting: [Thursdays at 8:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/98377891310)<br>* SIG Network KPNG APAC Meeting: [Wednesdays at 16:00 IST (Indian Standard Time) (weekly)](https://docs.google.com/document/d/1yW3AUp5rYDLYCAtZc6e4zeLbP5HPLXdvuEFeVESOTic/edit)<br>* SIG Network KPNG Meeting: [Fridays at 7:30 PT (Pacific Time) (weekly)](https://docs.google.com/document/d/1yW3AUp5rYDLYCAtZc6e4zeLbP5HPLXdvuEFeVESOTic/edit)<br>* SIG Network Meeting: [Thursdays at 09:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/361123509)<br> -|[Node](sig-node/README.md)|[node](https://github.com/kubernetes/kubernetes/labels/sig%2Fnode)|* [Dawn Chen](https://github.com/dchen1107), Google<br>* [Derek Carr](https://github.com/derekwaynecarr), Red Hat<br>|* [Slack](https://kubernetes.slack.com/messages/sig-node)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-node)|* Main SIG Meeting: [Tuesdays at 10:00 PT (Pacific Time) (weekly)](https://zoom.us/j/4799874685)<br>* Weekly CI/Triage Meeting: [Wednesdays at 10:00 PT (Pacific Time) (weekly)](https://zoom.us/j/4799874685)<br> +|[Network](sig-network/README.md)|[network](https://github.com/kubernetes/kubernetes/labels/sig%2Fnetwork)|* [Casey Davenport](https://github.com/caseydavenport), Tigera<br>* [Dan Williams](https://github.com/dcbw), Red Hat<br>* [Tim Hockin](https://github.com/thockin), Google<br>|* [Slack](https://kubernetes.slack.com/messages/sig-network)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-network)|* Gateway API GAMMA Meeting (APAC Friendly): [Tuesdays at 15:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/96951309977)<br>* Gateway API GAMMA Meeting (EMEA Friendly): [Tuesdays at 08:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/96951309977)<br>* Gateway API Meeting: [Mondays at 15:00 PT (Pacific Time) (weekly)](https://zoom.us/j/441530404)<br>* Network Policy API Meeting: [Tuesdays at 9:00 PT (Pacific Time) (bi-weekly)](https://zoom.us/j/96264742248)<br>* SIG Network Ingress NGINX Meeting: [Thursdays at 8:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/98377891310)<br>* SIG Network KPNG APAC Meeting: [Wednesdays at 16:00 IST (Indian Standard Time) (weekly)](https://docs.google.com/document/d/1yW3AUp5rYDLYCAtZc6e4zeLbP5HPLXdvuEFeVESOTic/edit)<br>* SIG Network KPNG Meeting: [Fridays at 7:30 PT (Pacific Time) (weekly)](https://docs.google.com/document/d/1yW3AUp5rYDLYCAtZc6e4zeLbP5HPLXdvuEFeVESOTic/edit)<br>* SIG Network Meeting: [Thursdays at 09:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/361123509)<br>* SIG Network Multi-Network Meeting: [Wednesdays at 08:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/95680858961?pwd=M1c2TTdMZHpMUUtIYXRpbjRobkNJZz09)<br> +|[Node](sig-node/README.md)|[node](https://github.com/kubernetes/kubernetes/labels/sig%2Fnode)|* [Sergey Kanzhelev](https://github.com/SergeyKanzhelev), Google<br>* [Mrunal Patel](https://github.com/mrunalp), Red Hat<br>|* [Slack](https://kubernetes.slack.com/messages/sig-node)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-node)|* Main SIG Meeting: [Tuesdays at 10:00 PT (Pacific Time) (weekly)](https://zoom.us/j/4799874685)<br>* Weekly CI/Triage Meeting: [Wednesdays at 10:00 PT (Pacific Time) (weekly)](https://zoom.us/j/4799874685)<br> |[Release](sig-release/README.md)|[release](https://github.com/kubernetes/kubernetes/labels/sig%2Frelease)|* [Jeremy Rickard](https://github.com/jeremyrickard), Microsoft<br>* [Stephen Augustus](https://github.com/justaugustus), Cisco<br>* [Sascha Grunert](https://github.com/saschagrunert), Red Hat<br>|* [Slack](https://kubernetes.slack.com/messages/sig-release)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-release)|* Regular SIG Meeting APAC/EU Oriented Time: [Tuesdays at 15:30 UTC (biweekly)](https://zoom.us/j/327142148?pwd=RE9aZWtCc0hhOWs4ZTdXZ0hBM0ROdz09)<br>* Regular SIG Meeting US Oriented Time: [Tuesdays at 17:00 UTC (biweekly)](https://zoom.us/j/327142148?pwd=RE9aZWtCc0hhOWs4ZTdXZ0hBM0ROdz09)<br> |[Scalability](sig-scalability/README.md)|[scalability](https://github.com/kubernetes/kubernetes/labels/sig%2Fscalability)|* [Marcel Zieba](https://github.com/marseel), Google<br>* [Shyam Jeedigunta](https://github.com/shyamjvs), AWS<br>|* [Slack](https://kubernetes.slack.com/messages/sig-scalability)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-scale)|* Regular SIG Meeting: [Thursdays at 10:30 PT (Pacific Time) (bi-weekly ([upcoming meeting dates](#upcoming-meeting-dates)))](https://zoom.us/j/94252896018?pwd=cTlMMlBoTHZqUEdjRm9VY2NWNUg5dz09)<br> |[Scheduling](sig-scheduling/README.md)|[scheduling](https://github.com/kubernetes/kubernetes/labels/sig%2Fscheduling)|* [Wei Huang](https://github.com/Huang-Wei), Apple<br>* [Abdullah Gharaibeh](https://github.com/ahg-g), Google<br>|* [Slack](https://kubernetes.slack.com/messages/sig-scheduling)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-scheduling)|* biweekly meeting (NA & Europe): [Thursdays at 17:00 UTC (biweekly starting Thursday June 7, 2018)](https://zoom.us/j/841218129)<br>* descheduler biweekly meeting: [Tuesdays at 17:00 UTC (biweekly starting Tuesday September 13, 2022)](https://zoom.us/j/841218129)<br>* monthly meeting (APAC): [first Thursdays at 02:00 UTC (monthly)](https://zoom.us/j/841218129)<br> diff --git a/sig-multicluster/annual-report-2021.md b/sig-multicluster/annual-report-2022.md index 53d8488e..51192c39 100644 --- a/sig-multicluster/annual-report-2021.md +++ b/sig-multicluster/annual-report-2022.md @@ -1,4 +1,4 @@ -# 2021 Annual Report: SIG Multicluster +# 2022 Annual Report: SIG Multicluster ## Current initiatives @@ -14,25 +14,12 @@ - - -3. KEP work in 2021 (1.x, 1.y, 1.z): -<!-- -In future, this will be generated from kubernetes/enhancements kep.yaml files -1. with SIG as owning-sig or in participating-sigs -2. listing 1.x, 1.y, or 1.z in milestones or in latest-milestone ---> - - Stable - - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable - - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable - - Beta - - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta - - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta - - Alpha - - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha - - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha - - Pre-alpha - - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) +3. KEP work in 2022 (v1.24, v1.25, v1.26): + - alpha: + - [2149 - ClusterID for ClusterSet Identification](https://github.com/kubernetes/enhancements/tree/master/keps/sig-multicluster/2149-clusterid) - v1.24 + ## Project health @@ -80,43 +67,29 @@ In future, this will be generated from kubernetes/enhancements kep.yaml files Include any other ways you measure group membership -## Subprojects +## [Subprojects](https://git.k8s.io/community/sig-multicluster#subprojects) + -<!-- -In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31 -Manually visible via `git diff HEAD@{$YYYY-01-01} HEAD@{$YYYY-12-31} -- $sig-id/README.md` ---> -New in $YYYY: -- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) -- +**Retired in 2022:** -Retired in $YYYY: -- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) -- + - kubemci -Continuing: -- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) -- +**Continuing:** -## Working groups + - Kubefed + - about-api + - mcs-api + - work-api -<!-- -In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31 -Manually visible via `git diff HEAD@{$YYYY-01-01} HEAD@{$YYYY-12-31} -- $sig-id/README.md` ---> -New in $YYYY: -- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) -- +## [Working groups](https://git.k8s.io/community/sig-multicluster#working-groups) -Retired in $YYYY: -- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) -- -Continuing: -- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) -- +**Continuing:** + + - IoT Edge + - Policy ## Operational @@ -128,8 +101,8 @@ Operational tasks in [sig-governance.md]: 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: +- [ ] Meeting notes and recordings for 2022 are linked from [README.md] and updated/uploaded if needed +- [ ] Did you have community-wide updates in 2022 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: - - @@ -140,4 +113,3 @@ Operational tasks in [sig-governance.md]: [sigs.yaml]: https://git.k8s.io/community/sigs.yaml [contributor guide]: https://git.k8s.io/community/contributors/guide/README.md [devel]: https://git.k8s.io/community/contributors/devel/README.md - diff --git a/sig-network/README.md b/sig-network/README.md index 8ea4b0a2..0f4d3223 100644 --- a/sig-network/README.md +++ b/sig-network/README.md @@ -30,6 +30,9 @@ The [charter](charter.md) defines the scope and governance of the Network Specia * SIG Network Meeting: [Thursdays at 09:00 PT (Pacific Time)](https://zoom.us/j/361123509) (biweekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=09:00&tz=PT%20%28Pacific%20Time%29). * [Meeting notes and Agenda](https://docs.google.com/document/d/1_w77-zG_Xj0zYvEMfQZTQ-wPP4kXkpGD8smVtW_qqWM/edit). * [Meeting recordings](https://www.youtube.com/watch?v=phCA5-vWkVM&list=PL69nYSiGNLP2E8vmnqo5MwPOY25sDWIxb). +* SIG Network Multi-Network Meeting: [Wednesdays at 08:00 PT (Pacific Time)](https://zoom.us/j/95680858961?pwd=M1c2TTdMZHpMUUtIYXRpbjRobkNJZz09) (biweekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=08:00&tz=PT%20%28Pacific%20Time%29). + * [Meeting notes and Agenda](https://docs.google.com/document/d/1pe_0aOsI35BEsQJ-FhFH9Z_pWQcU2uqwAnOx2NIx6OY/edit). + * [Meeting recordings](https://www.youtube.com/watch?v=phCA5-vWkVM&list=PL69nYSiGNLP2E8vmnqo5MwPOY25sDWIxb). ## Leadership diff --git a/sig-network/annual-report-2022.md b/sig-network/annual-report-2022.md new file mode 100644 index 00000000..a8a6e0b2 --- /dev/null +++ b/sig-network/annual-report-2022.md @@ -0,0 +1,130 @@ +# 2022 Annual Report: SIG Network + +## Current initiatives + +1. What work did the SIG do this year that should be highlighted? + + - + - + - + +2. What initiatives are you working on that aren't being tracked in KEPs? + + - + - + - + + + +3. KEP work in 2022 (v1.24, v1.25, v1.26): + - alpha: + - [2091 - Add support for AdminNetworkPolicy resources](https://github.com/kubernetes/enhancements/tree/master/keps/sig-network/2091-admin-network-policy) - v1.24 + - [2438 - Dual Stack API Server](https://github.com/kubernetes/enhancements/tree/master/keps/sig-network/2438-dual-stack-apiserver) - v1.24 + - beta: + - [2595 - Expanded DNS Configuration](https://github.com/kubernetes/enhancements/tree/master/keps/sig-network/2595-expanded-dns-config) - v1.26 + - stable: + - [1435 - Different protocols in the same service definition with type=loadbalancer](https://github.com/kubernetes/enhancements/tree/master/keps/sig-network/1435-mixed-protocol-lb) - v1.26 + - [1672 - Tracking Terminating Endpoints in EndpointSlice](https://github.com/kubernetes/enhancements/tree/master/keps/sig-network/1672-tracking-terminating-endpoints) - v1.26 + - [1864 - Optionally Disable Node Ports for Service Type=LoadBalancer](https://github.com/kubernetes/enhancements/tree/master/keps/sig-network/1864-disable-lb-node-ports) - v1.24 + - [2079 - Allow a Network Policy to contemplate a set of ports in a single rule](https://github.com/kubernetes/enhancements/tree/master/keps/sig-network/2079-network-policy-port-range) - v1.25 + - [2086 - Service Internal Traffic Policy](https://github.com/kubernetes/enhancements/tree/master/keps/sig-network/2086-service-internal-traffic-policy) - v1.26 + - [2433 - Topology Aware Hints](https://github.com/kubernetes/enhancements/tree/master/keps/sig-network/2433-topology-aware-hints) - v1.26 + - [3070 - Reserve Service IP Range For Dynamic and Static IP Allocation](https://github.com/kubernetes/enhancements/tree/master/keps/sig-network/3070-reserved-service-ip-range) - 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) + + - + - + - + +2. What metrics/community health stats does your group care about and/or measure? + + - + - + - + +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? + + - + +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? + + - + - + +## Membership + +- Primary slack channel member count: +- Primary mailing list member count: +- Primary meeting attendee count (estimated, if needed): +- Primary meeting participant count (estimated, if needed): +- Unique reviewers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files --> +- Unique approvers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files --> + +Include any other ways you measure group membership + +## [Subprojects](https://git.k8s.io/community/sig-network#subprojects) + + + +**Continuing:** + + - cluster-proportional-autoscaler + - cluster-proportional-vertical-autoscaler + - external-dns + - gateway-api + - ingress + - iptables-wrappers + - kpng + - kube-dns + - network-policy + - pod-networking + + +## [Working groups](https://git.k8s.io/community/sig-network#working-groups) + + +**Continuing:** + + - IoT Edge + - Multitenancy + - Policy + - Structured Logging + +## 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 2022 are linked from [README.md] and updated/uploaded if needed +- [ ] Did you have community-wide updates in 2022 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: + - + - + +[CONTRIBUTING.md]: https://git.k8s.io/community/sig-network/CONTRIBUTING.md +[contributor ladder]: https://git.k8s.io/community/community-membership.md +[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md +[README.md]: https://git.k8s.io/community/sig-network/README.md +[sigs.yaml]: https://git.k8s.io/community/sigs.yaml +[contributor guide]: https://git.k8s.io/community/contributors/guide/README.md +[devel]: https://git.k8s.io/community/contributors/devel/README.md diff --git a/sig-node/OWNERS b/sig-node/OWNERS index 2ea840ee..ba75a3cb 100644 --- a/sig-node/OWNERS +++ b/sig-node/OWNERS @@ -2,10 +2,8 @@ reviewers: - sig-node-leads - - SergeyKanzhelev approvers: - sig-node-leads - - SergeyKanzhelev emeritus_approvers: - ehashman labels: diff --git a/sig-node/README.md b/sig-node/README.md index d24c3908..383888ee 100644 --- a/sig-node/README.md +++ b/sig-node/README.md @@ -25,8 +25,16 @@ The [charter](charter.md) defines the scope and governance of the Node Special I ### Chairs The Chairs of the SIG run operations and processes governing the SIG. +* Sergey Kanzhelev (**[@SergeyKanzhelev](https://github.com/SergeyKanzhelev)**), Google +* Mrunal Patel (**[@mrunalp](https://github.com/mrunalp)**), Red Hat + +### Technical Leads +The Technical Leads of the SIG establish new subprojects, decommission existing +subprojects, and resolve cross-subproject technical issues and decisions. + * Dawn Chen (**[@dchen1107](https://github.com/dchen1107)**), Google * Derek Carr (**[@derekwaynecarr](https://github.com/derekwaynecarr)**), Red Hat +* Mrunal Patel (**[@mrunalp](https://github.com/mrunalp)**), Red Hat ## Contact - Slack: [#sig-node](https://kubernetes.slack.com/messages/sig-node) diff --git a/sig-node/annual-report-2022.md b/sig-node/annual-report-2022.md new file mode 100644 index 00000000..f46e5330 --- /dev/null +++ b/sig-node/annual-report-2022.md @@ -0,0 +1,143 @@ +# 2022 Annual Report: SIG Node + +## Current initiatives + +1. What work did the SIG do this year that should be highlighted? + + - + - + - + +2. What initiatives are you working on that aren't being tracked in KEPs? + + - + - + - + + + +3. KEP work in 2022 (v1.24, v1.25, v1.26): + - alpha: + - [2008 - Forensic Container Checkpointing](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/2008-forensic-container-checkpointing) - v1.25 + - [2371 - cAdvisor-less, CRI-full Container and Pod Stats](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/2371-cri-pod-container-stats) - v1.26 + - [2535 - Ensure Secret Pulled Images](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/2535-ensure-secret-pulled-images) - v1.24 + - [3063 - dynamic resource allocation](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/3063-dynamic-resource-allocation) - v1.26 + - [3085 - Pod networking ready condition](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/3085-pod-conditions-for-starting-completition-of-sandbox-creation) - v1.25 + - [3288 - Split Stdout and Stderr Log Stream of Container](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/3288-separate-stdout-from-stderr) - v1.25 + - [3327 - CPUManager policy option to align CPUs by Socket instead of by NUMA node](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/3327-align-by-socket) - v1.25 + - [3545 - Improved multi-numa alignment in Topology Manager](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/3545-improved-multi-numa-alignment) - v1.26 + - beta: + - [2712 - Pod Priority Based Graceful Node Shutdown](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/2712-pod-priority-based-graceful-node-shutdown) - v1.24 + - stable: + - [1972 - Kubelet Exec Probe Timeouts](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/1972-kubelet-exec-probe-timeouts) - v1.24 + - [2133 - Kubelet Credential Providers](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/2133-kubelet-credential-providers) - v1.26 + - [2221 - Removing dockershim from kubelet](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/2221-remove-dockershim) - v1.24 + - [2254 - cgroups v2](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/2254-cgroup-v2) - v1.25 + - [277 - Ephemeral Containers](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/277-ephemeral-containers) - v1.25 + - [3570 - CPU Manager](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/3570-cpumanager) - v1.26 + - [3573 - Device Manager Proposal](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/3573-device-plugin) - v1.26 + - [688 - Pod Overhead](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/688-pod-overhead) - v1.24 + + +## 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) + + - + - + - + +2. What metrics/community health stats does your group care about and/or measure? + + - + - + - + +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? + + - + +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? + + - + - + +## Membership + +- Primary slack channel member count: +- Primary mailing list member count: +- Primary meeting attendee count (estimated, if needed): +- Primary meeting participant count (estimated, if needed): +- Unique reviewers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files --> +- Unique approvers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files --> + +Include any other ways you measure group membership + +## [Subprojects](https://git.k8s.io/community/sig-node#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](https://git.k8s.io/community/sig-node#working-groups) + + +**New in 2022:** + + - Batch + +**Continuing:** + + - Multitenancy + - Policy + - Structured Logging + +## 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 2022 are linked from [README.md] and updated/uploaded if needed +- [ ] Did you have community-wide updates in 2022 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: + - + - + +[CONTRIBUTING.md]: https://git.k8s.io/community/sig-node/CONTRIBUTING.md +[contributor ladder]: https://git.k8s.io/community/community-membership.md +[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md +[README.md]: https://git.k8s.io/community/sig-node/README.md +[sigs.yaml]: https://git.k8s.io/community/sigs.yaml +[contributor guide]: https://git.k8s.io/community/contributors/guide/README.md +[devel]: https://git.k8s.io/community/contributors/devel/README.md diff --git a/sig-release/annual-report-2022.md b/sig-release/annual-report-2022.md new file mode 100644 index 00000000..2ce357fc --- /dev/null +++ b/sig-release/annual-report-2022.md @@ -0,0 +1,115 @@ +# 2022 Annual Report: SIG Release + +## Current initiatives + +1. What work did the SIG do this year that should be highlighted? + + - + - + - + +2. What initiatives are you working on that aren't being tracked in KEPs? + + - + - + - + + + +3. KEP work in 2022 (v1.24, v1.25, v1.26): + - alpha: + - [3000 - Artifact Distribution Policy](https://github.com/kubernetes/enhancements/tree/master/keps/sig-release/3000-artifact-distribution) - v1.24 + - beta: + - [3031 - Signing release artifacts](https://github.com/kubernetes/enhancements/tree/master/keps/sig-release/3031-signing-release-artifacts) - v1.25 + + +## 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) + + - + - + - + +2. What metrics/community health stats does your group care about and/or measure? + + - + - + - + +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? + + - + +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? + + - + - + +## Membership + +- Primary slack channel member count: +- Primary mailing list member count: +- Primary meeting attendee count (estimated, if needed): +- Primary meeting participant count (estimated, if needed): +- Unique reviewers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files --> +- Unique approvers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files --> + +Include any other ways you measure group membership + +## [Subprojects](https://git.k8s.io/community/sig-release#subprojects) + + + +**Retired in 2022:** + + - kubernetes/repo-infra + +**Continuing:** + + - Release Engineering + - Release Team + - SIG Release Process Documentation + + +## [Working groups](https://git.k8s.io/community/sig-release#working-groups) + + +**Continuing:** + + - Reliability + +## 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 2022 are linked from [README.md] and updated/uploaded if needed +- [ ] Did you have community-wide updates in 2022 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: + - + - + +[CONTRIBUTING.md]: https://git.k8s.io/community/sig-release/CONTRIBUTING.md +[contributor ladder]: https://git.k8s.io/community/community-membership.md +[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md +[README.md]: https://git.k8s.io/community/sig-release/README.md +[sigs.yaml]: https://git.k8s.io/community/sigs.yaml +[contributor guide]: https://git.k8s.io/community/contributors/guide/README.md +[devel]: https://git.k8s.io/community/contributors/devel/README.md diff --git a/sig-scalability/annual-report-2022.md b/sig-scalability/annual-report-2022.md new file mode 100644 index 00000000..4fa20757 --- /dev/null +++ b/sig-scalability/annual-report-2022.md @@ -0,0 +1,109 @@ +# 2022 Annual Report: SIG Scalability + +## Current initiatives + +1. What work did the SIG do this year that should be highlighted? + + - + - + - + +2. What initiatives are you working on that aren't being tracked in KEPs? + + - + - + - + + + +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) + + - + - + - + +2. What metrics/community health stats does your group care about and/or measure? + + - + - + - + +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? + + - + +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? + + - + - + +## Membership + +- Primary slack channel member count: +- Primary mailing list member count: +- Primary meeting attendee count (estimated, if needed): +- Primary meeting participant count (estimated, if needed): +- Unique reviewers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files --> +- Unique approvers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files --> + +Include any other ways you measure group membership + +## [Subprojects](https://git.k8s.io/community/sig-scalability#subprojects) + + + +**Continuing:** + + - kubernetes-scalability-and-performance-tests-and-validation + - kubernetes-scalability-bottlenecks-detection + - kubernetes-scalability-definition + - kubernetes-scalability-governance + - kubernetes-scalability-test-frameworks + + +## [Working groups](https://git.k8s.io/community/sig-scalability#working-groups) + + +**Continuing:** + + - Reliability + +## 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 2022 are linked from [README.md] and updated/uploaded if needed +- [ ] Did you have community-wide updates in 2022 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: + - + - + +[CONTRIBUTING.md]: https://git.k8s.io/community/sig-scalability/CONTRIBUTING.md +[contributor ladder]: https://git.k8s.io/community/community-membership.md +[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md +[README.md]: https://git.k8s.io/community/sig-scalability/README.md +[sigs.yaml]: https://git.k8s.io/community/sigs.yaml +[contributor guide]: https://git.k8s.io/community/contributors/guide/README.md +[devel]: https://git.k8s.io/community/contributors/devel/README.md diff --git a/sig-scheduling/annual-report-2022.md b/sig-scheduling/annual-report-2022.md new file mode 100644 index 00000000..19c20b7e --- /dev/null +++ b/sig-scheduling/annual-report-2022.md @@ -0,0 +1,134 @@ +# 2022 Annual Report: SIG Scheduling + +## Current initiatives + +1. What work did the SIG do this year that should be highlighted? + + - + - + - + +2. What initiatives are you working on that aren't being tracked in KEPs? + + - + - + - + + + +3. KEP work in 2022 (v1.24, v1.25, v1.26): + - beta: + - [3022 - Tuning the number of domains in PodTopologySpread](https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/3022-min-domains-in-pod-topology-spread) - v1.25 + - [3094 - Take taints/tolerations into consideration when calculating PodTopologySpread skew](https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/3094-pod-topology-spread-considering-taints) - v1.25 + - stable: + - [1258 - Default Pod Topology Spread](https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/1258-default-pod-topology-spread) - v1.24 + - [1923 - Prefer Nominated Node](https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/1923-prefer-nominated-node) - v1.24 + - [2249 - Namespace Selector for Pod Affinity](https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/2249-pod-affinity-namespace-selector) - v1.24 + - [785 - Scheduler Component Config API](https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/785-scheduler-component-config-api) - v1.25 + - [902 - Add NonPreempting Option For PriorityClasses](https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/902-non-preempting-priorityclass) - v1.24 + + +## 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) + + - + - + - + +2. What metrics/community health stats does your group care about and/or measure? + + - + - + - + +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? + + - + +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? + + - + - + +## Membership + +- Primary slack channel member count: +- Primary mailing list member count: +- Primary meeting attendee count (estimated, if needed): +- Primary meeting participant count (estimated, if needed): +- Unique reviewers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files --> +- Unique approvers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files --> + +Include any other ways you measure group membership + +## [Subprojects](https://git.k8s.io/community/sig-scheduling#subprojects) + + + +**New in 2022:** + + - kueue + - kwok + +**Retired in 2022:** + + - poseidon + +**Continuing:** + + - cluster-capacity + - descheduler + - kube-batch + - kube-scheduler-simulator + - scheduler + - scheduler-plugins + + +## [Working groups](https://git.k8s.io/community/sig-scheduling#working-groups) + + +**New in 2022:** + + - Batch + +**Continuing:** + + - Multitenancy + - Policy + - Structured Logging + +## 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 2022 are linked from [README.md] and updated/uploaded if needed +- [ ] Did you have community-wide updates in 2022 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: + - + - + +[CONTRIBUTING.md]: https://git.k8s.io/community/sig-scheduling/CONTRIBUTING.md +[contributor ladder]: https://git.k8s.io/community/community-membership.md +[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md +[README.md]: https://git.k8s.io/community/sig-scheduling/README.md +[sigs.yaml]: https://git.k8s.io/community/sigs.yaml +[contributor guide]: https://git.k8s.io/community/contributors/guide/README.md +[devel]: https://git.k8s.io/community/contributors/devel/README.md diff --git a/sig-security/annual-report-2022.md b/sig-security/annual-report-2022.md new file mode 100644 index 00000000..c1197c2a --- /dev/null +++ b/sig-security/annual-report-2022.md @@ -0,0 +1,107 @@ +# 2022 Annual Report: SIG Security + +## Current initiatives + +1. What work did the SIG do this year that should be highlighted? + + - + - + - + +2. What initiatives are you working on that aren't being tracked in KEPs? + + - + - + - + + + +3. KEP work in 2022 (v1.24, v1.25, v1.26): + - alpha: + - [2763 - KEP Template](https://github.com/kubernetes/enhancements/tree/master/keps/sig-security/2763-ambient-capabilities) - v1.24 + - [3203 - Auto-refreshing official CVE feed](https://github.com/kubernetes/enhancements/tree/master/keps/sig-security/3203-auto-refreshing-official-cve-feed) - v1.25 + + +## 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) + + - + - + - + +2. What metrics/community health stats does your group care about and/or measure? + + - + - + - + +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? + + - + +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? + + - + - + +## Membership + +- Primary slack channel member count: +- Primary mailing list member count: +- Primary meeting attendee count (estimated, if needed): +- Primary meeting participant count (estimated, if needed): +- Unique reviewers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files --> +- Unique approvers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files --> + +Include any other ways you measure group membership + +## [Subprojects](https://git.k8s.io/community/sig-security#subprojects) + + + +**Continuing:** + + - security-audit + - security-docs + - security-tooling + - sig-security + + +## [Working groups](https://git.k8s.io/community/sig-security#working-groups) + + +## 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 2022 are linked from [README.md] and updated/uploaded if needed +- [ ] Did you have community-wide updates in 2022 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: + - + - + +[CONTRIBUTING.md]: https://git.k8s.io/community/sig-security/CONTRIBUTING.md +[contributor ladder]: https://git.k8s.io/community/community-membership.md +[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md +[README.md]: https://git.k8s.io/community/sig-security/README.md +[sigs.yaml]: https://git.k8s.io/community/sigs.yaml +[contributor guide]: https://git.k8s.io/community/contributors/guide/README.md +[devel]: https://git.k8s.io/community/contributors/devel/README.md diff --git a/sig-storage/annual-report-2022.md b/sig-storage/annual-report-2022.md new file mode 100644 index 00000000..32e07338 --- /dev/null +++ b/sig-storage/annual-report-2022.md @@ -0,0 +1,141 @@ +# 2022 Annual Report: SIG Storage + +## Current initiatives + +1. What work did the SIG do this year that should be highlighted? + + - + - + - + +2. What initiatives are you working on that aren't being tracked in KEPs? + + - + - + - + + + +3. KEP work in 2022 (v1.24, v1.25, v1.26): + - alpha: + - [1432 - Volume Health Monitor](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/1432-volume-health-monitor) - v1.24 + - [1979 - Object Storage Support](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/1979-object-storage-support) - v1.25 + - [2644 - Honor Persistent Volume Reclaim Policy](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/2644-honor-pv-reclaim-policy) - v1.26 + - [2924 - In-tree Storage Plugin to CSI Migration - Ceph Cephfs](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/2924-csi-migration-cephfs) - v1.26 + - [3107 - SecretRef field addition to NodeExpandVolume request](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/3107-csi-nodeexpandsecret) - v1.25 + - [3294 - Provision volumes from cross-namespace snapshots](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/3294-provision-volumes-from-cross-namespace-snapshots) - v1.26 + - beta: + - [2268 - non graceful shutdown](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/2268-non-graceful-shutdown) - v1.26 + - [2589 - In-tree Storage Plugin to CSI Migration - Portworx](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/2589-csi-migration-portworx) - v1.25 + - [2923 - In-tree Storage Plugin to CSI Migration - Ceph RBD](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/2923-csi-migration-ceph-rbd) - v1.26 + - [3333 - Retroactive default StorageClass assignment](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/3333-reconcile-default-storage-class) - v1.26 + - stable: + - [1472 - Storage Capacity Constraints for Pod Scheduling](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/1472-storage-capacity-tracking) - v1.24 + - [1487 - In-tree Storage Plugin to CSI Migration - AWS](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/1487-csi-migration-aws) - v1.25 + - [1488 - In-tree Storage Plugin to CSI Migration - GCE PD](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/1488-csi-migration-gce-pd) - v1.25 + - [1489 - In-tree Storage Plugin to CSI Migration - Cinder](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/1489-csi-migration-cinder) - v1.24 + - [1490 - In-tree Storage Plugin to CSI Migration - Azuredisk](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/1490-csi-migration-azuredisk) - v1.24 + - [1491 - In-tree Storage Plugin to CSI Migration - vSphere](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/1491-csi-migration-vsphere) - v1.26 + - [1885 - In-tree Storage Plugin to CSI Migration - Azurefile](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/1885-csi-migration-azurefile) - v1.26 + - [2317 - Provide fsgroup of pod to CSI driver on mount](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/2317-fsgroup-on-mount) - v1.26 + - [284 - Growing Persistent Volume size](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/284-enable-volume-expansion) - v1.24 + - [361 - Local Ephemeral Storage Capacity Isolation](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/361-local-ephemeral-storage-isolation) - v1.25 + - [596 - Ephemeral Inline CSI Volumes](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/596-csi-inline-volumes) - v1.25 + - [625 - In-tree Storage Plugin to CSI Migration](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/625-csi-migration) - v1.25 + + +## 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) + + - + - + - + +2. What metrics/community health stats does your group care about and/or measure? + + - + - + - + +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? + + - + +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? + + - + - + +## Membership + +- Primary slack channel member count: +- Primary mailing list member count: +- Primary meeting attendee count (estimated, if needed): +- Primary meeting participant count (estimated, if needed): +- Unique reviewers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files --> +- Unique approvers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files --> + +Include any other ways you measure group membership + +## [Subprojects](https://git.k8s.io/community/sig-storage#subprojects) + + + +**Continuing:** + + - external-storage + - git-sync + - gluster-provisioner + - kubernetes-cosi + - kubernetes-csi + - mount-utils + - nfs-provisioner + - volume-populators + - volumes + + +## [Working groups](https://git.k8s.io/community/sig-storage#working-groups) + + +**Continuing:** + + - Data Protection + - Multitenancy + - Policy + - Structured Logging + +## 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 2022 are linked from [README.md] and updated/uploaded if needed +- [ ] Did you have community-wide updates in 2022 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: + - + - + +[CONTRIBUTING.md]: https://git.k8s.io/community/sig-storage/CONTRIBUTING.md +[contributor ladder]: https://git.k8s.io/community/community-membership.md +[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md +[README.md]: https://git.k8s.io/community/sig-storage/README.md +[sigs.yaml]: https://git.k8s.io/community/sigs.yaml +[contributor guide]: https://git.k8s.io/community/contributors/guide/README.md +[devel]: https://git.k8s.io/community/contributors/devel/README.md diff --git a/sig-testing/annual-report-2022.md b/sig-testing/annual-report-2022.md new file mode 100644 index 00000000..35f6647a --- /dev/null +++ b/sig-testing/annual-report-2022.md @@ -0,0 +1,118 @@ +# 2022 Annual Report: SIG Testing + +## Current initiatives + +1. What work did the SIG do this year that should be highlighted? + + - + - + - + +2. What initiatives are you working on that aren't being tracked in KEPs? + + - + - + - + + + +3. KEP work in 2022 (v1.24, v1.25, v1.26): + - beta: + - [3041 - NodeConformance and NodeFeature labels cleanup](https://github.com/kubernetes/enhancements/tree/master/keps/sig-testing/3041-node-conformance-and-features) - 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) + + - + - + - + +2. What metrics/community health stats does your group care about and/or measure? + + - + - + - + +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? + + - + +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? + + - + - + +## Membership + +- Primary slack channel member count: +- Primary mailing list member count: +- Primary meeting attendee count (estimated, if needed): +- Primary meeting participant count (estimated, if needed): +- Unique reviewers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files --> +- Unique approvers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files --> + +Include any other ways you measure group membership + +## [Subprojects](https://git.k8s.io/community/sig-testing#subprojects) + + + +**Retired in 2022:** + + - k8s-gsm-tools + +**Continuing:** + + - boskos + - e2e-framework + - kind + - kubetest2 + - prow + - sig-testing + - test-infra + - testing-commons + + +## [Working groups](https://git.k8s.io/community/sig-testing#working-groups) + + +**Continuing:** + + - Reliability + +## 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 2022 are linked from [README.md] and updated/uploaded if needed +- [ ] Did you have community-wide updates in 2022 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: + - + - + +[CONTRIBUTING.md]: https://git.k8s.io/community/sig-testing/CONTRIBUTING.md +[contributor ladder]: https://git.k8s.io/community/community-membership.md +[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md +[README.md]: https://git.k8s.io/community/sig-testing/README.md +[sigs.yaml]: https://git.k8s.io/community/sigs.yaml +[contributor guide]: https://git.k8s.io/community/contributors/guide/README.md +[devel]: https://git.k8s.io/community/contributors/devel/README.md diff --git a/sig-ui/annual-report-2022.md b/sig-ui/annual-report-2022.md new file mode 100644 index 00000000..621d8e9a --- /dev/null +++ b/sig-ui/annual-report-2022.md @@ -0,0 +1,101 @@ +# 2022 Annual Report: SIG UI + +## Current initiatives + +1. What work did the SIG do this year that should be highlighted? + + - + - + - + +2. What initiatives are you working on that aren't being tracked in KEPs? + + - + - + - + + + +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) + + - + - + - + +2. What metrics/community health stats does your group care about and/or measure? + + - + - + - + +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? + + - + +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? + + - + - + +## Membership + +- Primary slack channel member count: +- Primary mailing list member count: +- Primary meeting attendee count (estimated, if needed): +- Primary meeting participant count (estimated, if needed): +- Unique reviewers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files --> +- Unique approvers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files --> + +Include any other ways you measure group membership + +## [Subprojects](https://git.k8s.io/community/sig-ui#subprojects) + + + +**Continuing:** + + - dashboard + + +## [Working groups](https://git.k8s.io/community/sig-ui#working-groups) + + +## 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 2022 are linked from [README.md] and updated/uploaded if needed +- [ ] Did you have community-wide updates in 2022 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: + - + - + +[CONTRIBUTING.md]: https://git.k8s.io/community/sig-ui/CONTRIBUTING.md +[contributor ladder]: https://git.k8s.io/community/community-membership.md +[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md +[README.md]: https://git.k8s.io/community/sig-ui/README.md +[sigs.yaml]: https://git.k8s.io/community/sigs.yaml +[contributor guide]: https://git.k8s.io/community/contributors/guide/README.md +[devel]: https://git.k8s.io/community/contributors/devel/README.md diff --git a/sig-usability/annual-report-2021.md b/sig-usability/annual-report-2022.md index 6d2230d7..98a10afb 100644 --- a/sig-usability/annual-report-2021.md +++ b/sig-usability/annual-report-2022.md @@ -1,4 +1,4 @@ -# 2021 Annual Report: SIG Usability +# 2022 Annual Report: SIG Usability ## Current initiatives @@ -14,25 +14,10 @@ - - -3. KEP work in 2021 (1.x, 1.y, 1.z): -<!-- -In future, this will be generated from kubernetes/enhancements kep.yaml files -1. with SIG as owning-sig or in participating-sigs -2. listing 1.x, 1.y, or 1.z in milestones or in latest-milestone ---> - - Stable - - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable - - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable - - Beta - - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta - - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta - - Alpha - - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha - - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha - - Pre-alpha - - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) +3. KEP work in 2022 (v1.24, v1.25, v1.26): + ## Project health @@ -80,43 +65,17 @@ In future, this will be generated from kubernetes/enhancements kep.yaml files Include any other ways you measure group membership -## Subprojects - -<!-- -In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31 -Manually visible via `git diff HEAD@{$YYYY-01-01} HEAD@{$YYYY-12-31} -- $sig-id/README.md` ---> +## [Subprojects](https://git.k8s.io/community/sig-usability#subprojects) -New in $YYYY: -- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) -- -Retired in $YYYY: -- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) -- -Continuing: -- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) -- +**Continuing:** -## Working groups + - sig-usability -<!-- -In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31 -Manually visible via `git diff HEAD@{$YYYY-01-01} HEAD@{$YYYY-12-31} -- $sig-id/README.md` ---> -New in $YYYY: -- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) -- +## [Working groups](https://git.k8s.io/community/sig-usability#working-groups) -Retired in $YYYY: -- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) -- - -Continuing: -- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) -- ## Operational @@ -128,8 +87,8 @@ Operational tasks in [sig-governance.md]: 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: +- [ ] Meeting notes and recordings for 2022 are linked from [README.md] and updated/uploaded if needed +- [ ] Did you have community-wide updates in 2022 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: - - @@ -140,4 +99,3 @@ Operational tasks in [sig-governance.md]: [sigs.yaml]: https://git.k8s.io/community/sigs.yaml [contributor guide]: https://git.k8s.io/community/contributors/guide/README.md [devel]: https://git.k8s.io/community/contributors/devel/README.md - diff --git a/sig-windows/annual-report-2022.md b/sig-windows/annual-report-2022.md new file mode 100644 index 00000000..17fefd58 --- /dev/null +++ b/sig-windows/annual-report-2022.md @@ -0,0 +1,114 @@ +# 2022 Annual Report: SIG Windows + +## Current initiatives + +1. What work did the SIG do this year that should be highlighted? + + - + - + - + +2. What initiatives are you working on that aren't being tracked in KEPs? + + - + - + - + + + +3. KEP work in 2022 (v1.24, v1.25, v1.26): + - alpha: + - [2578 - Windows Conformance](https://github.com/kubernetes/enhancements/tree/master/keps/sig-windows/2578-windows-conformance) - v1.24 + - [3503 - Host Network Support for Windows Pods](https://github.com/kubernetes/enhancements/tree/master/keps/sig-windows/3503-host-network-support-for-windows-pods) - v1.26 + - stable: + - [1981 - Windows Privileged Container Support](https://github.com/kubernetes/enhancements/tree/master/keps/sig-windows/1981-windows-privileged-container-support) - v1.26 + - [2802 - Identify Pod's OS during API Server admission](https://github.com/kubernetes/enhancements/tree/master/keps/sig-windows/2802-identify-windows-pods-apiserver-admission) - v1.25 + + +## 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) + + - + - + - + +2. What metrics/community health stats does your group care about and/or measure? + + - + - + - + +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? + + - + +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? + + - + - + +## Membership + +- Primary slack channel member count: +- Primary mailing list member count: +- Primary meeting attendee count (estimated, if needed): +- Primary meeting participant count (estimated, if needed): +- Unique reviewers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files --> +- Unique approvers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files --> + +Include any other ways you measure group membership + +## [Subprojects](https://git.k8s.io/community/sig-windows#subprojects) + + + +**New in 2022:** + + - windows-operational-readiness + +**Continuing:** + + - windows-gmsa + - windows-samples + - windows-testing + - windows-tools + + +## [Working groups](https://git.k8s.io/community/sig-windows#working-groups) + + +## 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 2022 are linked from [README.md] and updated/uploaded if needed +- [ ] Did you have community-wide updates in 2022 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: + - + - + +[CONTRIBUTING.md]: https://git.k8s.io/community/sig-windows/CONTRIBUTING.md +[contributor ladder]: https://git.k8s.io/community/community-membership.md +[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md +[README.md]: https://git.k8s.io/community/sig-windows/README.md +[sigs.yaml]: https://git.k8s.io/community/sigs.yaml +[contributor guide]: https://git.k8s.io/community/contributors/guide/README.md +[devel]: https://git.k8s.io/community/contributors/devel/README.md @@ -1996,6 +1996,14 @@ sigs: url: https://zoom.us/j/361123509 archive_url: https://docs.google.com/document/d/1_w77-zG_Xj0zYvEMfQZTQ-wPP4kXkpGD8smVtW_qqWM/edit recordings_url: https://www.youtube.com/watch?v=phCA5-vWkVM&list=PL69nYSiGNLP2E8vmnqo5MwPOY25sDWIxb + - description: SIG Network Multi-Network Meeting + day: Wednesday + time: "08:00" + tz: PT (Pacific Time) + frequency: biweekly + url: https://zoom.us/j/95680858961?pwd=M1c2TTdMZHpMUUtIYXRpbjRobkNJZz09 + archive_url: https://docs.google.com/document/d/1pe_0aOsI35BEsQJ-FhFH9Z_pWQcU2uqwAnOx2NIx6OY/edit + recordings_url: https://www.youtube.com/watch?v=phCA5-vWkVM&list=PL69nYSiGNLP2E8vmnqo5MwPOY25sDWIxb contact: slack: sig-network mailing_list: https://groups.google.com/forum/#!forum/kubernetes-sig-network @@ -2072,12 +2080,22 @@ sigs: label: node leadership: chairs: + - github: SergeyKanzhelev + name: Sergey Kanzhelev + company: Google + - github: mrunalp + name: Mrunal Patel + company: Red Hat + tech_leads: - github: dchen1107 name: Dawn Chen company: Google - github: derekwaynecarr name: Derek Carr company: Red Hat + - github: mrunalp + name: Mrunal Patel + company: Red Hat meetings: - description: Main SIG Meeting day: Tuesday diff --git a/wg-api-expression/annual-report-2022.md b/wg-api-expression/annual-report-2022.md new file mode 100644 index 00000000..6cfe6a5f --- /dev/null +++ b/wg-api-expression/annual-report-2022.md @@ -0,0 +1,61 @@ +# 2022 Annual Report: WG API Expression + +## Current initiatives + +1. What work did the WG do this year that should be highlighted? + For example, artifacts, reports, white papers produced this year. + + - + - + - + +2. What initiatives are you working on that aren't being tracked in KEPs? + + - + - + - + +## Project health + +1. What's the current roadmap until completion of the working group? + + - + - + - + +2. Does the group have contributors from multiple companies/affiliations? + + - + +3. 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? + + - + - + +## Membership + +- Primary slack channel member count: +- Primary mailing list member count: +- Primary meeting attendee count (estimated, if needed): +- Primary meeting participant count (estimated, if needed): + +Include any other ways you measure group membership + +## Operational + +Operational tasks in [wg-governance.md]: + +- [ ] [README.md] reviewed for accuracy and updated if needed +- [ ] WG leaders in [sigs.yaml] are accurate and active, and updated if needed +- [ ] Meeting notes and recordings for 2022 are linked from [README.md] and updated/uploaded if needed +- [ ] Updates provided to sponsoring SIGs in 2022 + - [$sig-name](https://git.k8s.io/community/$sig-id/) + - links to email, meeting notes, slides, or recordings, etc + - [$sig-name](https://git.k8s.io/community/$sig-id/) + - links to email, meeting notes, slides, or recordings, etc + - + +[wg-governance.md]: https://git.k8s.io/community/committee-steering/governance/wg-governance.md +[README.md]: https://git.k8s.io/community/wg-api-expression/README.md +[sigs.yaml]: https://git.k8s.io/community/sigs.yaml diff --git a/wg-batch/annual-report-2022.md b/wg-batch/annual-report-2022.md new file mode 100644 index 00000000..e274d293 --- /dev/null +++ b/wg-batch/annual-report-2022.md @@ -0,0 +1,61 @@ +# 2022 Annual Report: WG Batch + +## Current initiatives + +1. What work did the WG do this year that should be highlighted? + For example, artifacts, reports, white papers produced this year. + + - + - + - + +2. What initiatives are you working on that aren't being tracked in KEPs? + + - + - + - + +## Project health + +1. What's the current roadmap until completion of the working group? + + - + - + - + +2. Does the group have contributors from multiple companies/affiliations? + + - + +3. 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? + + - + - + +## Membership + +- Primary slack channel member count: +- Primary mailing list member count: +- Primary meeting attendee count (estimated, if needed): +- Primary meeting participant count (estimated, if needed): + +Include any other ways you measure group membership + +## Operational + +Operational tasks in [wg-governance.md]: + +- [ ] [README.md] reviewed for accuracy and updated if needed +- [ ] WG leaders in [sigs.yaml] are accurate and active, and updated if needed +- [ ] Meeting notes and recordings for 2022 are linked from [README.md] and updated/uploaded if needed +- [ ] Updates provided to sponsoring SIGs in 2022 + - [$sig-name](https://git.k8s.io/community/$sig-id/) + - links to email, meeting notes, slides, or recordings, etc + - [$sig-name](https://git.k8s.io/community/$sig-id/) + - links to email, meeting notes, slides, or recordings, etc + - + +[wg-governance.md]: https://git.k8s.io/community/committee-steering/governance/wg-governance.md +[README.md]: https://git.k8s.io/community/wg-batch/README.md +[sigs.yaml]: https://git.k8s.io/community/sigs.yaml diff --git a/wg-data-protection/annual-report-2022.md b/wg-data-protection/annual-report-2022.md new file mode 100644 index 00000000..7c7b7570 --- /dev/null +++ b/wg-data-protection/annual-report-2022.md @@ -0,0 +1,61 @@ +# 2022 Annual Report: WG Data Protection + +## Current initiatives + +1. What work did the WG do this year that should be highlighted? + For example, artifacts, reports, white papers produced this year. + + - + - + - + +2. What initiatives are you working on that aren't being tracked in KEPs? + + - + - + - + +## Project health + +1. What's the current roadmap until completion of the working group? + + - + - + - + +2. Does the group have contributors from multiple companies/affiliations? + + - + +3. 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? + + - + - + +## Membership + +- Primary slack channel member count: +- Primary mailing list member count: +- Primary meeting attendee count (estimated, if needed): +- Primary meeting participant count (estimated, if needed): + +Include any other ways you measure group membership + +## Operational + +Operational tasks in [wg-governance.md]: + +- [ ] [README.md] reviewed for accuracy and updated if needed +- [ ] WG leaders in [sigs.yaml] are accurate and active, and updated if needed +- [ ] Meeting notes and recordings for 2022 are linked from [README.md] and updated/uploaded if needed +- [ ] Updates provided to sponsoring SIGs in 2022 + - [$sig-name](https://git.k8s.io/community/$sig-id/) + - links to email, meeting notes, slides, or recordings, etc + - [$sig-name](https://git.k8s.io/community/$sig-id/) + - links to email, meeting notes, slides, or recordings, etc + - + +[wg-governance.md]: https://git.k8s.io/community/committee-steering/governance/wg-governance.md +[README.md]: https://git.k8s.io/community/wg-data-protection/README.md +[sigs.yaml]: https://git.k8s.io/community/sigs.yaml diff --git a/wg-iot-edge/annual-report-2021.md b/wg-iot-edge/annual-report-2022.md index b6120e07..5f0b1dde 100644 --- a/wg-iot-edge/annual-report-2021.md +++ b/wg-iot-edge/annual-report-2022.md @@ -1,4 +1,4 @@ -# 2021 Annual Report: WG IoT Edge +# 2022 Annual Report: WG IoT Edge ## Current initiatives @@ -48,8 +48,8 @@ Operational tasks in [wg-governance.md]: - [ ] [README.md] reviewed for accuracy and updated if needed - [ ] WG leaders 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 -- [ ] Updates provided to sponsoring SIGs in 2021 +- [ ] Meeting notes and recordings for 2022 are linked from [README.md] and updated/uploaded if needed +- [ ] Updates provided to sponsoring SIGs in 2022 - [$sig-name](https://git.k8s.io/community/$sig-id/) - links to email, meeting notes, slides, or recordings, etc - [$sig-name](https://git.k8s.io/community/$sig-id/) @@ -59,4 +59,3 @@ Operational tasks in [wg-governance.md]: [wg-governance.md]: https://git.k8s.io/community/committee-steering/governance/wg-governance.md [README.md]: https://git.k8s.io/community/wg-iot-edge/README.md [sigs.yaml]: https://git.k8s.io/community/sigs.yaml - diff --git a/wg-multitenancy/annual-report-2021.md b/wg-multitenancy/annual-report-2022.md index 48822ea6..1185a79a 100644 --- a/wg-multitenancy/annual-report-2021.md +++ b/wg-multitenancy/annual-report-2022.md @@ -1,4 +1,4 @@ -# 2021 Annual Report: WG Multitenancy +# 2022 Annual Report: WG Multitenancy ## Current initiatives @@ -48,8 +48,8 @@ Operational tasks in [wg-governance.md]: - [ ] [README.md] reviewed for accuracy and updated if needed - [ ] WG leaders 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 -- [ ] Updates provided to sponsoring SIGs in 2021 +- [ ] Meeting notes and recordings for 2022 are linked from [README.md] and updated/uploaded if needed +- [ ] Updates provided to sponsoring SIGs in 2022 - [$sig-name](https://git.k8s.io/community/$sig-id/) - links to email, meeting notes, slides, or recordings, etc - [$sig-name](https://git.k8s.io/community/$sig-id/) @@ -59,4 +59,3 @@ Operational tasks in [wg-governance.md]: [wg-governance.md]: https://git.k8s.io/community/committee-steering/governance/wg-governance.md [README.md]: https://git.k8s.io/community/wg-multitenancy/README.md [sigs.yaml]: https://git.k8s.io/community/sigs.yaml - diff --git a/wg-policy/annual-report-2021.md b/wg-policy/annual-report-2022.md index a2399a31..fb3948d7 100644 --- a/wg-policy/annual-report-2021.md +++ b/wg-policy/annual-report-2022.md @@ -1,4 +1,4 @@ -# 2021 Annual Report: WG Policy +# 2022 Annual Report: WG Policy ## Current initiatives @@ -48,8 +48,8 @@ Operational tasks in [wg-governance.md]: - [ ] [README.md] reviewed for accuracy and updated if needed - [ ] WG leaders 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 -- [ ] Updates provided to sponsoring SIGs in 2021 +- [ ] Meeting notes and recordings for 2022 are linked from [README.md] and updated/uploaded if needed +- [ ] Updates provided to sponsoring SIGs in 2022 - [$sig-name](https://git.k8s.io/community/$sig-id/) - links to email, meeting notes, slides, or recordings, etc - [$sig-name](https://git.k8s.io/community/$sig-id/) @@ -59,4 +59,3 @@ Operational tasks in [wg-governance.md]: [wg-governance.md]: https://git.k8s.io/community/committee-steering/governance/wg-governance.md [README.md]: https://git.k8s.io/community/wg-policy/README.md [sigs.yaml]: https://git.k8s.io/community/sigs.yaml - diff --git a/wg-reliability/annual-report-2021.md b/wg-reliability/annual-report-2022.md index 923acd4e..cccca700 100644 --- a/wg-reliability/annual-report-2021.md +++ b/wg-reliability/annual-report-2022.md @@ -1,4 +1,4 @@ -# 2021 Annual Report: WG Reliability +# 2022 Annual Report: WG Reliability ## Current initiatives @@ -48,8 +48,8 @@ Operational tasks in [wg-governance.md]: - [ ] [README.md] reviewed for accuracy and updated if needed - [ ] WG leaders 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 -- [ ] Updates provided to sponsoring SIGs in 2021 +- [ ] Meeting notes and recordings for 2022 are linked from [README.md] and updated/uploaded if needed +- [ ] Updates provided to sponsoring SIGs in 2022 - [$sig-name](https://git.k8s.io/community/$sig-id/) - links to email, meeting notes, slides, or recordings, etc - [$sig-name](https://git.k8s.io/community/$sig-id/) @@ -59,4 +59,3 @@ Operational tasks in [wg-governance.md]: [wg-governance.md]: https://git.k8s.io/community/committee-steering/governance/wg-governance.md [README.md]: https://git.k8s.io/community/wg-reliability/README.md [sigs.yaml]: https://git.k8s.io/community/sigs.yaml - diff --git a/wg-structured-logging/annual-report-2022.md b/wg-structured-logging/annual-report-2022.md new file mode 100644 index 00000000..4218d521 --- /dev/null +++ b/wg-structured-logging/annual-report-2022.md @@ -0,0 +1,61 @@ +# 2022 Annual Report: WG Structured Logging + +## Current initiatives + +1. What work did the WG do this year that should be highlighted? + For example, artifacts, reports, white papers produced this year. + + - + - + - + +2. What initiatives are you working on that aren't being tracked in KEPs? + + - + - + - + +## Project health + +1. What's the current roadmap until completion of the working group? + + - + - + - + +2. Does the group have contributors from multiple companies/affiliations? + + - + +3. 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? + + - + - + +## Membership + +- Primary slack channel member count: +- Primary mailing list member count: +- Primary meeting attendee count (estimated, if needed): +- Primary meeting participant count (estimated, if needed): + +Include any other ways you measure group membership + +## Operational + +Operational tasks in [wg-governance.md]: + +- [ ] [README.md] reviewed for accuracy and updated if needed +- [ ] WG leaders in [sigs.yaml] are accurate and active, and updated if needed +- [ ] Meeting notes and recordings for 2022 are linked from [README.md] and updated/uploaded if needed +- [ ] Updates provided to sponsoring SIGs in 2022 + - [$sig-name](https://git.k8s.io/community/$sig-id/) + - links to email, meeting notes, slides, or recordings, etc + - [$sig-name](https://git.k8s.io/community/$sig-id/) + - links to email, meeting notes, slides, or recordings, etc + - + +[wg-governance.md]: https://git.k8s.io/community/committee-steering/governance/wg-governance.md +[README.md]: https://git.k8s.io/community/wg-structured-logging/README.md +[sigs.yaml]: https://git.k8s.io/community/sigs.yaml |