diff options
| -rw-r--r-- | committee-steering/governance/README.md | 2 | ||||
| -rw-r--r-- | committee-steering/governance/annual-reports.md | 2 | ||||
| -rw-r--r-- | committee-steering/governance/sig-governance.md | 5 | ||||
| -rw-r--r-- | communication/best-practices.md | 2 | ||||
| -rw-r--r-- | communication/contributor-comms/OWNERS | 4 | ||||
| -rw-r--r-- | communication/contributor-comms/README.md | 2 | ||||
| -rw-r--r-- | communication/slack-config/channels.yaml | 1 | ||||
| -rw-r--r-- | contributors/chairs-and-techleads/leadership-changes.md | 2 | ||||
| -rw-r--r-- | contributors/devel/sig-node/e2e-node-tests.md | 5 | ||||
| -rw-r--r-- | contributors/guide/contributor-cheatsheet/README.md | 2 | ||||
| -rw-r--r-- | governance.md | 8 | ||||
| -rw-r--r-- | sig-cluster-lifecycle/README.md | 4 | ||||
| -rw-r--r-- | sig-scalability/slos/pod_startup_latency.md | 5 | ||||
| -rw-r--r-- | sigs.yaml | 6 |
14 files changed, 29 insertions, 21 deletions
diff --git a/committee-steering/governance/README.md b/committee-steering/governance/README.md index 8fda6940..e75c2e5a 100644 --- a/committee-steering/governance/README.md +++ b/committee-steering/governance/README.md @@ -43,7 +43,7 @@ As part of this we will define roles for the [OARP] process (Owners, Approvers, If more substantial changes are desired it is advisable to socialize those before drafting a PR. - The steering committee will be looking to ensure the scope of the SIG as represented in the charter is reasonable (and within the scope of Kubernetes) and that processes are fair. - For large changes alert the rest of the Kubernetes community (Participants) as the scope of the changes becomes clear. - Sending mail to [dev@kubernetes.io] and/or announcing at the community meeting are a good ways to do this. + Sending mail to [dev@kubernetes.io] and (optionally) announcing it in the #kubernetes-contributors slack channel. If there are questions about this process please reach out to the steering committee at [steering@kubernetes.io]. diff --git a/committee-steering/governance/annual-reports.md b/committee-steering/governance/annual-reports.md index 84e13121..a4209cbc 100644 --- a/committee-steering/governance/annual-reports.md +++ b/committee-steering/governance/annual-reports.md @@ -201,7 +201,7 @@ Operational tasks in [sig-governance.md]: [ ] 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 $YYYY are linked from [README.md] and updated/uploaded if needed -[ ] Did you have community-wide updates in $YYYY (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: +[ ] Did you have community-wide updates in $YYYY (e.g. kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: - - diff --git a/committee-steering/governance/sig-governance.md b/committee-steering/governance/sig-governance.md index fc1e6108..81d9c514 100644 --- a/committee-steering/governance/sig-governance.md +++ b/committee-steering/governance/sig-governance.md @@ -16,9 +16,6 @@ repo [Kubernetes Community YouTube playlist] - Report activity with the community via the dev@kubernetes.io mailing list at least once a year. - - Each SIG is assigned an update during the [monthly community meeting] - throughout the year from sig-contributor-experience. The meeting host will publish the notes to the - kubernetes-dev mailing list with the update. - This is separate from the [annual report]. - Participate in release planning meetings and retrospectives, and burndown meetings, as needed @@ -115,7 +112,6 @@ Subproject contributors (as applicable). groups like SIGs and the Steering Committee but *MAY* delegate the actual communication and creation of content to other contributors where appropriate -- *MUST* provide updates through the [monthly community meeting] - *MUST* present yearly [annual report] for the group but *SHOULD* get help with curation from other SIG participants @@ -276,6 +272,5 @@ Issues impacting multiple subprojects in the SIG should be resolved by either: [Marketing Council]: /communication/marketing-team/role-handbooks/council.md [Events Lead]: /events/events-team/events-lead.md [PR Wrangler]: https://kubernetes.io/docs/contribute/participate/pr-wranglers/ -[monthly community meeting]: /events/community-meeting.md [Inclusive Open Source Community Orientation course]: https://training.linuxfoundation.org/training/inclusive-open-source-community-orientation-lfc102/ [technical-lead.md]: /contributors/chairs-and-techleads/technical-lead.md diff --git a/communication/best-practices.md b/communication/best-practices.md index 188ee00a..39cdf13c 100644 --- a/communication/best-practices.md +++ b/communication/best-practices.md @@ -94,7 +94,7 @@ procedure, see the Gmail help page on [Creating rules to filter your email]. These suggestions come largely from an old [kubernetes-dev] mailing list [thread] on Gmail filters for Kubernetes. -[kubernetes-dev]: https://groups.google.com/g/kubernetes-dev +[kubernetes-dev]: https://groups.google.com/a/kubernetes.io/g/dev [thread]: https://groups.google.com/forum/#!topic/kubernetes-dev/5qU8irU7_tE/discussion <!-- shared links --> diff --git a/communication/contributor-comms/OWNERS b/communication/contributor-comms/OWNERS index e99f2649..a18dd739 100644 --- a/communication/contributor-comms/OWNERS +++ b/communication/contributor-comms/OWNERS @@ -1,12 +1,14 @@ # See the OWNERS docs at https://go.k8s.io/owners reviewers: + - Atharva-Shinde - AvineshTripathi - chris-short - fsmunoz - imnmo - kaslin approvers: + - Atharva-Shinde - AvineshTripathi - chris-short - fsmunoz @@ -19,4 +21,4 @@ emeritus_approvers: - rajula96reddy labels: - sig/contributor-experience - - area/contributor-comms
\ No newline at end of file + - area/contributor-comms diff --git a/communication/contributor-comms/README.md b/communication/contributor-comms/README.md index fe63430f..04c3adf6 100644 --- a/communication/contributor-comms/README.md +++ b/communication/contributor-comms/README.md @@ -10,7 +10,7 @@ To better inform the Kubernetes contributor community and highlight their work t | --- | --- | --- | | Subproject Lead | @kaslin, @chris-short | Shadow role is available. | | [Social Media Coordinator](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/role-handbooks/Social-Media.md) |@kaslin | Shadow role is available. | -| [Comms Tech Lead](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/role-handbooks/Comms-Tech-Lead.md) | @imnmo | @markarranz (shadow) | +| [Comms Tech Lead](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/role-handbooks/Comms-Tech-Lead.md) | @Atharva-Shinde, @imnmo | @markarranz (shadow) | | [Comms Event Lead] | @AvineshTripathi | Shadow role is available. | | [Comms Blog Coordinator](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/role-handbooks/blog-coordinator.md) | @fsmunoz | Shadow role is available. | | [Storytellers] & other members | @hpopal11, @Atharva-Shinde | New to Contributor Comms? Add your name here! | diff --git a/communication/slack-config/channels.yaml b/communication/slack-config/channels.yaml index 238f3b7a..27f9454c 100644 --- a/communication/slack-config/channels.yaml +++ b/communication/slack-config/channels.yaml @@ -362,6 +362,7 @@ channels: - name: osbkit - name: outreachy-apps id: CDH610735 + - name: paralus - name: pharmer - name: pinniped - name: pl-users diff --git a/contributors/chairs-and-techleads/leadership-changes.md b/contributors/chairs-and-techleads/leadership-changes.md index bc0dbb78..03e1af35 100644 --- a/contributors/chairs-and-techleads/leadership-changes.md +++ b/contributors/chairs-and-techleads/leadership-changes.md @@ -35,7 +35,7 @@ lazy consensus cannot be achieved, an election should be held. SIG Contributor Experience should be contacted to assist with the administration of the election. -[kubernetes-dev]: https://groups.google.com/g/kubernetes-dev +[kubernetes-dev]: https://groups.google.com/a/kubernetes.io/g/dev [steering-private]: steering-private@kubernetes.io [member]: /community-membership.md#member [`sigs.yaml`]: /sigs.yaml diff --git a/contributors/devel/sig-node/e2e-node-tests.md b/contributors/devel/sig-node/e2e-node-tests.md index bbfbdee7..c44262c4 100644 --- a/contributors/devel/sig-node/e2e-node-tests.md +++ b/contributors/devel/sig-node/e2e-node-tests.md @@ -16,8 +16,9 @@ Prerequisites: - [Install etcd](https://github.com/coreos/etcd/releases) and include the path to the installation in your PATH - Verify etcd is installed correctly by running `which etcd` - Or make etcd binary available and executable at `/tmp/etcd` -- [Install ginkgo](https://github.com/onsi/ginkgo) and include the path to the installation in your PATH - - Verify ginkgo is installed correctly by running `which ginkgo` +- [containerd](https://github.com/containerd/containerd) configured with the cgroupfs driver +- Working CNI + - Ensure that you have a valid CNI configuration in /etc/cni/net.d/. For testing purposes, a [bridge](https://www.cni.dev/plugins/current/main/bridge/) configuration should work. From the Kubernetes base directory, run: diff --git a/contributors/guide/contributor-cheatsheet/README.md b/contributors/guide/contributor-cheatsheet/README.md index f4fd8956..0ed76794 100644 --- a/contributors/guide/contributor-cheatsheet/README.md +++ b/contributors/guide/contributor-cheatsheet/README.md @@ -387,7 +387,7 @@ git push --force [Kubernetes Code Search]: https://cs.k8s.io/ [@dims]: https://github.com/dims [calendar]: https://calendar.google.com/calendar/embed?src=calendar%40kubernetes.io -[kubernetes-dev]: https://groups.google.com/forum/#!forum/kubernetes-dev +[kubernetes-dev]: https://groups.google.com/a/kubernetes.io/g/dev [slack channels]: http://slack.k8s.io/ [Stack Overflow]: https://stackoverflow.com/questions/tagged/kubernetes [youtube channel]: https://www.youtube.com/c/KubernetesCommunity/ diff --git a/governance.md b/governance.md index 0ef27937..903abafc 100644 --- a/governance.md +++ b/governance.md @@ -166,10 +166,9 @@ user groups are documented in [sigs.yaml]. As you can see in the descriptions above, the project is robust with diverse groups of contributors and their varying degrees of expected communications. -The annual community group health check will establish an opportunity for deeper +The [annual community group health check] will establish an opportunity for deeper dialogue and broader communication across the chairs of each group and the - Steering Committee. By including this reporting with the existing community - meeting structure, we can focus on the goals outlined in the [Annual Report] doc. + Steering Committee. ## Cross-project Communication and Coordination @@ -223,6 +222,5 @@ All contributors must sign the CNCF CLA, as described [here](CLA.md). [working group governance]: /committee-steering/governance/wg-governance.md [user group governance]: /committee-steering/governance/ug-governance.md [SIG Governance Requirements]: /committee-steering/governance/sig-governance-requirements.md -[Annual Report]: /committee-steering/governance/annual-reports.md -[monthly community meeting]: /events/community-meeting.md +[annual community group health check]: /committee-steering/governance/annual-reports.md [KEP process]: https://github.com/kubernetes/enhancements/tree/master/keps#kubernetes-enhancement-proposals-keps diff --git a/sig-cluster-lifecycle/README.md b/sig-cluster-lifecycle/README.md index e7865f2d..649ce370 100644 --- a/sig-cluster-lifecycle/README.md +++ b/sig-cluster-lifecycle/README.md @@ -253,6 +253,10 @@ A project that uses Ansible / Vagrant for deploying production ready clusters on - **Contact:** - Slack: [#kubespray](https://kubernetes.slack.com/messages/kubespray) - [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-cluster-lifecycle) +### logical-cluster +A set of APIs to improve the Kubernetes user experience for cluster administration by offering utilities to interact with fleet of clusters which can be managed by Cluster API, or other entities (like cloud providers). +- **Owners:** + - [kubernetes-sigs/logical-cluster](https://github.com/kubernetes-sigs/logical-cluster/blob/main/OWNERS) ### minikube Implements a local Kubernetes cluster for application development on macOS, Linux, and Windows - **Owners:** diff --git a/sig-scalability/slos/pod_startup_latency.md b/sig-scalability/slos/pod_startup_latency.md index 84bde2fe..57611f1c 100644 --- a/sig-scalability/slos/pod_startup_latency.md +++ b/sig-scalability/slos/pod_startup_latency.md @@ -7,8 +7,9 @@ | __Official__ | Startup latency of schedulable<sup>[1](#footnote1)</sup> stateless<sup>[2](#footnote2)</sup> pods, excluding time to pull images and run init containers, measured from pod creation timestamp to when all its containers are reported as started and observed via watch, measured as 99th percentile over last 5 minutes | In default Kubernetes installation, 99th percentile per cluster-day <= 5s | | __WIP__ | Startup latency of schedulable<sup>[1](#footnote1)</sup> stateful<sup>[3](#footnote3)</sup> pods, excluding time to pull images, run init containers, provision volumes (in delayed binding mode) and unmount/detach volumes (from previous pod if needed), measured from pod creation timestamp to when all its containers are reported as started and observed via watch, measured as 99th percentile over last 5 minutes | In default Kubernetes installation, 99th percentile per cluster-day <= X where X depends on storage provider | -<a name="footnote1">[1\]</a>By schedulable pod we mean a pod that can be -scheduled in the cluster without causing any preemption. +<a name="footnote1">[1\]</a>By schedulable pod we mean a pod that has to be immediately +(without actions from any other components) schedulable in the cluster without +causing any preemption. <a name="footnote2">[2\]</a>A `stateless pod` is defined as a pod that doesn't mount volumes with sources other than secrets, config maps, downward API and @@ -1287,6 +1287,12 @@ sigs: mailing_list: https://groups.google.com/forum/#!forum/kubernetes-sig-cluster-lifecycle owners: - https://raw.githubusercontent.com/kubernetes-sigs/kubespray/master/OWNERS + - name: logical-cluster + description: A set of APIs to improve the Kubernetes user experience for cluster + administration by offering utilities to interact with fleet of clusters which + can be managed by Cluster API, or other entities (like cloud providers). + owners: + - https://raw.githubusercontent.com/kubernetes-sigs/logical-cluster/main/OWNERS - name: minikube description: Implements a local Kubernetes cluster for application development on macOS, Linux, and Windows |