Call For Unconference Topics - Kubernetes Contributor Summit North America, Salt Lake City 2024 #7993
Comments
k8s-ci-robot
added
the
needs-sig
|
/sig contributor-experience |
k8s-ci-robot
added
sig/contributor-experience
|
/assign |
|
Topic: Untangling the Kubernetes E2E test Description: The e2e tests framework is improving slowly, a new an important feature was added recently by @pohly that allows to organize better the tests #7824 and makes its consumption easier, avoiding regex and using labels. An attempt to better categorize the test was done
Moderator: @aojea, @BenTheElder , @pohly |
|
Topic: Dynamic Pods and other improvements to enhance Kubernetes for Dynamic Batch Workloads |
|
Topic: WG-Etcd-Operator Working Session Description: WG-Etcd-Operator would like to have an open working session at the KCS. We'll be working on the operator design, code, and testing. This will also be an opportunity to share the state of the operator design with the Kubernetes community. |
|
Topic: The future of native resources Description: Modern hardware changed our view on the native resources (CPU, memory). We want to talk on what and how it can be potentially improved on all levels: possible UX in Pod spec, per pod/container granularity to specify preferences, CRI API, relation to DRA, dynamic node resize, roles of kubelet and container runtimes. Moderator: @kad, @johnbelamaric |
|
Topic: Metaresources & Policy Attachment Description: Gateway API (SIG-NETWORK) introduced Policies as a declarative mechanism to enhance Kubernetes objects like Services and network extensions such as Gateways and HTTPRoutes. These Policies–more generally referred to as Metaresources–are the central piece of a pattern known as Policy Attachment, which is heading to new levels of maturity, evolving from initially an inventive way to expand solidified stable APIs, now into a new standard in the making across several networking-related implementations for contextual API extensions. This session will delve into the concept and evolution of Metaresources & Policy Attachment, exploring its goals, current state, and future potential. Moderator: @guicassolato |
|
Topic: wg-lts: proposal to increase release lifetime with regards to CVEs Description: The security releases proposal attempts to take a slightly different approach to LTS than what is traditionally discussed. Instead of trying to mark any particular Kubernetes release as LTS, it proposes that we increase the supported lifetime of all Kubernetes releases, but with only security fixes being backported after the initial 14 months. Such a change has an impact on a broad set of community members, so lets take this opportunity to discuss things in person. Moderator: @enj @jeremyrickard |
|
Topic: The lost WG: Network Plumbing Working Group Description: The Kubernetes Network Plumbing Working Group (NPWG) was formed at Kubecon US in Austin in 2017, with a goal of finding a path forward for attaching Kubernetes pods to multiple networks: that is, for multi-homed pods. The group decided to work out-of-tree and form a de-facto standard for the NetworkAttachmentDefinition custom resource, and built tooling and reference implementation that interface Kubernetes and CNI to enable advanced networking use cases and for attaching pods to multiple networks (for such use cases as network isolation and performance). The NPWG, operating under its own governance model, developed and maintains 39 GitHub repositories, ranging from wildly experimental to fully GA software – including Multus CNI (an implementation of NetworkAttachmentDefinitions), SRIOV-CNI, SRIOV device plugin, and Whereabouts IPAM CNI, among others. We'll look into the history of NPWG, what the group is working on today, and the insights the group has into the future of networking in Kubernetes and across the CNCF, especially related to the future of CNI, the multinetworking WG and DRA. We'd love to explore what it might look like to bring this group officially into the CNCF and to enable its contributors to officially serve and better collaborate with the community that it was formed around. Moderators: Doug, @LionelJouin, @shaneutt |
|
@dougbtv that feels like a discussion we'd need to have somewhere CNCF leadership is present. Like, it totally makes sense to me to make it a CNCF project -- or something? -- but I don't know what the TOC would want. And most TOC members will not be at the KCS. |
|
Topic: Consistency in api-machinery between authorization and admission Description: To secure a cluster today, admins typically grant RBAC authorization permissions and also write separate admission policies in various formats (OPA/Gatekeeper, Kyverno, Validating webhooks containing CEL) to further restrict permissions granted in authorization. Because Kubernetes performs authorization and admission checks separately, for an administrator to safely revoke a permission, they must first revoke the RBAC authorization, wait some amount of time for admission controller (such as OPA) watch caches to sync, and then remove the admission policy. In an overloaded API server if both policies were revoked simultaneously, it's possible that an identity using the RBAC rule could have a request authorized, but the validation restrictive policy would get dropped, and a request would be improperly allowed through. Moderators: @micahhausler @deads2k |
|
Topic: Being a maintainer is hard - how exactly, and how can we make it better? Description: The day-to-day, week-to-week, release-to-release job of being a maintainer of Kubernetes is hard. Perhaps unnecessarily so? In this session we can talk about what EXACTLY makes it hard, and what parts of that could be eliminated, streamlined, or delegated. We have lots of people who want to help, how can we enable them to? Where could we apply development energy to once-and-for-all overcome some of the "papercuts" that we all live with. Moderators: @thockin @BenTheElder |
|
Topic: Test code is real code - it needs to be good, too Description: I often see test code which is "not quite as polished" as the "real" code. Every PR should come with tests, but few people have the incentives to clean up tests. We are all guilty of "just adding one more case to the table", without considering the bigger picture. The harder a test is to comprehend, the more likely it is that the test itself is broken. In this session we will discuss some strategies for simpler, more maintainable tests. Moderators: @thockin |
|
re: #7993 (comment)
... have you all proposed a Kubernetes Community Workgroup? We have a well established formal concept of a Kubernetes Working Group: https://github.com/kubernetes/community/blob/master/governance.md#community-groups This is a bit off-topic for the thread, but I think it might be more productive to follow established paths async and/or join the SIG Network meetings.
If this were to become a CNCF level organization and not Kubernetes level, I'd at least expect a different name, "Kubernetes [...] Working Group" at the very least has a major naming collision with the project's own organization. ... but regardless, I agree that the Kubernetes Contributor Summit is unlikely to have the right people for discussing CNCF adoption of projects. SIG Network could agree to host some of the projects under the Kubernetes organization, but that's also another conversation with an established path: "Repository creation/migration" issue type in github.com/kubernetes/org has more details: To start, raise the possibility to the SIG Leadership. |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
|
Topic: E2E node test coverage Description: Working session to collate and analyze current node E2E test coverage against key node features to, in priority order:
The output of this working session is a doc containing the working session's findings to be shared to SIG-Node. Moderator: TBD, co-presented by @SergeyKanzhelev |
|
Topic: Pod lifecycle and related code health Description: Begins with a short interest and feedback session to collect and socialize gaps in pod lifecycle management today. Followed by a working session to enumerate specific gaps in documentation and tests relating to the pod lifecycle, and brainstorm, including how to evaluate for feasibility, architectures to unify the state transition flow of pod lifecycle management (ref: state transition). The output of this working session is
Moderator: @lauralorenz (yes I am attending in person) |
Hello friends!🌎
We're excited to host an Unconference at this year's Kubernetes Contributor Summit in Salt Lake City, Utah! Your input is crucial in making this event a success, so we'd love to hear from you about the topics you're passionate about. You can submit a topic and upvote the ones that catch your interest. Our goal is to capture what the community is most interested in, whether you're attending in person or participating remotely.
Topic: [Submit your topic here]
Description: [Provide a brief description]
Moderator: [Are you attending in person and willing to moderate? (yes or no)]
To upvote topics, please use the 👍 emote.
For any questions, feel free to reach out to me (nitish on Slack).
Thank you for your contributions!
Nitish Kumar, KCNA Contributor Summit 2024 Content Lead
SESSION NOTES CAN BE FOUND HERE: k8s.dev/summit/notes
The text was updated successfully, but these errors were encountered: