nitishfy
commented
4 months ago /sig contributor-experience /area contributor-summit /area na-summit
Open nitishfy opened 4 months ago
nitishfy
commented
4 months ago /sig contributor-experience /area contributor-summit /area na-summit
nitishfy
commented
4 months ago /assign
aojea
commented
2 months ago 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 https://github.com/kubernetes/community/pull/7824 and makes its consumption easier, avoiding regex and using labels. An attempt to better categorize the test was done in https://github.com/kubernetes/enhancements/pull/3042, but we need to achieve a wider consensus between SIGs and e2e consumers so we can standardize the categorization and organization of these tests. There are multiple dimensions to debate:
Moderator: @aojea, @BenTheElder , @pohly
ameukam
commented
2 months ago Topic: Issue and PR Triage with AI. Description: This is inspired by the Golang effort to use LLMs to triage issues. We could have a conversation with the community on how we explore usage LLMs to help with issue triage and minimal code review. Moderator: @ameukam (unsure at the moment)
SergeyKanzhelev
commented
2 months ago Topic: Dynamic Pods and other improvements to enhance Kubernetes for Dynamic Batch Workloads Description: Discuss the future of hierarchical scheduling and possible improvements on k8s to better support dynamic batch workloads Moderator: @SergeyKanzhelev @dchen1107 See also: https://docs.google.com/document/d/1J8Aq0XzN8BiNdWHXSEGA1Xw2nXcZRSKTMoi-tNh7FTc/edit#heading=h.nz1pdsqflie7
jberkus
commented
2 months ago 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.
Moderator: @jmhbnz, @jberkus
kad
commented
2 months ago 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
guicassolato
commented
1 month ago 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
enj
commented
1 month ago 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
dougbtv
commented
1 month ago 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
jberkus
commented
1 month ago @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.
micahhausler
commented
1 month ago 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
thockin
commented
1 month ago 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
thockin
commented
3 weeks ago 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
BenTheElder
commented
3 weeks ago re: https://github.com/kubernetes/community/issues/7993#issuecomment-2419643251
[...] Kubernetes Network Plumbing Working Group [...]
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.
... 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 https://github.com/kubernetes/community/blob/master/governance.md#working-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.
@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.
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: https://github.com/kubernetes/org/issues/new?assignees=&labels=area%2Fgithub-repo&projects=&template=repo-create.yml&title=REQUEST%3A+%3CCreate+or+Migrate%3E+%3Cgithub+repo%3E
To start, raise the possibility to the SIG Leadership.
satrox28
commented
3 weeks ago Hi Team,
I am interested in presenting the topic.
Title: Unlocking Cost Savings with Spot Instances on Kubernetes: CNCF Tools & Strategies for Resilient Workloads.
Description: Ready to maximize cloud savings without sacrificing reliability? Join this hands-on session to explore how CNCF tools like KEDA, OpenCost, and the Kubernetes Cluster Autoscaler can help you harness the power of spot instances effectively. We’ll dive into practical strategies for managing spot instance interruptions, optimizing workloads for mixed-instance pools, and scaling intelligently to minimize costs.
Thanks & Regards Sathish Kumar.V
On Tue, Oct 29, 2024 at 11:23 AM Benjamin Elder @.***> wrote:
[...] Kubernetes Network Plumbing Working Group [...]
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.
... 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
https://github.com/kubernetes/community/blob/master/governance.md#working-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.
@dougbtv https://github.com/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.
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.
— Reply to this email directly, view it on GitHub https://github.com/kubernetes/community/issues/7993#issuecomment-2445027596, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFYTJL4STCUG4EN3BQWM5XDZ57HAJAVCNFSM6AAAAABLO2Y7PKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINBVGAZDONJZGY . You are receiving this because you are subscribed to this thread.Message ID: @.***>
thockin
commented
3 weeks ago Unlocking Cost Savings with Spot Instances
This doesn't sound like a contributor-summit talk to me. Did you post this in the wrong place?
satrox28
commented
3 weeks ago Hi Tim,
Apologies, I was replying to another email, the message got swapped.
Title: Istio Ambient Mesh: Sidecarless Service Mesh Revolution
Description: Explore Ambient Mesh, a revolutionary approach to service mesh that eliminates sidecars. Discover how this model simplifies operations, enhances resource efficiency, and brings robust observability and security—all without the overhead of sidecar proxies.
On Tue, Oct 29, 2024, 4:50 p.m. Tim Hockin @.***> wrote:
Unlocking Cost Savings with Spot Instances
This doesn't sound like a contributor-summit talk to me. Did you post this in the wrong place?
— Reply to this email directly, view it on GitHub https://github.com/kubernetes/community/issues/7993#issuecomment-2445527505, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFYTJLYLIDKQLUY4FZRS4QTZ6ANMHAVCNFSM6AAAAABLO2Y7PKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINBVGUZDONJQGU . You are receiving this because you commented.Message ID: @.***>
thockin
commented
3 weeks ago I don't think that's a contrib-summit talk either
satrox28
commented
3 weeks ago Hmm ok fine.
On Tue, Oct 29, 2024, 9:47 p.m. Tim Hockin @.***> wrote:
I don't think that's a contrib-summit talk either
— Reply to this email directly, view it on GitHub https://github.com/kubernetes/community/issues/7993#issuecomment-2445838301, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFYTJL3HSUY2GGEJAZ4X4B3Z6BQGPAVCNFSM6AAAAABLO2Y7PKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINBVHAZTQMZQGE . You are receiving this because you commented.Message ID: @.***>
lauralorenz
commented
3 weeks ago 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
lauralorenz
commented
3 weeks ago 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