search

kubernetes / community

Kubernetes community content
Apache License 2.0
11.98k stars 5.17k forks source link

Unconference Topics - KCNA Contributor Summit 2023 Chicago #7531

Closed cailyn-codes closed 8 months ago

cailyn-codes commented 1 year ago

Hello friends!

Once again we will be hosting an Unconference for the Contributor Summit. We'd love to hear from you about topics in which you are interested. You can submit a topic, and upvote topics that seem interesting to you. We want to understand what is of general interest to the community, and not just for those who happen to be joining us in Chicago.

Topic: [Sample Topic Submission] Description: [Sample Topic Description] Moderator: [Will you be there in person and like to moderate? (yes or no)]

To upvote, please use the :+1: emote

Feel free to reach out to @cailynse (@cailyn_codes in Slack) for any questions.

Thank you! Cailyn Edwards, KCNA Contributor Summit 2023 Content Lead

cailyn-codes commented 1 year ago

/sig contributor-experience

chris-short commented 1 year ago

Topic: K8s Contributor Site Hackathon

Description: The Kubernetes Contributor site (K8s.dev) could use a little help updating theme and Hugo versions to more recent ones. Other folks that have ideas for the site can also come and make those suggestions as well (cough @mrbobbytables cough). Only pre-requisite is some experience with Hugo.

Moderator: @chris-short, Contributor Comms

jeremyrickard commented 1 year ago

Topic: WG-LTS: What's Next?

Description: The LTS working group has reformed, and we've also seen more discussion about extended support for Kubernetes releases. We have been discussing upgrade friction and trying to understand why users lag on using supported versions. Where should the LTS working group look next? What does LTS mean for the community?

Moderator: @jeremyrickard

jeremyrickard commented 1 year ago

Topic: The VEX-ing problem of vulnerabilities, scanners, and SBOMs

Description: If you scan Kubernetes images with scanners today, you'll likely find a number of vulnerabilities....even if they don't impact a Kubernetes release. In general, the project doesn't cherry pick things back to release branches just to silence scanners. Is there anything we can do about that? SIG Release has been producing a software bill of materials for sometime, and we'd like to discuss also producing a Vulnerability Exploitability eXchange (VEX) document. These additional documents could be used to better inform consumers of Kubernetes about vulnerabilities that exist in releases. We can also discuss changes to our SBOMs and other supply chain security artifacts to better support end users

Moderator: @jeremyrickard

qedrakmar commented 1 year ago

Topic: Helping SIGs and WGs publicize Non-Code Contributions

Description: The Non-Code contributor guide, in its current state, is 5 years old and has proven more academic that actionable. Initiatives to revisit it are in process, but the direct question here is How can we help the various SIGs and WGs to identify non-code tasks and roles and how can we elevate visibility of these things? Is this an issue of GitHub Issue tracking or is there a better way? Come to this session to help us brainstorm ways to help all the kubernetes groups make non-code roles presentable, visible, and able to be worked on.

Moderator: @qedrakmar

jpbetz commented 12 months ago

Topic: Can we improve HA Controller management?

Description: Controllers are bundled into controller-managers, and in HA configurations, only one controller manager is leader at a time, using lease based leader election. This has a few consequences: (a) controller workload cannot distributed across control plane nodes in HA configurations, (b) during the mixed-version phase of HA upgrades, the version of a controller manager running is not deterministic (it can be either the old or new version, and in pathological cases, it can flip-flop between the old and new version). All of this is a consequence of how we bundle controllers and manage leader election. We could change it. Should we consider splitting controllers into smaller groups that are leader elected independently? Should we consider alternatives to a "first to acquire the lease wins" leader election?

Moderator: @jpbetz

k8s-triage-robot commented 8 months ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

qedrakmar commented 8 months ago

The event has passed.

/close

k8s-ci-robot commented 8 months ago

@qedrakmar: Closing this issue.

In response to [this](https://github.com/kubernetes/community/issues/7531#issuecomment-1918659164): >The event has passed. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.