Kubernetes Contributors – Documentation

Events: Kubernetes Meet and Greet

Thu, 01 Jan 2026 00:00:00 +0000

About

Grab your lunch and come join the Kubernetes Meet and Greet! This event is for SIGs and WGs, new and experienced contributors. We will have representatives from many SIG / WG to answer questions and talk more about how to get involved.

The Kubernetes M&G is for both:

Experienced Kubernetes contributors who are interested in expanding their involvement in new SIGs / WGs, or just hanging out with their SIG/WG collaborators.
New contributors who are looking for where they can contribute to Kubernetes

Details

The Kubernetes Meet and Greet will take place on Wednesday, March 25, from noon to 3pm, in the Europe Foyer.

Instructions for New Contributors

Please grab your lunch in the main exhibit hall. Then proceed over to the Europe Foyer, enter the room, and look for one or more SIGs, WGs, or other teams that seem like something you’ll be interested in. Sit down, and ask them about their SIG/WG.

Note that SIGs and WGs will share tables, with more than one at a table. If you have trouble finding the group you want, there will be a volunteer from SIG-Contrbutor Experience to guide you to the right table.

Instructions for SIG Members and Current Contributors

Please grab your lunch in the main exhibit hall. Then proceed over to the Europe Foyer, enter the room, and look for your SIG/WG, or the one where you want to discuss contributions.

It may be that you are the first member of your SIG/WG to arrive. In that case, take the sign and the bag of SIG pins and find an empty table, or a table with sufficient space for another SIG to join. When all members of your SIG depart, please pack up the pins and sign, and return them to ContribEx.

SIG members are not expected to stay the entire 3 hours. Instead, pick a period of one to two hours where you can staff the table.

Events: Maintainer Summit Europe 2026

Thu, 01 Jan 2026 00:00:00 +0000

About

The European edition of the Maintainer Summit will take place on Sunday, March 22, 2026, in Amsterdam, Netherlands, alongside KubeCon + CloudNativeCon Europe 2026.

The Summit is a dedicated day for maintainers to collaborate in person. The event will feature:

Submitted Talks: Technical deep dives and project health updates.
Unconference Sessions: Open-space discussions for spontaneous problem-solving and SIG alignment.
Documentation Sprint: A collaborative session focused on improving project resources.
Contributor Social: An evening of games and networking following the technical tracks.

📅 Schedule & Participation

Volunteer & Staffing: If you are interested in volunteering or staffing for this event, please see kubernetes/community#8819.
Call for Proposals (CFP): Check the event schedule for submission deadlines.
Registration: Register here.

Eligibility

Who can attend Maintainer Summit?

Sandbox Project Maintainers
Incubating Project Org Members
Graduated Project Org Members
CNCF TOC Members
CNCF TAG Chairs, Technical Leads and Working Group Leads

For more information, please visit the official event page.

🤝 Code of Conduct

Attendees agree to abide by the Kubernetes Code of Conduct. To report an incident, please reach out to the CNCF event staff.

Community: 2019 Awards

Mon, 01 Jan 0001 00:00:00 +0000

By Special Interest Group (SIG)

SIG Cloud Provider

Lubomir Ivanov

SIG Instrumentation

Han Kang

SIG Release

Katharine Berry

SIG Scheduling

Huang Wei

SIG Storage

Michelle Au

SIG Windows

Jordan Liggitt

WG Multitenancy

Ryan Bezdicek

Community: 2020 Awards

Mon, 01 Jan 0001 00:00:00 +0000

By Special Interest Group (SIG)

API Machinery

Haowei Cai
Chao Xu

Architecture

Hippie Hacker
Michelle Au
Dawn Chen
Paris Pittman

Authentication

Shihang Zhang

CLI

Yao Zhou
Brian Pursely
Syam Sundar Kirubakaran

Cloud Provider

Cici Huang

Contributor Experience

Matthew Broberg
Kaslin Fields
Noah Kantrowitz
Rajula Vineet Reddy

Cluster Lifecycle

Ciprian Hacman
John Gardiner Myers
Ole Markus

Documentation

Tim Bannister
Qiming Teng
Zachary Sarah Corleissen

Instrumentation

Hongcai Ren
Lili Cosic
Marek Siarkowicz

Network

Antonio Ojea
Jay Vyas

Release

Joyce Kung
Daniel Mangum

Scheduling

Aldo Culquicondor

Storage

Patrick Ohly

Testing

Antonio Ojea
Daniel Magnum

Usability

Gaby Moreno Cesar
Carl J Pearson
Josie Pynadath

Windows

James Sturtevant

Community: 2021 Awards

Mon, 01 Jan 0001 00:00:00 +0000

By Special Interest Group (SIG) with listed message/nomination reason

API Machinery

Han Kang, @logicalhan
For their continued contributions related to the overlap with SIG Instrumentation.

Antoine Pelisse
For their long term effort and leadership on server-side-apply and the related wg-api-expression.

Apps

Aldo Culquicondor
For improving the jobs controller, expanding its functionality

Architecture

Riaan Kleinhans
Conformance Work

Madhav Jivrajani
KEP Reading Club

Kirsten Garrison, @kikisdeliveryservice
Enhancements Subproject

Elana Hashman, @ehashdn
Production Readiness Reviews

Autoscaling

Wayne, @wangyysde
Promoting the HPA v2 API to GA after being in beta for more than 3 years.

CLI

Natasha Sarkar
Maintaining Kustomize

Paco Xu
Holding down the APAC timezone for SIG-CLI by triaging and organization issues.

Chok Yip Lau
Shipped backlogged bug fixes and features requested by the community.

Cluster-lifecycle

Cecile Robert-Michon
Long time Cluster API leader, maintainer, and active contributor

Paco Xu
Great contributor in the kubeadm sub-project, helping in multiple areas and onboarding new contributors

Contributor-experience

Josh Berkus, @jberkus
Paris Pittman, @parispittman
Thank you both for being a rock, and always willing to step up and help with the works that needs doing <3

Docs

Natali Vlatko, @natalisucks
Helping to shape the localization subproject efforts

Arsh Sharma, @RinkiyaKeDad
Helping to form the new contributor ambassador role

Instrumentation

Damien Grisonnet
Work on core Kubernetes metrics, triage, bringing great ideas to SIG discussions, and thorough, detailed reviews.

Patrick Ohly
Stepping up to assist with the structured logging migration and adopting, coordinating, and completing an instrumental amount of work.

Multicluster

Laura Lorenz
Outstanding contributions pushing the ClusterProperty and Multicluster services projects forward with cross SIG collaboration.

Network

Antonio Ojea, @aojea
For always volunteering for the dirtiest jobs and demonstrating an exemplary leadership attitude.

Kal Henidak
For keeping an eye on the ideal future, and trying hard to make it happen one step at a time.

Node

Elana Hashman, @ehashdn
Driving broad community participation, improving and sustaining the health of SIG Node CI, helping new contributors.

Sergey Kanzhelev, @sergeykanzhelev
Driving broad community participation, improving and sustaining the health of SIG Node CI, helping new contributors.

Mrunal Patel, @mrunalp
New maintainer in the SIG Node kubelet sub-project and coordinating release feature goals.

Release

Karen Chu
For stepping up to be the 1.23 communications lead, reaching all deadlines in the 1.23 release cycle, and mentoring shadows that could succeed as communications lead in 1.24 and beyond.

Jesse Butler
For stepping up to be the 1.22 communications lead as a first time shadow and stepping up to be the 1.23 docs lead without release docs experience, reorienting the incoming communication lead, and for being a great mentor.

Nabarun Pal
For being a huge impact in SIG Release as the lead for the 1.21 release, as a release manager associate, as a branch manager shadow for the 1.23 release, for bringing the CI Signal tool into a Kubernetes community repository, and for being willing to contribute to the success of the project and the SIG.

Rey Lejano
For being a consistent contributor to SIG Release for some time across many releases and roles. When the 1.23 Release came around, he volunteered to lead the release when we were unable to identify a release lead.

Scalability

Wojciech Tyczyński
Outstanding cross-SIG work working on P&F and Efficient watch resumption which required cross-SIG collaboration and were large contributions to multiple Kubernetes releases.

Security

Savitha Raghunathan, @coffeeartgirl
Pushkar Joglekar, @PuDiJoglekar
Building a welcoming, encouraging community for new and experienced contributors, for being great examples on how we help each other grow, for seeing what needs to be done and putting in the work to do it while bringing others along.

Scheduling

Mike Dame
Leading the descheduler project, leading the refactoring effort to cut unneeded dependencies, for designing and implementing a new simplified scheduler plugin configuration API.

Storage

Hemant Kumar, @gnufied
Working on difficult bugs, long-standing reliability issues such as uncertain mounts, and slow mounts due to recursive fsgroup and fixing issues in order to move the volume expansion feature to GA

Jiawei Wang
Driving the CSI migration effort that has been ongoing for several releases and hosting meetings and working with maintainers across many cloud providers to move in-tree volume plugins to out-of-tree CSI drivers.

Testing

Arnaud Meukam, @ameukam
k8s-infra prow and migrating scalability jobs

Chao Dai
Automating prow updates

Claudiu Belu
Migrating Kubernetes to k8s.gcr.io/e2e-test-images

UI

Sebastian Florek
Marcin Maciaszczyk
Both of their efforts maintaining Kubernetes Dashboard for over five years and keeping the Kubernetes Dashboard project healthy and secure

Usability

Cleopatra Enjeck
Helping SIG Usability operationalize how the SIG weighs feedback in the jobs-to-be-done study and helping the SIG make progress in analyzing the results of the study

Josie Pynadath
Interviewing and collecting results for SIG Usability’s study

Carl J. Pearson, @carljpearson
Creating and presenting a framework on how to “code” results from the jobs-to-be-done study that enables new contributors

Windows

Ravi Gudimetla
Established and runs the weekly SIG Windows CI/Triage meeting and for cross-SIG collaboration to get a new OS field added to Pod specs (alpha in v1.23) which will help solve many SIG Windows related issues such as being able to enforce OS specific policies during admission time.

Amim Knabben, @ak_ndb
Improving the developer experience for Windows related changes in Kubernetes which eases the on-ramp of developers to be involved with SIG Windows.

Community: 2022 Awards

Mon, 01 Jan 0001 00:00:00 +0000

By Special Interest Group (SIG) with listed message/nomination reason

API Machinery

Joe Betz, @jpbetz
For his leadership and contributions introducing CEL as a powerful feature for Kubernetes, and leading the strategy and execution of all the subsequent projects like CRD Validation, Admission Control, and more to come.

Antonio Ojea, @aojea
For the long list of sustained contributions, especially for the cross-over from networking to apimachinery/client-go, picking up bug fixes, backports, and code reviews.

Apps

Aldo Culquicondor, @alculquicondor
Aldo continues working on the job controller improving its functionality coming from wg-batch, and fixing long-standing issues with calculating pods, among other things.

Architecture

Kirsten Garrison, @kikisdeliveryservice
Kirsten has been advocating for better enhancements process for a while now. She has been able to build a band of folks along with sig-release folks to roll out a new process for 1.26 which will make life much easier for everyone

Riann Kleinhans, @Riaankl
Riann has been leading the charge to close the gap in our conformance test suite which assures end users that the kubernetes distribution works as expected. Due to his leadership we are very close to paying down the debt on our older APIs.

Patrick Ohly, @pohly
Patrick has been awesome across multiple fronts in code organization. He’s especially led updates to klog and how we get to structured logging across kubernetes code base

Auth

Anish Ramasekar, @aramase
For driving KMS v2alpha1 and maintaining the Secrets Store CSI Driver subproject

CLI

Arda Güçlü, @ardaguclu
Arda joined SIG CLI at the end of 2021 and almost from the beginning caught our attention by being very diligent and patient proposing fixes and improvements to kubectl. Since then he grew into a valued member of our SIG, and is currently a member of our reviewers cohort, on the path to becoming a reviewer.

Cluster Lifecycle

Stefan Büringer, @sbueringer
We love Stefan because he is not only an amazing contributor, but also such a lovely and nice person that truly represent the spirit of this community by being relentless in trying to help people, on every issue, PR, slack thread, always providing valuable and constructive feedback. Thanks Stefan for all your hard work and enjoy this well deserved award!

Contributor Experience

Marky Jackson, @markyjackson-taulia
For stepping up to do the unglamorous but necessary work of community management

Nabarun Pal, @palnabarun
For driving continuous improvement of community github administration

Docs

Shannon Kularathna, @shannonxtreme
For high-quality contributions, both to content and processes, across SIG Docs and achieving reviewer status

Seokho Son, @seokho-son
For consistently leading and maintaining the Korean Localization

Anubhav Vardhan, @anubha-v-ardhan
For leading the launch of the Hindi Localization, our first using the Devanagari script

Yung-Hsiang Wei, @Sea-n
For achieving reviewer status on the Chinese Localization team and continued contributions to SIG Docs English PRs

Instrumentation

Patrick Ohly, @pohly
For their continued contributions to WG Structured Logging and for driving the contextual logging effort

Sally O’Malley, @sallyom
For driving the kubelet tracing effort and sticking with it through a years-long review process

K8s Infra

Caleb Woodbine, @BobyMCbobs
For his critical role in building the AWS infrastructure of registry.k8s.io and other efforts in sig-k8s-infra.

Network

Antonio Ojea, @aojea
Antonio is prolific, invariably helpful, and consistently volunteers to take on the hardest, dirtiest problems. He values quality and reliability, and strives to make sure that every PR makes the project better. He exemplifies the idea of “maintainer”, and lifts up everyone who has the opportunity to work with him.

Node

Vinay Kulkarni, @vinaykul
For driving long standing and complicated in-place pod vertical autoscaling project

Danielle Lancashire, @endocrimes
For driving broad community participation and coordinating SIG Node CI project

Brian McQueen, @xmcqueen
For improving and sustaining the health of SIG Node CI

Mrunal Patel, @mrunalp
For driving broad community participation and coordinating release feature goals

David Porter, @bobbypage
Driving several critical initiatives including cgroup v2 and graceful node shutdown

Release

Lauri Apple, @lappleapple
Lauri has been instrumental in helping to organize the SIG Release roadmap and continues to play an important part in helping SIG Release focus and deliver. She welcomes new contributors, seeks to unblock stalled efforts, and above all has helped to ensure that critical initiatives make forward progress. Thank you Lauri for shaping the future of our SIG!

Verónica López, @verolop
Verónica is a phenomenal Release Manager and has served as the branch manager for several releases, most recently Kubernetes 1.23 and Kubernetes 1.25. During both of these releases, she also served as a mentor for a Branch Manager Shadow and ensured that they were empowered to learn and able to take up the role for the next release. A special thanks to you Verónica for continuously driving our release machine!

Marko Mudrinić, @xmudrii
Marko is a profound current Release Manager and has been a long term contributor to SIG Release. We want to recognize his dedication to the project and to the success of SIG Release. He has balanced university and his contributions to the SIG and always brings a valuable perspective to the table when we are addressing issues. Thank you Marko for your outstanding efforts within our community!

Scalability

Maciek Borsz, @mborsz
For outstanding contributions to SIG Scalability

Security

Cailyn Edwards, @cailynse
Cailyn has done a stellar job in making SIG Security related artifacts better through their hands on expertise and review comments! Cailyn has also brought in new contributors into the community and made the group richer through their valuable contributions!

Robert Ficcagilia, @rficcaglia
For oustanding contributions to SIG Security with the third-party security audit subproject and Cluster API security self-assessment

Rory McCune, @raesene
Rory is a thought leader and an amazing example of how to be inclusive, share knowledge in public and improve the project through community collaboration. This is one of those cases where Kubernetes Org is lucky that Rory would like to be its member

Mahé Tardy, @mtardy
Mahé as been a regular member of SIG Security and a repeat contributor on Kubernetes security related issues and PRs. He has also presented a learning session to the community on an opensource pentest tool - kdigger that he co-created!

Scheduling

Kensei Nakada, @sanposhiho
For being a top contributor in scheduler, making continuous and diligent work on PR reviews, issue triaging, KEP design/impl., as well as maintaining some of sig-scheduling sub-projects. We hope to use this chance to thank their efforts to the community.

Kante Yin, @kerthcet
For being a top contributor in scheduler, making continuous and diligent work on PR reviews, issue triaging, KEP design/impl., as well as maintaining some of sig-scheduling sub-projects. We hope to use this chance to thank their efforts to the community.

Storage

Jing Xu, @jingxu97
Jing Xu worked on many projects in SIG Storage, including GA features such as CSI Volume Snapshots and CSI Windows, etc. Most recently in 1.25, she moved Local Storage Capacity Isolation to GA. Jing has been helping with hosting CSI Implementation meetings, tracking features in Kubernetes releases, reviewing KEPs and PRs, as well as fixing bugs such as mount issues.

Andy Zhang, @andyzhangx
Andy Zhang is the maintainer of CSI drivers for Azure Disk and Azure File. He made sure CSI Migration for Azure in-tree plugins are progressing as planned. He is also a maintainer of the SMB and NFS CSI Drivers. In addition, he helps fixing CI issues in the CSI spec repo by introducing GitHub actions and helps catching vulnerability issues in the CSI sidecars.

Testing

Dave Chen, @chendave
For the huge Kubernetes e2e test ginkgo v2 migration

Michelle Shepardson, @michelle192837
For helping run the SIG: a huge help running meetings, organizing the SIG annual report etc

Antonio Ojea, @aojea
For the huge Kubernetes e2e test ginkgo v2 migration

Patrick Ohly, @pohly
For the huge Kubernetes e2e test ginkgo v2 migration

Eddie Zane, @eddiezane
For helping run the SIG: a huge help running meetings, organizing the SIG annual report etc

UI

Cédric de Saint Martin, @desaintmartin
For outstanding contributions to SIG UI

Windows

Aravindh Puthiyaparambil, @aravindhp
For continued participation in bug triage, backlog grooming, and all of the work on done for the node service log viewer enhancement.

Community: 2023 Awards

Mon, 01 Jan 0001 00:00:00 +0000

By Special Interest Group (SIG) with listed message/nomination reason

API Machinery

Mike Spreitzer, @MikeSpreitzer
For his continued contributions and relentless effort in designing, leading, implementing, and refining priority and fairness for the kube-apiserver.

Jeffrey Ying, @Jefftree
For his design and implementation work for aggregated discovery which improves all discovering clients for his design and implementation work for aggregated discovery which improves all discovering REST clients.

Apps

Michał Woźniak, @mimowo
Michał has been consistently contributing improvements and fixes to the job controller to improve its usage in various batch workloads.

Filip Křepinský, @atiratree
Filip has been consistently helpful in various tasks throughout the SIG Apps portfolio. He’s working hard to promote several features forward, is putting a lot of effort into reviewing PRs across the board and finally he’s always helpful and open to other community members.

Architecture

Wojciech Tyczynski, @wojtek-t
wojtek has been on point and taking really good care of ongoing business for reviewing PRR(s) for a while now. The PRR program is extremely important to ensure that we as a community spend enough time thinking about readiness of new enhancements being proposed and how it will affect the millions of workloads/users that will need to update to newer versions we roll out.

Mark Rossetti, @marosset
Github project for K8s enhancement tracking.

Grace Nguyen, @gracenng
Github project for K8s enhancement tracking.

Priyanka Saggu, @Priyankasaggu11929
Github project for K8s enhancement tracking.

Autoscaling

Kensei Nakada, @sanposhiho
“Kensei picked up a feature which had languished in alpha for an extended period (container resource metrics autoscaling), and drove the work required to graduate it to beta. This included significant improvements in the observability of the HPA controller metrics for all users, not just for adopters of the new functionality. Their hard work was entirely responsible for this feature making it to beta, and being in a position to be graduated to stable in the near future, despite not having worked with SIG Autoscaling before. Kensei’s work here was a glowing example of seeing a problem and proactively solving it for all users of k8s.”

CLI

Marly Puckett, @mpuckett159
Marly has been helping with SIG-CLI for several months, tackling almost impossible problems (like jsonpath support for config, kuberc among many others). For the past several months she’s also been active and recently taking over leading our monthly bug scrubs.

Yugo Kobayashi, @koba1t
Yugo volunteered for our Kustomize training cohort a few months back. Since then he’s been actively helping answer questions, fixing bugs and being a great community member. Recently, he was also promoted to be one of the kustomize maintainer.

Cloud Provider

Joel Speed, @JoelSpeed
Joel has dug into complex problems to create workable cross-provider solutions, and always writes clear and thorough issues and explanations.

Cluster Lifecycle

Michael McCune, @elmiko
Mike embodies the heart and soul of the Cluster API community, he is a wonderful host of many of our meetings, and the tireless driving force behind many initiatives and discussions

Killian Muldoon, @killianmuldoon
Killian deserves this nomination for his tireless work to improve and stabilize the project’s E2E tests, creating a solid foundation for implementing exciting new features in the upcoming releases

Joe Kratzat, @joekr
Joe led the Cluster API release team for V1.5.0 to ship an awesome release and set the bar for being a great mentor and a model for all the contributors involved in this effort. Well done!

Furkat Gofurov, @furkatgofurov7
Furkat is leading the release team for Cluster API v1.6.0 with energy and passion, consistently improving the project’s release machinery while mentoring and empowering all the contributors involved in this effort

Contributor Experience

Avinesh Tripathi, @AvineshTripathi
For outstanding contributions to the Contributor Comms Team

Chris Short, @chris-short
For your enthusiastic and tenacious support of comms across the Kubernetes Project

Nigel Brown, @pnbrown
Doing (and then automating!) the invisible work that keeps the project going.

Frederico Muñoz, @fsmunoz
For being an absolute boss of a Comms blogging lead and showing us all how coordinating many projects and contributors at once is done.

Docs

Mauren Berti, @stormqueen1990
For their leadership of the Portuguese localization of Kubernetes docs, and their contributions to improving the localization process for all teams and languages

Nate Waddington, @nate-double-u
For their mentorship across release docs tasks and reviews to help with the Kubernetes Blog

Instrumentation

Richa Banker, @Richabanker
Richa has made significant contributions to SIG Instrumentation, driving forward the Component SLI KEP as well as Kubelet Resource Metrics (not to mention her cross-SIG activity in API-Machinery via work on the MVP KEP).

K8s Infra

Mahamed Ali, @upodroid
Mahamed has been a machine (see his github profile image!) churning out stuff to help us in sig-k8s-infra enabling us to stand up and use both existing infrastructure based on GCP and new infra we have been standing up on AWS. Helping out with kops based harness(es) and chipping away on arm64 test suites as well. His knowledge of our infra is remarkable and has helped us immensely.

Marko Mudrinić, @xmudrii
Marko has been an outstanding asset in standing up new infrastructure using our new AWS credits. He has been a liaison with sig-release as well, working on really difficult problems in both spaces. How best to deploy/maintain the infra as well as use it efficiently and frugally. With his guidance we have been able to move release artifacts over to our fastly CDN as well (after building them on OBS).

Ricky Sandowski, @rjsadow
Ricky is a role model for how to engage with the community, building trust, digging deep, learning things and ramping up quickly. Ricky has helped with moving test CI jobs over to new infrastructure, making sure they are healthy, keeping track of how far we got and encouraging others as well in the mission.

Network

Rob Scott, @robscott
Rob has been essential to the success of Gateway API, helping to found it and working tirelessly in the years since to bring it to GA. Without Rob this year’s GA release wouldn’t have been possible, and we deeply appreciate his contributions!

Nick Young, @youngnick
Nick has been critical to the development of Gateway API, and his efforts have led it to be the vibrant and successful community project that it is today. We greatly appreciate the long hours spent meticulously building Gateway API, and helping to shape the future of Kubernetes!

Lars Ekman, @uablrek
Lars is always present, highly technical and knowledgeable and is often found deep in the Kubernetes machinery. He is crucial to keeping the deeper technical parts of Kubernetes moving forward. Lars’ contributions and his commitment to the community is profoundly appreciated!

Dan Winship, @danwinship
Dan’s deep insights and technical expertise are foundational for Kubernetes. Dan is both a contributor to the code, and a mentor to us all. We appreciate the tremendous impact he has on the community and the technology!

Andrew Stoycos, @astoycos
Andrew has had a profound impact on Kubernetes: He’s worked on many different projects throughout the community (including his tireless efforts on Network Policy) but is also a benefactor to all those in need. We are extremely thankful to have him building the tech while always supporting others along the way!

Node

Ed Bartosh, @bart0sh
For the tireless and continuous pull request reviews and triage for SIG Node

Paco Xu, @pacoxu
For continuous contributions to SIG Node and representing SIG Node at KubeCon China 2023

Release

Marko Mudrinić, @xmudrii
We would like to recognize Marko for his work migrating the Kubernetes release process to the use of the Open Build Service for producing deb and rpm packages. The release process had a long-standing dependency on Google for final publishing and signing of deb and rpm packages, which over time became a risk to the continued release cadence of the project. Marko led a proof of concept of this new capability, worked to integrate it seemlessly into our release process, and coordinated communications for an accelerated cutover away from the Google produced packages. We now produce and distribute packages using only community managed infrastructure and are closer to relying only on community managed infrastructure within the project.

Kat Cosgrove, @katcosgrove
“We would like to recognize Kat Cosgrove, for her work on the Release Team since Kubernetes v1.23, and for her collaboration across multiple SIGs within the Kubernetes community. In particular, we’d like to highlight Kat’s outstanding work during the v1.28 release cycle. The Release Team is responsible for synthesizing inputs across multiple community groups to ensure that we can ship a high-quality and on-time release to our users. Kat noticed a gap in our reporting, escalated the issue, and then stepped up to help manage that section’s responsibilities in close partnership with our friends in SIG Docs to ensure we could release. Her consistency and follow-through in being an active participant in the release retrospectives, filing her findings, and improving process documentation for the Release Team should help to ensure that we can better manage release status reporting for all of our releases to come!”

Security

Rey Lejano, @reylejano
For the third-party audit, especially the post-audit follow-up, and so many other things across SIGs

Ashish Malik, @ashish493
For detailed and and collaborative work on the SIG Security Docs hardening guide

Kris Nóva, @krisnova
For so much Kubernetes security work, especially work that was done anonymously or was uncredited. We see you, we love you, and we miss you

Scheduling

Shiming Zhang, @wzshiming
Shiming is co-founder of the Kubernetes sub-project KWOK, which has garnered immense popularity as a toolkit for rapidly simulating Kubernetes clusters with thousands of nodes in just seconds. His dedication to this project has played a pivotal role in elevating its status within the community. I would like to express my heartfelt gratitude to him for his tremendous contributions to our community.

Yuki Iwai, @tenzen-y
For becoming a maintainer of the Kueue subproject, after multiple contributions in code, designs and reviews.

Storage

Humble Devassy Chirammal, @humblec
Humble Devassy Chirammal introduced the alpha feature NodeExpandSecret in Kubernetes 1.25 and moved it to beta in the 1.27 release, and is now working on moving it to GA in the 1.29 release. He has been a maintainer for Ceph RBD and CephFS in-tree plugins and announced the deprecation of them in 1.28 while advising users to move to CSI drivers. He has been helping with various bug fixes in SIG Storage and doing work to facilitate the CSI sidecar releases. He also signed up for the mentoring program and guided mentees with upstream contributions in SIG Storage.

Ben Swartzlander, @bswartz
Ben Swartzlander originally introduced the Volume Populators alpha feature in Kubernetes 1.18 release, redesigned it in1.22, and moved it to beta in 1.24 release. As an approver of the CSI spec, he has been providing thoughtful feedback to various features getting added to CSI. He contributed to design discussions of many SIG Storage features and has been an active participant in the Kubernetes Data Protection WG.

Testing

Mahamed Ali, @upodroid
For consistent, cross-SIG work and communication to improve K8s testing and its reliability.

Davanum Srinivas, @dims
For consistent, cross-SIG work and communication to improve K8s testing and its reliability.

Windows

Daman Arora, @aroradaman
Daman has done a tremendous amount of work fixing low level windows-service-proxy bugs and testing it on different provider infrastructures, to help prove out, as a POC an out-of-tree implementation of the Windows Kernelspace proxy. This has the potential to make windows networking easier to reason about and maintain.

Tatenda Zifundi, @tzifudzi
Tatenda has lead the operational-readiness improvements and standardization for sig-windows over the last quarter. He has worked on behalf of his company to build a brighter and more transparent future for Kubernetes on Windows, defining what it means to be a Windows cluster for sig-windows, and the broader community at large. This will give us a more uniform and consistent set of user expectations for K8s users on different OS’s in the future.

Kulwant Singh, @KlwntSingh
Kulwant has led the storage and webhook aspects of making windows e2e tests perform consistently across multiple clouds as part of his commitment to working with the windows operational-readiness team towards the standardization of the definition of Kubernetes on Windows, without his efforts, our broader windows standardization goals would be hard, if not impossible, to achieve.

Community: 2024 Awards

Mon, 01 Jan 0001 00:00:00 +0000

By Special Interest Group (SIG) with listed message/nomination reason

API Machinery

Marek Siarkowicz, @serathius
Marek’s contributions to the Consistent Reads from Cache project over the past few years have been truly inspiring. This initiative required deep expertise in both etcd and Kubernetes, coupled with a steadfast determination to see it through to completion. Marek’s work has led to one of the most significant scalability improvements in recent years. Without his dedication and skill, this achievement would not have been possible.

Lukasz Szaszkiewicz, @polynomial
@polynomial for his work on streaming lists. It’s been a long road producing new API mechanics, designing drop-in compatible clients to leverage the new construct, and building new feature gating mechanisms to control enablement. Great job making a feature in a way that our ecosystem can adopt.

Architecture

Stephen Heywood, @heyste
For outstanding dedication and exceptional long term contributions to the Kubernetes Conformance Program

CLI

Maciej Szulik, @soltysh
Maciej spends significant amount of time to review all PRs, KEPs in sig-cli and one of the key persons for the progress.

Cluster Lifecycle

Fan Baofa, @carlory
Various kubeadm contributions. becoming a reviewer of the project.

Christian Schlotter, @chrischdi
Various contributions to Cluster API and Cluster API vSphere provider. acting as reviewer and approver of the projects.

Max Gautier, @VannTen
Various contributions to kubespray: support for installing helm charts, CI improvements, bootstrap-os refactoring, fine grained OS packages installation, cleanup of PodSecurityPolicy support, others.

Contributor Experience

Jason Braganza, @jasonbraganza
For single-handedly holding the fort of Kubernetes New Org Memberships for close to a year now. Jason has demonstrated exceptional diligence, thoroughness, care and compassion in reviewing NMC requests, consistently flagging issues and initiating discussions for careful decision-making, and our GitHub org is safer for it. Thank you, Jason!

Mario Fahlandt, @mfahlandt
For tackling important technical challenges for the Comms & LWKD teams and for leading KCSNA 2024.

Sreeram Venkitesh, @sreeram-venkitesh
For boosting so many messages both to and about our contributors, and taking on and mastering many new comms tasks.

Noah Kantrowitz, @coderanger
For doing all the little tasks to keep contributor systems running.

Sandeep Kanabar, @sandeepkanabar*
For outstanding contributions to the KCS and SIG ContribEx Comms teams. Sandeep went above and beyond to pick up tasks and learn to lead comms as a shadow for KCSNA24.

Arvind Parekh, @ArvindParekh*
For outstanding contributions to the KCS and SIG ContribEx Comms teams. Arvind went above and beyond to pick up tasks and learn to lead comms as a shadow for KCSNA24.

Docs

Dipesh Rawat, @dipesh-rawat
For his awesome journey in advancing through the SIG Docs contributor ladder, where he has now become a regular approver and reviewer for the Kubernetes Documentation community. His expertise in web development and localization, alongside his great application of the Kubernetes documentation guidelines for other SIGs, has been exemplary for those wishing to become leaders in the project.

Abigail McCarthy, @a-mccarthy
For her stewardship of the Localization subproject, where she has been able to guide new language teams and improve processes for existing teams. SIG Docs leads have been able to let the Localization subproject run independently thanks to the leadership of Abbie and her co-owner, Seokho. She has set a high bar for leadership across SIG Docs for current and promising subproject owners.

SIG etcd

Ivan Valdes, @ivanvc
Ivan has been extremely active across a number of etcd-io subprojects since getting involved with the project 12 months ago at our ContribFest in Chicago in November 2023 and has helped take sig-etcd tooling to another level. Ivan adding to your code & review contributions we are deeply appreciative of your focus on helping other community members and being active in our regular community and triage meetings, thank you for all your hard work.

Siyuan Zhang, @siyuanfoundation
Siyuan has been making crucial contributions to some of our most important roadmap items for etcd, both within the etcd-io repository but also across a number of kubernetes subprojects relating to etcd. Siyuan the amount of progress you’ve contributed towards etcd 3.6 since your first pr just over a year ago is extraordinary. Thank you for your help towards making etcd 3.6 a reality and helping to bridge the divide between Kubernetes and etcd. Your efforts on livez/readyz, downgrades and etcd feature gates are making a huge difference.

Wei Fu, @fuweid
Fu Wei has demonstrated extraordinary knowledge in crucial areas of etcd and bbolt. They were instrumental in landing etcd’s extremely complex upgrade from grpc gateway from v1 to v2 and creating our new robustness testing suite for bbolt.

Instrumentation

Catherine Fang, @catherineF-dev
Catherine has easily been one of the most prominent contributors in Kube State Metrics since her involvement from the v2.6.0 release (August, 2022). Since then, she has not only unblocked us on various fronts by contributing crucial patches, but also been an excellent all-rounder, keeping the tooling and documentation in shape, as well as actively seeking out issues that affect the community, and addressing them timely. She has helped out with 204 pull request to date, while driving 34 pull requests of her own.

Manuel Rüger, @mrueg
Manuel has landed 144 pull requests to date, with patothes entailing major features, as well as keeping the release machineTV in shape which enabled him to deliver new releases ofn time. He has been active in the project since v1.5.0 (January, 2019), and been a major help ever since (involved in reviewing ~555 pull requests) Kube State Metrics could never have gotten to the pedestal which it is on today without his efforts.

K8s Infra

Ricky Sandowski, @rjsadow
Drive an huge effort to migrate our prowjobs to the community infrastructure

Marko Mudrinić, @xmudrii
Ensure a transparent and robust integration between our CI and AWS.

Multicluster

Mike Morris, @mikemorris
For significant contributions to shaping both the Multi-Cluster Service API and the new Cluster Inventory project, and for being a consistently active participant in the sig-multicluster community.

Network

Quan Tian, @tnqn
Quan made a bunch of great contributions this year, and was added as a reviewer. We really appreciate him jumping in to help, and look forward to continuing to work with him. Thank you Quan!

Daman Arora, @aroradaman
Daman came from the KPNG project over to core to help out with in-tree kube-proxy, and has been deeply involved in the maintenance and future direction ever since. Thank you Daman!

Maciej Skrocki, @mskrocki
As a sub-project lead Maciej has been tirelessly pushing forward the multi-network sub-project for a couple of years now, and we want to recognize him for his dedication as we expect many will benefit from this work in the coming years. Thank you Maciej!

Dave Protasowski, @dprotaso
Dave has been a prolific contributor to the Gateway API sub-project. Not only does he have a lot of commits in the main repository, but he’s also been personally involved (and commonly drives) on many of our Gateway API enhancement proposals. Thank you for your dedication Dave!

Node

Peter Hunt, @haircommander
In recognition of your longstanding contributions and unwavering commitment to continuous improvement initiatives.

Francesco Romani, @ffromani
In recognition of prolonged contributions in the domain of resource management, unwavering commitment, and persistent endeavors towards continuous enhancements.

Release

Meha Bhalodiya, @mehabhalodiya
We would like to recognize Meha for her work as a branch manager. Meha has been very hands on with all of the release cut activities and has been very proactive with communication across multiple timezones and goes out of her way to offer to share her knowledge.

Vyom Yadav, @Vyom-Yadav
Vyom has gone above and beyond in supporting the new Release Signal sub team over the last few releases. Thank you for your dedication, Vyom.

Scalability

Harish Kuna, @hakuna-matatah
Harish helped ramp up Kubernetes scalability testing on AWS to 5000-node cluster by working closely with SIG testing. This helps distribute the cost of scale-testing and the responsibility of ensuring scalability readiness of Kubernetes releases across cloud providers. He also strives to maintain the health of these jobs and improve test coverage.

Prateek Gogia, @prateekgogia
Prateek played a foundational role in enabling scalability tests on AWS by ensuring the right capabilities/configurations are in place with our tooling (kops, test-infra).

Justin Santa Barbara, @justinsb
Prateek played a foundational role in enabling scalability tests on AWS by ensuring the right capabilities/configurations are in place with our tooling (kops, test-infra).

Scheduling

Sheng Zhan, @AxeZhan
For working on several important features, refactors and bug fixes around scale and for being an active participant in SIG discussions.

Security

Anshuman Tripathi, @AnshumanTripathi
For tenacious curiosity: researching the most obscure kube-scheduler arcana and writing it up in a way that never existed before. Because of your work, we have all levelled up.Thank you for learning and working in community so we all benefit!

Ala Dewberry, @aladewberry
For excellent leadership of Self Assessments: teaching people and SIGs to create security threat models for themselves, and attracting new contributors along the way. Your ambition and enthusiasm to take on the subproject lead role and learn by doing is an example for us all.

Storage

Baofa Fan, @carlory
Baofa is a relatively new contributor in SIG Storage. He has made lots of contributions since he started to contribute to SIG Storage in K8s 1.28 release. He has helped with CSI sidecar releases, adding e2e tests, fixing bugs, doing code cleanup, and helped with development for multiple features, including Non-Graceful Node Shutdown, Volume Attributes Class, Always Honor Reclaim Policy, CSI Migration, etc. At the time of this writing, he has authored more than 100 PRs. He has also been helping with reviews and contributing to other SIGs including sig-testing and sig-scheduling.

Raunak Shah, @RaunakShah
Raunak has been contributing to SIG Storage for a while. He has helped with CSI sidecar releases, fixing bugs, and adding e2e tests. He designed and implemented a feature that addressed a potential security problem by preventing unauthorized volume mode conversion and eventually moved it to GA. He also made major contributions in bringing the VolumeGroupSnapshot feature to Alpha.

Windows

Ritika Gupta, @ritikaguptams
Ritika has been a tremendous help in migrating the SIG-Windows test passes to the community infra clusters!

Community: 2025 Awards

Mon, 01 Jan 0001 00:00:00 +0000

By Special Interest Group (SIG) with listed message/nomination reason

API Machinery

Aaron Prindle, @aaron-prindle
Aaron has been a driving force behind the new declarative validation framework in Kubernetes. His leadership and technical contributions to KEP-5073, which introduces validation-gen, have been instrumental in moving Kubernetes API validation from complex, handwritten Go code to a more maintainable and author-friendly declarative model. Over the last year, Aaron’s work has established the foundational infrastructure for this transition, including the creation of the validation-gen code generator. This work significantly lowers the barrier for new contributors and improves the overall quality and consistency of the Kubernetes API, making it a more robust and accessible project for the entire community.

Joel Speed, @JoelSpeed
We are pleased to nominate Joel Speed for his valuable contributions to the kube-api-linter project. This tool is essential for ensuring the quality and consistency of Kubernetes-style APIs, and Joel’s recent work has been vital to its continued improvement. His contributions over the last year have helped enhance the linter’s capabilities, making it easier for developers to identify and correct issues in their custom resources and controllers. Joel’s dedication to improving the tooling around API development demonstrates a strong commitment to the health of the broader Kubernetes ecosystem and helps developers build better, more reliable extensions for Kubernetes.

Yongrui Lin, @yongruilin
We nominate Yongrui for his significant and detailed contributions to the implementation of declarative validation in Kubernetes. Working closely on KEP-5073, Yongrui has been pivotal in the hands-on development and refinement of the validation-gen tool and its integration into the Kubernetes codebase. His numerous commits over the past 12 months reflect a deep commitment to improving the API validation process. Yongrui’s technical diligence and collaborative efforts have been crucial in turning the vision of a declarative validation system into a tangible reality, directly impacting the future maintainability and stability of the Kubernetes API.

Architecture

Patrick Ohly, @pohly
Tireless and extraordinary efforts to bring DRA to GA over several years.

Auth

Taahir Ahmed, @ahmedtd
Significant contributions to Kubernetes certificate trust distribution and issuance to pods.

Standa Láznička, @stlaz
Significant contributions to Kubernetes image pull security.

Harshal Neelkamal, @HarshalNeelkamal
Significant contributions to Kubernetes external service account token signing.

Autoscaling

Adrian Moisey, @adrianmoisey
Outstanding project maintainer (VPA) and Kubernaut omnivore.

Omer Aplatony, @omerap12
Outstanding project maintainer (VPA) and HPA resurrector.

Cluster Lifecycle

Bing Hongtao, @HirazawaUi
HirazawaUi has excelled at being a new kubeadm contributor for SIG Cluster Lifecycle. HirazawaUi climbed the contributor ladder of being first a reviewer and then an approver very fast, while actively reviewing new PRs and participating in important discussions.

Takuma Shibuya, @sivchari
We are happy to use this opportunity to recognize Takuma for being always available to help and for the impact he made in the Cluster API project.

Contributor Experience

Arpit Agrawal, @Hii-Arpit
Arpit has been meaningfully contributing to the Contributor Comms team for years now. This year, he has particularly stepped up to explore running his own video project. He’s created a variety of types of content and built on what he’s learned to help others by presenting the New Contributor Orientation content at local community events. Thank you, Arpit, for your contributions to the community!

Sayak Mukhopadhyay, @SayakMukhopadhyay
For driving the long-overdue Hugo/Docsy upgrade on the Kubernetes contributor site and fixing local website previews to improve the contributor workflow.

Docs

Sayak Mukhopadhyay, @SayakMukhopadhyay
For his excellent work in aligning the Kubernetes website with upstream Docsy, which has required continuous refactors and upgrades. Sayak’s expertise has been extremely needed to make our documentation more robust, and he has proceeded whilst ensuring we’re on the latest environment and dependency versions, all while continuing to support our docs throughout the constant changes we experience during each release cycle.

Graziano Casto, @graz-dev
For his helpful work on the Kubernetes Blog, which has led him to become a co-maintainer of our blog in a helpful, efficient, and kind manner. Graziano’s reviews for authors are well-received, and he has generally mastered our blog guidelines to become a definitive authority within our small SIG Docs Blog team, which was sorely needed. We’re incredibly grateful for Graziano’s step-up into blog maintainer for the SIG.

SIG etcd

Joshua James, @joshjms
Joshua documented the process for bumping etcd versions in Kubernetes, has been working toward unifying etcd image management in Kubernetes, and has contributed to various project chores such as release and dependency updates.

Nont Thanonchai, @nwnt
Nont’s work has been critical to improving etcd’s robustness and correctness. As the primary contributor behind the Antithesis testing effort, he helped uncover serious issues—including a bug where a watch on a future revision could receive past events. His focus on discovering subtle, complex problems has had a lasting positive impact on etcd’s reliability.

Instrumentation

Yongrui Lin, @yongruilin
Yongrui is recognized again, this time by SIG Instrumentation, for his careful work fixing critical bugs, improving documentation, and strengthening tests across instrumentation features. His diligence has improved both stability and clarity for users of Kubernetes observability components.

Network

Surya Seetharaman, @tssurya
Surya has been a key contributor to SIG Network for many years. Her design work and leadership around Network Policy, both technically and within the community, are a major reason the feature stands where it does today. Her sustained commitment and expertise have been central to the SIG’s success.

Adrian Moisey, @adrianmoisey
Adrian has recently become a driving force within SIG Network, bringing fresh energy and a willingness to dive into some of the hardest problems in core networking. His enthusiasm and work on complex issues have energized the community and moved important efforts forward.

Lionel Jouin, @LionelJouin
Lionel has spent years pushing the boundaries of what Kubernetes networking can do. His constant exploration of new ideas and innovative approaches has helped the SIG grow and evolve, lifting the entire community’s ambitions along the way.

Node

Tim Allclair, @tallclair
Tim is recognized for his substantial contributions to the In-Place Resize beta as well as many other initiatives over the years. His long-standing dedication to SIG Node has had a meaningful impact across the project.

Bing Hongtao, @HirazawaUi
Bing is also celebrated by SIG Node for his work fixing critical bugs, building new features, and driving testing for evented PLEG to evaluate its viability. His efforts have directly improved Kubernetes node reliability and feature velocity.

Kevin Hannon, @kannon92
Kevin has been instrumental in developing and maintaining SIG Node’s test infrastructure, carefully shepherding KEPs, and contributing across a wide range of initiatives. His broad, dependable contributions make a big difference to the SIG’s ability to move forward confidently.

Release

Matteo Bianchi, @mbianchidev
Matteo has gone above and beyond as a Release Branch Manager. He significantly improved and streamlined Release Engineering documentation, created detailed technical checklists, and successfully shepherded another release cut on a tight schedule. His continued efforts keep the release process smoother and more predictable.

Scalability

Alay Patel, @alaypatel07
Alay was key to building scalability tests for Dynamic Resource Allocation, ensuring that DRA could reach GA with confidence in Kubernetes 1.34. His work helps guarantee that new features meet the scale and reliability expectations of large deployments.

Scheduling

David Grove, @dgrove-oss
David has delivered impactful improvements in Kueue to address real-world issues. He led KEP-3589, which gives cluster admins better control over Kueue’s management namespace, and KEP-2937, which makes resource transformations configurable and lays the groundwork for more flexible workload estimation. His efforts have significantly expanded Kueue’s capabilities.

Jiang Zhenyu (CY Jiang), @googs1025
CY Jiang has made numerous contributions to the Kubernetes scheduler and has also been active in related projects such as descheduler and scheduler-plugins. His steady stream of improvements across these components has been invaluable to SIG Scheduling.

Storage

Drew Sirenko, @AndrewSirenko
Drew Sirenko has been a key contributor to the VolumeAttributesClass feature, developing and refining it through comprehensive end-to-end testing and diligent bug fixes, significantly enhancing its stability and functionality. He has also supported Kubernetes CSI sidecar releases, addressing and resolving bugs to improve the reliability of Kubernetes Storage.

Sunny Song, @sunnylovestiramisu
Sunny has led the design and implementation of the VolumeAttributesClass feature, a major enhancement targeted for GA in Kubernetes 1.34, coordinating with multiple cloud providers and storage vendors. She was also instrumental in bringing volume populators to GA in Kubernetes 1.33. In addition, she continues to support CSI sidecar releases and tackle important bug fixes, further strengthening Kubernetes storage capabilities.

WG etcd-operator

Arka Saha, @ArkaSaha30 Arka has led the development of the key feature for etcd-operator version 0.2, certificate management, and has continued mentoring security feature development.

Abdur Rehman, @abdurrehman107 Abdur launched the E2E test suite for etcd-operator, enabling the first release of the operator as well as anchoring future test work.

Events: How to Join

Mon, 01 Jan 0001 00:00:00 +0000

Notice

This event has passed. Recordings from the event can be found on the Kubernetes Community YouTube Channel.

The celebration and all the activities will all take place on the official Kubernetes Discord server with major events being streamed to the Kubernetes YouTube Channel.

Register for the event

Invites will be sent to people that register on Thursday, December 10th. If you register after that date, an invite will be sent shortly after you’ve signed up.

Look for an email sent from the contributors@kubernetes.io account with the subject line: Kubernetes Contributor Celebration Invite.

Connecting to Discord

Create and verify your account

For instructions on creating an account and installing the client, see the official instructions. They include instructions for multiple platforms.

Connecting to the server

After you login to Discord, click on the Add a server button (The + symbol) on the left side of the application.

A menu should pop up asking if you’d like to create or join a server. Select Join a server.
Copy the invite link from the “Kubernetes Contributor Celebration Invite” email, and paste it in the Invite link text box.
Two things will happen: You will be directed to the #instructions-to-connect channel and you will receive a DM from our bot YAGPDB.xyz. The #instructions-to-connect channel contain the next steps to finish joining the server.
The bot will dm you a unique link where you will need to complete a captcha.

NOTE: If you did not get a dm from the bot, right click on the bot name (@YAGPDB.xyz), and select message. That will take you to the correct prompt.

If you do not complete the captcha within 10 minutes, you will be booted from the server (you will still be able to reconnect).
After completing the captcha, navigate to the #code-of-conduct channel. There you will need to read and agree to the Code of Conduct by clicking on the Kubernetes emoji. This must be done before you can access any other channels within the server.

Once you accept the Code of conduct, you will see a list of categories and channels on the left side of the app. We have set up existing channels for popular games and activities, if you’re not interested in something you can collapse that entire section in the sidebar.

Note: Unlike Slack you can see every channel, and every user on the server! This is normal. The workflow is that you can see everything, but choose the categories you’re interested in and mute the others.

Tips and suggestions for using Discord

Managing audio

You have full control of your incoming audio! You can right click on a person in the voice room and individually assign a user volume to them. This is handy since not everyone has the same microphone and some people might be too loud, and some might be too soft. If you’re expecting to play with a group for a long time this can help tremendously:

Once you’ve joined a voice channel you can use the widgets at the bottom left of the screen to share your own screen and to use video if you want:

The Voice connected text and signal meter will change depending on your internet connection. Sometimes hanging up (clicking the phone icon with the X on it) and rejoining the voice channel is useful if you have a bad connection.

Troubleshooting your audio/video settings

If your audio or video is having an issue, you may need to alter the voice or video settings.

Begin by clicking on the cog next to your Discord username in the lower left corner:
Navigate to the Voice & Video section of the User Settings to adjust your inputs and outputs.

If you are continuing to have problems, check our FAQ or see the official Discord Voice and Video Troubleshooting Guide

Where to get help

First, please check the FAQ. You can find it both here on the contributor site, and within Discord itself in the Info and Announcements Category.

If you’re problem was not covered in the FAQ, you can reach out for help in the #Help channel under the Info and Announcements Category.

Events: How to Join

Mon, 01 Jan 0001 00:00:00 +0000

Notice

This event has passed. Recordings from the event can be found on the Kubernetes Community YouTube Channel.

The celebration and all the activities will all take place on the official Kubernetes Discord server with major events being streamed to the Kubernetes YouTube Channel.

Register for the event

Invites will be sent to people that register closer to the event.

Look for an email sent from the contributors@kubernetes.io account with the subject line: Kubernetes Contributor Celebration Invite.

Connecting to Discord

Create and verify your account

For instructions on creating an account and installing the client, see the official instructions. They include instructions for multiple platforms.

Connecting to the server

After you login to Discord, click on the Add a server button (The + symbol) on the left side of the application.

A menu should pop up asking if you’d like to create or join a server. Select Join a server.
Copy the invite link from the “Kubernetes Contributor Celebration Invite” email, and paste it in the Invite link text box.
Two things will happen: You will be directed to the #instructions-to-connect channel and you will receive a DM from our bot YAGPDB.xyz. The #instructions-to-connect channel contain the next steps to finish joining the server.
The bot will dm you a unique link where you will need to complete a captcha.

NOTE: On desktop clients, if you did not get a dm from the bot, right click on the bot name (@YAGPDB.xyz), and select message. That will take you to the correct prompt. On the web client, you need to click the “Home” server in the upper left corner in order to see the bot’s message.

If you do not complete the captcha within 10 minutes, you will be booted from the server (you will still be able to reconnect).
After completing the captcha, navigate to the #code-of-conduct channel. There you will need to read and agree to the Code of Conduct by clicking on the Kubernetes emoji. This must be done before you can access any other channels within the server.

Once you accept the Code of conduct, you will see a list of categories and channels on the left side of the app. We have set up existing channels for popular games and activities, if you’re not interested in something you can collapse that entire section in the sidebar.

Note: Unlike Slack you can see every channel, and every user on the server! This is normal. The workflow is that you can see everything, but choose the categories you’re interested in and mute the others.

Tips and suggestions for using Discord

Managing audio

Troubleshooting your audio/video settings

If your audio or video is having an issue, you may need to alter the voice or video settings.

Begin by clicking on the cog next to your Discord username in the lower left corner:
Navigate to the Voice & Video section of the User Settings to adjust your inputs and outputs.

If you are continuing to have problems, check our FAQ or see the official Discord Voice and Video Troubleshooting Guide

Where to get help

First, please check the FAQ. You can find it both here on the contributor site, and within Discord itself in the Info and Announcements Category.

If you’re problem was not covered in the FAQ, you can reach out for help in the #Help channel under the Info and Announcements Category.

Resources: Services and Requests

Mon, 01 Jan 0001 00:00:00 +0000

GitHub requests

Organization membership

Kubernetes GitHub Org members should be actively contributing to the upstream project, and should meet the general requirements outlined in the community membership guidelines.

Org membership requests can be made using the Org Membership Request form in the kubernetes/org repo. Requests are often processed in batch once every 2-3 business days.

NOTE: If you are an existing member of the kubernetes org, you are not required to apply for org membership in another Kubernetes org, such as kubernetes-sigs. Instead, open a pull request to the kubernetes/org repo adding yourself a member of the other org.

Team membership

GitHub team membership changes should be made by directly opening a pull request against the kubernetes/org repo, updating the desired team.

Repo requests

GitHub requests such as repo creation, migration, or archival can be made using one of the issue templates in the kubernetes/org repo.

Repo requests require approval from the owning SIG leads, or in some instances, community members that are granted permission to request repos on behalf of a subproject.

Donated repos, or repos that were originally created outside the project have some additional requirements that must be satisfied before they can be transferred to a Kubernetes project owned GitHub organization.

For more information, see the Kubernetes GitHub Repository Guidelines.

Communication platform and services

Contributor communications

Contributor communication requests, such as tweets from @K8sContributors, blog posts, editorial support, promotion requests, or announcements can be made by filling out the Contributor Comms Request form in the kubernetes/community repo.

Mailing lists

Mailing lists are largely intended for community groups, but are available for subprojects if the need arises. These groups should be made following the community mailing list creation procedure. With the subproject’s entry in sigs.yaml, being updated with the new mailing list.

Slack

Public Slack channels and user groups may be requested by opening a pull request updating the slack-config in the kubernetes/community repo. Slack channels must adhere to some common-criteria to be added. As an example, project focused channels must be for an Open Source project and not a private commercial one.

Other Slack requests, such as for private channels or integration requests should be through the Slack Request form in the kubernetes/community readme.

For more information, see the Slack Guidelines.

Surveys

The Kubernetes project has access to the CNCF SurveyMonkey account for creating community surveys, and SIG-Contributor Experience includes people who can give advice on improving the quality of surveys, as well as promote them. Requests can be made using the Community Survey Request form in the kubernetes/community repo.

For additional information, on survey services, see the community Survey request guidelines.

YouTube

YouTube playlists or upload requests can be made to the YouTube admin team, by pinging @youtube-admins in the SIG ContribEx Slack channel.

For more information, see the YouTube guidelines.

Zoom

Zoom meetings requests should be made to the owning community group leads. They are responsible for the creation and posting of the meeting to the group’s mailing list.

For more information, see the Kubernetes Zoom guidelines.

If you need further assistance, you can open an issue in the kubernetes/community repo, or ping the @zoom-admins in the SIG ContribEx Slack channel.

Other

Netlify websites

Official Kubernetes subprojects can request a domain and site hosting for their project specific documentation. The Kubernetes community has standardized on Netlify for this purpose.

Requesting a site requires three things:

Configuring a site and it’s corresponding config within the repo.
Opening a Netlify Site Request in the kubernetes/org repo.
Opening a corresponding pull request or issue adding the domain in the kubernetes/k8s.io repo.

There are some specific formats and guidelines around some of these items, they can be be reviewed in the Netlify subproject site guidelines.

Funding

Need to pay for something on behalf of the Kubernetes Project? Funding requests can be made by opening an issue in the kubernetes/funding repo using one of the available issue templates.

Items that are covered fall largely into one of four categories:

Infrastructure: testing infra, video conferencing, mailing lists, domains, etc
Events: SIG face-to-face meetings, developer summits, etc
Consulting services: docs writers, security auditors, etc
Community Gifts: swag codes, thank you cards, etc

For more information on funding requests, see the Project Funding page.

Docs: Contributor Cheatsheet

Mon, 01 Jan 0001 00:00:00 +0000

Kubernetes Contributor Cheat Sheet

A list of common resources when contributing to Kubernetes, tips, tricks, and common best practices used within the Kubernetes project. It is a “TL;DR” or quick reference of useful information to make your GitHub contribution experience better.

Table of Contents

Helpful Resources

Getting Started

Contributor Course - NEW - The E-Learning for Contributors course for Kubernetes!
Contributor Guide - Guide on how to begin contributing to Kubernetes Project.
Developer Guide - Guide to contributing code directly to the Kubernetes Project.
Security and Disclosure Information - Guide for reporting vulnerabilities and the security release process.

SIGs and Other Groups

Master Group List

Community

Calendar - View all the Kubernetes Community events (SIG/WG meetings, events etc.)
kubernetes-dev - The Kubernetes development mailing list
Kubernetes Forum - Official Kubernetes forum.
Slack channels - Official Kubernetes Slack.
Stack Overflow - A place to ask your Kubernetes end-user questions.
YouTube Channel - Official channel for the Kubernetes community.

Workflow

Prow - Kubernetes CI/CD System.
Tide - Prow plugin that manages merges and tests. Tide Dashboard
Bot commands - Commands used to interact with Kubernetes Bots (examples: /cc, /lgtm, and /retest)
GitHub labels - List of labels used throughout the Kubernetes Project
Kubernetes Code Search, maintained by @dims

Tests

Prow - Kubernetes CI/CD System.
Test Grid - View historical tests and their associated information.
Triage Dashboard - Aggregates similar failures together for better troubleshooting.

Important Email Aliases

community@kubernetes.io - Mail someone on the community team (SIG Contributor Experience) about a community issue.
conduct@kubernetes.io - Contact the Code of Conduct committee, private mailing list.
github@kubernetes.io - Mail the GitHub Administration Team privately, for sensitive items.
steering@kubernetes.io - Mail the steering committee. Public address with public archive.
steering-private@kubernetes.io - Mail the steering committee privately, for sensitive items.
social@cncf.io - Contact the CNCF social team; blog, twitter account, and other social properties.

Communicating Effectively on GitHub

How to be Excellent to Each Other

As a first step, familiarize yourself with the Code of Conduct.

Examples of Good/Bad Communication

When raising an issue, or seeking assistance, please be polite with your request:

🙂 “X doesn’t compile when I do Y, do you have any suggestions?”

😞 “X doesn’t work! Please fix it!”

When closing a PR, convey an explanatory and cordial message explaining why it does not meet the requirements to be merged.

🙂 “I’m closing this PR because this feature can’t support the use case X. In its proposed form, it would be better to implement with Y tool. Thank you for working on this.”

😞 “Why isn’t this following the API conventions? This should be done elsewhere!”

Submitting a Contribution

Signing the CLA

Before you can submit a contribution, you must sign the Contributor License Agreement(CLA). The Kubernetes project can only accept a contribution if you or your company have signed the CLA.

Should you encounter any problems signing the CLA, follow the CLA troubleshooting guidelines.

Opening and Responding to Issues

GitHub Issues are the primary means of tracking things such as bug reports, enhancement requests, or reporting other issues such as failing tests. They are not intended for user support requests. For those, please check with the troubleshooting guide, report the problem to Stack Overflow, or follow up on the Kubernetes forum.

References:

Creating an Issue

Use an issue template if one is available. Using the correct one will aid other contributors in responding to your issue.
- Follow any directions described in the issue template itself.
Be descriptive with the issue you are raising.
Assign appropriate labels. If you are unsure, the k8s-ci-robot bot (Kubernetes CI bot) will reply to your issue with the needed labels for it to be effectively triaged.
Be selective when assigning issues using /assign @<username> or /cc @<username>. Your issue will be triaged more effectively applying correct labels over assigning more people to the issue.

Responding to an Issue

When tackling an issue, comment on it letting others know you are working on it to avoid duplicate work.
When you have resolved something on your own at any future time, comment on the issue letting people know before closing it.
Include references to other PRs or issues (or any accessible materials), example: “ref: #1234”. It is useful to identify that related work has been addressed somewhere else.

Opening a Pull Request

Pull requests (PR) are the main means of contributing code, documentation or other forms of work that would be stored within a git repository.

References:

Creating a Pull Request

Follow the directions of the pull request template if one is available. It will help those who respond to your PR.
If a trivial fix such as a broken link, typo, or grammar mistake, review the entire document for other potential mistakes. Do not open multiple PRs for small fixes in the same document.
Reference any issues related to your PR, or issues that PR may solve.
Avoid creating overly large changes in a single commit. Instead, break your PR into multiple small, logical commits. This makes it easier for your PR to be reviewed.
Comment on your own PR where you believe something may need further explanation.
Be selective when assigning your PR with /assign @<username>. Assigning excessive reviewers will not yield a quicker PR review.
If your PR is considered a “Work in progress” prefix the name with [WIP] or use the /hold command. This will prevent the PR from being merged till the [WIP] or hold is lifted.
If you have not had your PR reviewed, do not close and open a new PR with the same changes. Ping your reviewers in a comment with @<github username>.
If your PR isn’t getting enough attention, post a link to the PR in the #pr-reviews channel on Slack to find additional reviewers.

Example PR Description

Ref. #3064 #3097
All files owned by SIG testing were moved from `/devel` to the new folder `/devel/sig-testing`.
/sig contributor-experience
/cc @stakeholder1 @stakeholder2
/kind cleanup
/area developer-guide
/assign @approver1 @approver2 @approver3

What’s in that PR:

Line 1 - Reference to other issues or PRs (#3064 #3097).
Line 2 - A brief description of what is being done in the PR.
Line 4 - SIG assignment with the command /sig contributor-experience.
Line 5 - Reviewers that may have interest in this specific issue or PR are specified with the /cc command.
Line 6 - The /kind cleanup command adds a label that categorizes issues or PR as related to cleaning up code, process, or technical debt.
Line 7 - The /area developer-guide command categorizes issue or PR as related to the developer guide.
Line 8 - The command /assign assigns an approver to the PR. An approver will be suggested by the k8s-ci-robot and is selected from the list of owners in the OWNERS file. They will add the /approve label to the PR after it has been reviewed.

Troubleshooting a Pull Request

After your PR is proposed, a series of tests are executed by the Kubernetes CI platform, Prow. If any of the tests failed, the k8s-ci-robot will reply to the PR with links to the failed tests and available logs.

Pushing new commits to your PR will automatically trigger the tests to re-run.

Occasionally there can be issues with the Kubernetes CI platform. These can occur for a wide variety of reasons even if your contribution passes all local tests. You can trigger a re-run of the tests with the /retest command.

For more information on troubleshooting specific tests, see the Testing Guide.

Labels

Kubernetes uses labels to categorize and triage issues and Pull Requests. Applying the right labels will help your issue or PR be triaged more effectively.

References:

Frequently used labels:

/sig <sig name> Assign a SIG to the ownership of the issue or PR.
/area <area name> Associate the issue or PRs to a specific area.
/kind <category> Categorizes the issue or PR.

Working Locally

Before you propose a pull request, you will have to do some level of work locally. If you are new to git, the Atlassian git tutorial is a good starting point. As an alternative, Stanford’s Git magic tutorial is a good multi-language option.

References:

Branch Strategy

The Kubernetes project uses a “Fork and Pull” workflow that is standard to GitHub. In git terms, your personal fork is referred to as the "origin" and the actual project’s git repository is called "upstream". To keep your personal branch (origin) up to date with the project (upstream), it must be configured within your local working copy.

Adding Upstream

Add upstream as a remote, and configure it so you cannot push to it.

# replace <upstream git repo> with the upstream repo URL
# example:
# https://github.com/kubernetes/kubernetes.git
# git@github.com/kubernetes/kubernetes.git
git remote add upstream <upstream git repo>
git remote set-url --push upstream no_push

This can be verified by running git remote -v which will list your configured remotes.

Keeping Your Fork in Sync

Fetch all the changes from upstream and “rebase” them on your local master branch. This will sync your local repo with the upstream project. Push the local changes to your remote master.

git fetch upstream
git checkout master
git rebase upstream/master
git push

You should do this minimally before creating a new branch to work on your feature or fix.

git checkout -b myfeature

Squashing Commits

The main purpose of squashing commits is to create a clean readable git history or log of the changes that were made. Usually, this is done in the last phase of a PR revision. If you are unsure if you should squash your commits, it is better to err on the side of having more and leave it up to the judgment of the other contributors assigned to review and approve your PR.

Perform an interactive rebase to choose which commits you want to keep and which you want to squash, then force push your branch:

git rebase -i HEAD~3
...
git push --force

Note: you can also use the bot to help squash commits, please see squashing commits for more details.

Events: Events and Activities

Mon, 01 Jan 0001 00:00:00 +0000

Notice

This event has passed. Recordings from the event can be found on the Kubernetes Community YouTube Channel.

NOTE: This list is not complete or final, there will be room for more :)

Events

Kubernetes Contributor Awards

Session link

Kubernetes SIG Co-Chairs and Tech Leads would like for you to attend this special event where we honor and dedicate the hard work that the community has been working on. These peer awards are a tradition at the Kubernetes Contributor Summits so we are bringing them virtual, please join us to thank and support all the people who have worked hard to help us this year.

Most Extreme Kubernetes Challenge - DevOps Party Game

Join Ian Coldwater along with Jeremy Meiss as they host a special edition of the DevOps Party Game. We will have Kubernetes questions and panelists to take this variation of a party game to another level! There will be two sessions to cover time zones, and we’ll be broadcasting this to the Kubernetes YouTube channel. Audience participation makes this a fun time for all attendees!

We will be giving away lots of great prizes!

The Great Cloud Native Bake Off

Session Link

A virtual cooking even styled after the Great British Bake-off will be held during the Kubernetes celebration Event hosted by CNCF Ambassador Kat Cosgrove on Saturday Dec 12 at 12pm PT.

Contestants will have 90 minutes to cook a Kubernetes themed dessert. Anything goes, as long as the majority of preparation is done live. The competition is open to all skill levels, from baking from a cake mix to grinding your own flour as long as you can theme it to Kubernetes.
Contestants will be responsible for their own recipes and acquiring their ingredients. If you need help with either of these, let us know!
Contestants will be expected to join a video conference call 30 mins prior to kick off, and should have a phone or ipad with a stand (or a patient friend ) to capture them preparing their dessert.
Our Host and Commentators will provide commentary on our contestants and will ask each contestant questions through the event. At the end of the 90minutes we’ll be joined by an esteemed group of expert judges who will judge your (hopefully completed) dessert on the following criteria:
- Execution: How well does it fit the “Kubernetes theme”
- Appearance: How does it look?
- Taste: Obviously the judges can’t taste it, so they’ll need to be creative for this one.

We’re looking for cooks of all backgrounds and talents. If this sounds like fun to you and you want to cook with us, email pczarkowski@vmware.com with the subject “Great Kubernetes Bake-off”. List your name, company you work for, your self-assessed cooking skills (from 1 to 5, 5 being Gordon Ramsey), a twitter handle (or other social media) and any other details you wish to provide.

Party Games

For Linux players, there are no game specific instructions, but many can run on Linux through proton

NOTE: These are attendee suggestion driven and should not be considered an endorsement for the Kubernetes project as a whole.

Among Us

URL: https://innersloth.itch.io/among-us
Platforms: PC (Steam / itch.io) | Android | iOS
Cost: $5 on PC, free on mobile
Players: 4-10

NOTE: It’s Cross-Platform!

Join your crewmates in a multiplayer game of teamwork and betrayal!

Play online with 4-10 community members as you attempt to hold your spaceship together and return back to civilization. But beware…as there may be alien impostors aboard!

One or two crewmates have been replaced by parasitic shapeshifters. Their goal is to eliminate the rest of the crew before the ship reaches home. The Impostors will sabotage the ship, sneak through vents, deceive, and frame others to remain anonymous and kill off the crew.

While everyone is fixing up the ship, no one can talk to maintain anonymity. Once a body is reported, the surviving crew will openly debate who they think The Impostor is. The Impostors’ goal is to pretend that they are a member of the crew. If The Impostor is not voted off, everyone goes back to maintaining the ship until another body is found. If The Impostors are voted off, the crew wins!

Reporting: There is no in-game reporting mechanism. If there is an issue with a Kubernetes community member, please use the /report command or contact the CoCC directly.

Animal Crossing

URL: https://www.animal-crossing.com/new-horizons/
Platforms: Nintendo Switch
Cost: $60
Players: Varies

“Escape to a deserted island and create your own paradise as you explore, create, and customize in the Animal Crossing: New Horizons game. Your island getaway has a wealth of natural resources that can be used to craft everything from tools to creature comforts. You can hunt down insects at the crack of dawn, decorate your paradise throughout the day, or enjoy sunset on the beach while fishing in the ocean. The time of day and season match real life, so each day on your island is a chance to check in and find new surprises all year round.

Show off your island utopia to family and friends—or pack your bags and visit theirs. Whether playing online* or with others beside you**, island living is even better when you can share it. Even without hopping on a flight, you’ll meet a cast of charming animal residents bursting with personality. Friendly faces like Tom Nook and Isabelle will lend their services and happily help you grow your budding community. Escape to your island getaway—however, whenever, and wherever you want.” - Nintendo

Reporting: See Nintendo’s doc: How to Report Profanity or Offensive Behavior

Destiny 2

URL: https://www.bungie.net/7/en/Destiny/NewLight
Platforms: PC (Steam) | Xbox | Playstation | Stadia
Cost: Free (base game only, expansions are $25-$40)
Players: 3-6

Destiny is a multiplayer scifi/fantasy space shooter game with lots of guns and space super powers. Players can team up in 3 person squads for missions called strikes, 4 player teams for Gambit, and up to 6v6 in player-vs-player.

Preparation: The base game is free to play, however there is no cross play, so we’ll have to group up by platform. Download the game before the event since it’s about 70GB. You’ll probably want to do the tutorial campaign ahead of time to get a feel for the game. Ideally complete enough of the introduction to be able to head to “The Tower”.

Reporting: Reporting can be done via the “Roster” tab in game. Generally speaking chat is done via third party tools so other than player usernames you don’t typically chat with other players. If there is an issue with a Kubernetes community member, please use the /report command or contact the CoCC directly.

Guides / New Player Coaches: Jorge Castro (PC), Allison Downey(PC),and Wayne Witzel(PC)

Fall Guys

URL: https://fallguys.com/
Platforms: PC (Steam) | Playstation
Cost: $20
Players: 1-60

Up to 60 players compete in matches with battle royale-style gameplay. Players, represented as jellybean-like figures, move around a three-dimensional playing field, with additional moves such as jumping, grabbing/climbing, or diving to assist gameplay. The aim is to qualify for subsequent rounds by successfully completing each of the randomly selected mini-games. Certain mini-games involve running towards a finish line at the end of the map, while others add elements of teamwork. On every mini-game, obstacles appear around the map for added complexity. Players who are too slow or who fail certain requirements for a mini-game are eliminated. On the final round, the remaining few players compete in a final match with a randomised mini-game designed for a smaller player size. The winner of the match is the last player standing.

Reporting: There is no in-game reporting mechanism. If there is an issue with a Kubernetes community member, please use the /report command or contact the CoCC directly.

skribbl.io

[Game Site][sk-site]

Platforms: Browser
URL: https://skribble.io
Cost: Free
Players: 2-8

skribbl.io is a free multiplayer drawing and guessing game. One game consists of a few rounds in which every round someone has to draw their chosen word and others have to guess it to gain points! The person with the most points at the end of the game will then be crowned as the winner!

When it’s your turn to draw, you will have to choose a word from three options and visualize that word in 80 seconds, alternatively when somebody else is drawing you have to type your guess into the chat to gain points, be quick, the earlier you guess a word the more points you get!

Reporting: There is no in-game reporting mechanism. If there is an issue with a Kubernetes community member, please use the /report command or contact the CoCC directly.

Jackbox

Platforms: Windows, Mac, Linux (browser for participants)
Steam: https://store.steampowered.com/app/1211630/The_Jackbox_Party_Pack_7/
Cost: $30 (only host needs to purchase)
Players: 2-8

Jackbox is a mainstay of the DevOps Party Games stream. The link is for Pack 7 but as the name implies, there’s quite a few others from over the years, each with different minigames. The host will have to stream their display for others to watch, Discord supports game streaming itself or you can use Twitch or YouTube or anything else you’re comfortable with.

Board Games

Just because we are internet-partying doesn’t mean we need to skimp on the board games! This is not an exhaustive list and if you have any questions please join us in the board-games channel on Discord! If you want to lead a game and there isn’t an open voice/video channel available, please ask for one in the mod-chat-public channel and we’ll be happy to make more!

Board Game Arena

Platforms: Browser
URL: https://boardgamearena.com/
Cost: Mostly free, premium games require at least one paid player
Players: Varies by game, up to 10+

BGA hosts a wide variety of games, from classics like Connect Four to nerd staples like Innovation. Setup and hosting a game is super smooth. Highly recommended if they have a game you’re looking for.

Dominion Online

Platforms: Browser
URL: https://dominion.games/
Cost: Base game free, expansions require at least one paid player
Players: 2-6

The definitive online version of Dominion, a deck-building game. The website can be a bit graphically intensive for a tablet, but laptops should have no trouble. The original base game is free, and I would recommend new players stick to that anyway. If you want to unlock expansions there is a slightly awkward subscription option, it’s cheap but make sure you cancel if you aren’t going to keep using it.

Jinteki.net (Netrunner)

Platforms: Browser
URL: https://www.jinteki.net/
Cost: Free
Players: 2

A fan-run, online version of Android: Netrunner, an older two-player card game. Unfortunately being a website for existing fans, it doesn’t have a tutorial to speak of so you will need an existing player to show you the ropes. But once you get in, it’s a very solid implementation of a great game. If you haven’t tried out a fully asymmetric game before, Netrunner is a fun way to expand your horizons.

Tabletopia

Platforms: Browser, Mac, Windows
URL: https://tabletopia.com/
Cost: Many free, a lot of newer games require paid subscription
Players: Varies by game

Tabletopia is a generalized tabletop gaming simulator with support for thousands of games. Usually not quite as smooth as the previous options given its sandbox-y nature but allows for even very complex tabletop games. This also has free, native Mac and Windows clients if WebGL makes your browser sad.

Yucata

Platforms: Browser
URL: https://www.yucata.de/en
Cost: Free
Players: Varies by game, mostly 2-4

Similar to BGA, Yucata is a fan-run site with many games on offer, all free and even allowing playing as a guest. The games are mostly a bit older and niche given the difficulties of securing licenses, but well implemented.

Boiteajeux

Platforms: Browser
URL: http://www.boiteajeux.net/
Cost: Free
Players: Varies by game

One step more niche than Yucata is Boiteajeux. But it is notable for having an online version of Dixit (think Apple to Apples or Cards Against Humanity but with paintings instead of words and stories instead of madlibs) and Agricola (the tableau-building game which unseated Puerto Rico as the BGG champion back in 2008).

Tabletop Simulator

Platforms: Windows, Mac, Linux
Steam: https://store.steampowered.com/app/286160/Tabletop_Simulator/
Cost: $20 (plus DLC for official game modes)
Players: Varies by game

Similar to Tabletopia, Tabletop Simulator is exactly what it sounds like, a gaming sandbox with a scripting system to implement games. It does offer a few dozen official games for an extra DLC charge, but the vast majority of the reason to use it is the incredibly extensive user-created selection in Steam Workshop. Some Workshop games are fully scripted, while others are just the pieces and cards and whatnot and you have to handle the rules yourself. It also support a VR mode, though more as a fun lark than something I would really recommend for a long gaming session.

Wingspan

Platforms: Windows, Mac
Steam: https://store.steampowered.com/app/1054490/Wingspan/
Cost: $20
Players: 1-5

If you know any boardgame nerds, they probably won’t shut up about Wingspan and I won’t either, it’s great. On top of being a fantastic game, this desktop version is gorgeous and has both real-time and async multiplayer support. It includes the 1 player solitaire Wingspan Automata but human and bot multiplayer too.

Race For The Galaxy

Platforms: Windows and Mac have pre-built versions, source available for Linux
URL: http://keldon.net/rftg/
Cost: Free
Players: 2-6

A bit of an odd one out, Keldon’s RFTG is a fan-made version of the tableau-building classic but with the blessing of the original publisher. Like other fan-made implementations, it doesn’t have a built-in tutorial but it does have a simple online multiplayer system. Linux users might need to compile it themselves. The defining feature is AI opponents but it also supports online play with other humans.

Terraforming Mars

Platforms: Windows
Steam: https://store.steampowered.com/app/800270/Terraforming_Mars/
Cost: $20
Players: 1-5

Terraforming Mars is a well loved board game, though the digital version is a bit more buggy than I would like. The Prelude DLC has just launched though, so if you already own it on Steam and want a new challenge with friends, it’s always a good time! Online multiplayer does require creating a free Asmodee account.

Ticket To Ride

Platforms: Windows, Mac
Steam: https://store.steampowered.com/app/108200/Ticket_to_Ride/
Cost: $10 (plus DLC for expansions)
Players: 2-5

Another true classic, Ticket To Ride has been a staple of board game nights for over a decade. This also has numerous console and mobile ports, though I’m unsure if the online multiplayer is compatible between them.

Sentinels Of The Multiverse

Platforms: Windows, Mac, Linux
Steam: https://store.steampowered.com/app/337150/Sentinels_of_the_Multiverse/
Cost: $10 (plus DLC for expansions, free demo for the tutorial)
Players: 2-5

A bit older but still putting out expansions, Sentinels is a superhero-themed cooperative card game where you work together to take down supervillians. All the original game expansions have now been released as DLC with Steam Workshop support coming soon for player-made expansions and new cards.

Roll For The Galaxy

Platforms: Windows
Steam: https://store.steampowered.com/app/893840/Roll_for_the_Galaxy/
Cost: $15
Players: 2-5

The same developer as the earlier free Race has also built a full commercial release for the dice-based spinnoff Roll. As polished as the other retail games here, but with the clear heart of a true fan too. If you haven’t tried this game and like Race For The Galaxy, definitely check it out.

Virtual Photobooth

Turn on your webcams and bring out your silly faces! In lieu of taking a group photo at a contributor summit this year, let’s make a collage of all our awesome faces instead! Zero pressure and totally optional! Once you click the link and follow the directions you’ll see a 3-2-1 countdown and it’ll take your picture! Don’t worry, if you don’t like it, it gives you a chance to retake your photos before submitting. Smile!

https://app.virtualbooth.me/booth/q64QRzGM

Events: Events and Activities

Mon, 01 Jan 0001 00:00:00 +0000

Notice

This event has passed. Recordings from the event can be found on the Kubernetes Community YouTube Channel.

NOTE: This list is not complete or final, there will be room for more :)

Events

Events

Kubernetes Contributor Awards

DevOps Party Games: Most Extreme Kubernetes Contributor Challenge

DevOps Party Games takes the idea of “online party games” and tilts it on its head by adding DevOps-inspired content to existing games, and then streams it live via Twitch for a worldwide audience to watch, comment, and hopefully be entertained. In addition, the hosts (Matt Stratton, Jeremy Meiss, and Dan Maher) will provide color commentary, much like a modern day Cotton McKnight and Pepper Brooks (announcers from Dodgeball).

For this edition there will be a twist! All participants are Kubernetes contributors! Join your hosts Matty Stratton (main DPG host) + Paris Pittman (K8s Steering Committee) with fellow contributor and maintainer participants: Laura Lorenz (sig-multicluster), Tim Hockin (sig-network), Tabitha Sable (sig-security), Xing Yang (sig-storage), Adolfo Garcia (sig-release), Kat Cosgrove (sig-release), Dims Srinivas (Steering, sig-architecture), Danielle Lancashire (sig-node)

Cloud Native Community Cookbook - Kiwi Hackbach Edition

Hippie’s Hackbach will be cooking up a couple recipes from our Cloud Native Community Cookbook… and in true open-source style, everyone is encouraged to cook along in your own kitchen! From one of the many existing recipes, or add you own (via a PR of course)! We hope is to create a new release of the cookbook and send physical copy it out to the folks in attendance.

Krafternetes

All day December 16th, creative folks will be showing up in the Krafternetes channel on Discord to share art, music, and performances. Between studio tours, a collaborative “quick draw” session, or online performances, the artists of Kubernetes will have events all day to share with you. If you’re interested in participating, speak up in channel Krafternetes on slack.

Kubernetes the Tabletop RPG

Comms go to static, and all you can see is a blinding red flash meaning this space ship is now in HIGH_ALERT. Will you and the rest of the crew make it off this asteroid mining hauler alive? @lauralorenz is GMing a Contributor Summit special one-shot of the Tabletop RPG “Mothership”. And you just know that in this sci-fi horror fantasy world, all life support and warp systems are running on k8s version 1.23 – which wouldn’t be as scary if the game world wasn’t in the year 2491. No tabletop roleplaying experience required, 6 players maximum, PG-13 content and 2 hour timebox. You will need access to voice and 2 d10 die (or use the dice widget on Google search). Sign up here for Thursday or Friday night sessions.

Events: Registration

Mon, 01 Jan 0001 00:00:00 +0000

Registration is open to all members of one of the Kubernetes orgs or sponsored attendees.

Register Here

If you are not yet a member, but active within the project, please consider joining! The process of joining is straight forward. See our org membership docs for more information. If your application to join is pending, please contact us at community@kubernetes.io about registering.

NOTE: The summit adheres to KubeCon’s Health & Safety Guidelines requiring ALL in-person attendees to be fully vaccinated against the COVID-19 virus.

Events: Registration

Mon, 01 Jan 0001 00:00:00 +0000

Registration is open to all members of one of the Kubernetes orgs or sponsored attendees.

Registration will close on October 20th.

NOTE: The summit adheres to KubeCon’s Health & Safety Guidelines requiring ALL in-person attendees to be fully vaccinated against the COVID-19 virus or to show proof of a negative COVID-19 test administered by a verified provider.

If you acknowledge the above, please go ahead and click below to register:

Register Here

Events: Registration

Mon, 01 Jan 0001 00:00:00 +0000

Registration is open to all members of one of the Kubernetes orgs.

NOTE: The summit adheres to KubeCon’s Health & Safety Guidelines

If you acknowledge the above, please go ahead and click below to register:

Register Here

Events: Registration

Mon, 01 Jan 0001 00:00:00 +0000

Registration is open to all members of one of the Kubernetes orgs or sponsored attendees.

NOTE: The summit adheres to KubeCon’s Health & Safety Guidelines

If you acknowledge the above, please go ahead and click below to register:

Register Here

Events: Registration

Mon, 01 Jan 0001 00:00:00 +0000

Registration is open to all members of one of the Kubernetes orgs, qualified Etcd contributors, or sponsored attendees. Registration closes: Thursday, November 2nd, 2023; 16:00 US Eastern Time

NOTE: The summit adheres to KubeCon’s Health & Safety Guidelines

If you acknowledge the above, please go ahead and click below to register:

Register Here

Events: Registration

Mon, 01 Jan 0001 00:00:00 +0000

Registration is open to all members of one of the Kubernetes orgs or sponsored attendees.

NOTE: The summit adheres to KubeCon’s Health & Safety Guidelines

If you acknowledge the above, please go ahead and click below to register:

Register Here

Events: Registration

Mon, 01 Jan 0001 00:00:00 +0000

Registration is open to all members of one of the Kubernetes orgs, qualified Etcd contributors, or sponsored attendees. Registration closes: Thursday, November 7th, 2024; 16:00 US Eastern Time

If you are sponsored by a SIG Lead please fill in the SIG in the registration form. All registrations by non Org members will be declined.

NOTE: The summit adheres to KubeCon’s Health & Safety Guidelines

KubeCon registration is required for Contributor Summit attendees.

If you acknowledge the above, please go ahead and click below to register:

Register Here

Events: RSVP

Mon, 01 Jan 0001 00:00:00 +0000

As we are not holding the formal Contributor Summit, we are not running conference registration. SIGs and subprojects who choose to hold a mini-event will be responsible for any kind of signups they need to manage.

We will be holding an evening social event, however, and have an RSVP link for attendees. To attend the social, you must be a member or active contributor of one of the Kubernetes GitHub Orgs (e.g., kubernetes or kubernetes-sigs) or a sponsored attendee. If you are an active contributor but not a member, consider applying for org membership!

If you have questions, please see the faq or reach out to us at community@kubernetes.io.

Registration is currently closed.

NOTE: Any in-person events held by SIGs and subprojects will follow KubeCon’s Health & Safety Guidelines requiring ALL in-person attendees to be fully vaccinated against the COVID-19 virus.

Events: Schedule

Mon, 01 Jan 0001 00:00:00 +0000

Notice

This event has passed. Recordings from the event can be found on the Kubernetes Community YouTube Channel.

Thursday December 10th, the doors will open and members will be invited to discord.

Events and official activities are planned for Friday and Saturday, with the server remaining open on Sunday for anyone that would still like to join in and hang out.

Kubernetes Contributor Celebration

Events: Schedule

Mon, 01 Jan 0001 00:00:00 +0000

Notice

This event has passed. Recordings from the event can be found on the Kubernetes Community YouTube Channel.

Kubernetes Contributor Celebration

Docs: Making your First Contribution

Mon, 01 Jan 0001 00:00:00 +0000

Your First Contribution

Find something to work on

Find something to work on

The first step to getting starting contributing to Kubernetes is to find something to work on. Help is always welcome, and no contribution is too small (but see below)!

Here are some things you can do today to get started contributing:

Help improve the Kubernetes documentation
Clarify code, variables, or functions that can be renamed or commented on
Write test coverage
Help triage issues

If the above suggestions don’t appeal to you, you can browse the issues labeled as a good first issue to see who is looking for help. Those interested in contributing without writing code can also find ideas in the Non-Code Contributions Guide.

Note: although contributions are welcome, beware that every pull request creates work for maintainers and costs for testing it. Fixing linter warnings is often not worth it because the existing code is fine. Always discuss with maintainers first before creating such PRs.

Find a good first topic

There are multiple repositories within the Kubernetes organization. Each repository has beginner-friendly issues that are a great place to get started on your contributor journey. For example, kubernetes/kubernetes has help wanted and good first issue labels for issues that don’t need high-level Kubernetes knowledge to contribute to. The good first issue label also indicates that Kubernetes Members have committed to providing extra assistance for new contributors. Another way to get started is to find a documentation improvement, such as a missing/broken link, which will give you exposure to the code submission/review process without the added complication of technical depth.

Issue Assignment in Github

When you’ve found an issue to work on, you can assign it to yourself.

Reply with /assign or /assign @yourself on the issue you’d like to work on
The K8s-ci-robot will automatically assign the issue to you.
Your name will then be listed under, Assignees.

Learn about SIGs

Some repositories in the Kubernetes Organization are owned by [Special Interest Groups], or SIGs.

The Kubernetes community is broken out into SIGs in order to improve its workflow, and more easily manage what is a very large community project. The developers within each SIG have autonomy and ownership over that SIG’s part of Kubernetes. Understanding how to interact with SIGs is an important part of contributing to Kubernetes. Check out the list of SIGs for contact information.

SIG structure

A SIG is an open, community effort.

Anybody is welcome to jump into a SIG and begin fixing issues, critique design proposals, and review code. SIGs have regular video meetings which everyone is welcome to attend. Each SIG has a Slack channel, meeting notes, and their own documentation that is useful to read and understand. There is an entire SIG (sig-contributor-experience) devoted to improving your experience as a contributor. If you have an idea for improving the contributor experience, please consider attending one of the Contributor Experience SIG’s weekly meetings.

Finding the appropriate SIG for your contribution and adding a SIG label will help you ask questions in the correct place and give your contribution higher visibility and a faster community response.

For Pull Requests, the automatically assigned reviewer will add a SIG label if you haven’t already done so.

For Issues, please note that the community is working on a more automated workflow. Since SIGs do not directly map onto Kubernetes subrepositories, it may be difficult to find which SIG your contribution belongs in. Review the list of SIGs to determine which SIG is most likely related to your contribution.

Example: if you are filing a CNI issue (that’s Container Networking Interface) you’d choose the Network SIG. Add the SIG label in a new comment on GitHub by typing the following:

/sig network

Follow the link in the SIG name column to reach each SIG’s README.

Most SIGs will have a set of GitHub Teams with tags that can be mentioned in a comment on issues and pull requests for higher visibility. If you are not sure about the correct SIG for an issue, you can try SIG-contributor-experience, or ask in Slack.

SIG-specific contributing guidelines

Some SIGs have their own CONTRIBUTING.md files, which may contain extra information or guidelines in addition to these general ones. These are located in the SIG-specific community directories:

File an Issue

Not ready to contribute code, but see something that needs work? While the community encourages everyone to contribute code, it is also appreciated when someone reports an issue. Issues should be filed under the appropriate Kubernetes subrepository. For example, a documentation issue should be opened in kubernetes/website. Make sure to adhere to the prompted submission guidelines while opening an issue. Check the issue triage guide for more information.

Events: Schedule

Mon, 01 Jan 0001 00:00:00 +0000

NOTE: You must go through vaccine verification and pick up your badge before attending the summit or social evening event.

Steering AMA

The Summit will start off with an AMA with members of the Kubernetes Steering Committee. Bring any and all questions about how we’re running the project, ongoing efforts & issues, and whatever you’d like to discuss with Steering.

Unconference

The Contributor Summit will be an Unconference-style event. This means that you should arrive with topics in mind, and we will pitch them and vote on them in the morning, and then hold sessions in the afternoon, after the Steering AMA. This is the format used at many DevOps Days, and helps us accommodate changing needs and unpredictable travel schedules.

If you already have a topic in mind, we urge you to add it to the Topics issue so that other contributors can arrive mentally prepared for it. This is especially crucial if you think you might not make it to the Summit until afternoon.

SIG Meetings

SIGs, Working Groups, and teams will be meeting during the Summit. See if your team is meeting and mark your attendance on our SIG Meetings Schedule.

Doc Sprint

SIG-Docs will have a full-day Documentation working session during the Summit. If you contribute to the docs – and who doesn’t – or you want to learn to do it better, join them.

Schedule

Kubernetes Contributor Summit Europe 2022

Events: Schedule

Mon, 01 Jan 0001 00:00:00 +0000

Kubernetes Contributor Summit Europe 2022

Events: Schedule

Mon, 01 Jan 0001 00:00:00 +0000

NOTE: You MUST pick up your badge before attending the summit event.

Schedule

Tuesday, September 26th

09:00 ~ 09:15 am - Welcome: Kevin Wang (Huawei Cloud)/Puja (Gaint Swarm)
09:15 ~ 09:45 am - #sig-multi-cluster: Technical thinking, practice, and planning of multi-cluster management in the Kubernetes community by Hongcai Ren (Huawei Cloud, Karmada Maintainer)
09:45 ~ 10:15 am - Declaratively deploy your Kubernetes manifests, Kustomize configs, and Charts as Helm releases: Helmfile by Xiongxiong Yuan (Gitlab China)
10:15 ~ 10:30 am - Break/Networking (Tea break) & Group Photo
10:30 ~ 11:00 am - #sig-scheduling: Kubernetes Scheduling Updates and Future: Leibo Wang (Huawei Cloud)
11:00 ~ 12:30 am - Unconference
Lunch & Networking

Unconference

The unconference sessions coming soon! If you have a topic in mind, please check back soon - we’ll launch a tracking issue for submissions closer to the event.

Events: Schedule

Mon, 01 Jan 0001 00:00:00 +0000

NOTE: You MUST pick up your badge before attending the summit or social evening event.

Steering AMA

Unconference

The Contributor Summit will be primarily an Unconference-style event. This means that you should arrive with topics in mind, and we will pitch them and vote on them in the morning, and then hold sessions in the afternoon, after the Steering AMA. This is the format used at many DevOps Days, and helps us accommodate changing needs and unpredictable travel schedules.

If you have a topic in mind, please add it to the GitHub Issue.

Doc Sprint

SIG-Docs will have a full-day Documentation working session during the Summit. If you contribute to the docs – and who doesn’t – or you want to learn to do it better, join them.

CFP

If you would like to submit a formal session, please use the CFP Form. This form will be open through Friday, March 31st, and covers presentation, workshop, and collaboration style sessions.
Unconference sessions should use the GitHub issue referenced above.

Schedule

Kubernetes Contributor Summit Europe 2023

Events: Schedule

Mon, 01 Jan 0001 00:00:00 +0000

NOTE: You MUST pick up your badge before attending the summit or social evening event.

CFP

A CFP for sessions is open through Friday, September 15th. Please, expect the schedule to be announced on October 6th, 2023.

Steering AMA

Preselected Sessions

The Contributor Summit will have two rooms of preselected sessions submitted through our CfP. This will include current development and community issue discussions, introducing new initiatives, workshops for improving contributor skills, and other sessions by and for Kubernetes contributors.

SIG Meetings

Included in our preselected sessions will be several SIG, WG, and team meetings. If your SIG/team in Kubernetes has enough people at Kubecon to have a face-to-face meeting, take advantage of it and host one. SIG meetings are open to all attendees.

Unconference

The Contributor Summit will include one track of Unconference-style sessions.
After the CfP closes, contributors will be able to pitch and vote on last-minute sessions in a GitHub Issue, and final selection of those topics will be made at the Summit itself. This allows us to incorporate community issues and ideas that come to light after the CfP ends.

This is the format used at many DevOps Days, and helps us accommodate changing needs and unpredictable travel schedules.

If you have a topic in mind, please check back soon - we’ll launch a tracking issue for submissions closer to the event.

Doc Sprint

SIG-Docs will have a full-day Documentation working session during the Summit. If you contribute to the docs – and who doesn’t – or you want to learn to do it better, join them.

Schedule

Kubernetes Contributor Summit North America 2023

Events: Schedule

Mon, 01 Jan 0001 00:00:00 +0000

NOTE: You MUST pick up your badge before attending the summit or social evening event.

Steering AMA

Unconference

This is the format used at many DevOps Days, and helps us accommodate changing needs and unpredictable travel schedules.

If you have a topic in mind, please add it to the Unconference Topics Issue

Doc Sprint

SIG-Docs will have a full-day Documentation working session during the Summit. If you contribute to the docs – and who doesn’t – or you want to learn to do it better, join them.

CFP

A CFP for sessions is open through ~~Sunday, February 4th~~ Wednesday, February 14th. Please, expect the schedule to be announced on February 25th, 2023. It will cover presentation, workshop and collaboration style sessions. Unconference sessions should use the Github issue referenced above.

Schedule

Kubernetes Contributor Summit Europe 2024

Events: Schedule

Mon, 01 Jan 0001 00:00:00 +0000

NOTE: You MUST pick up your badge before attending the summit or social evening event.

CFP

The Cfp is closed. You can still propose topics in the Unconference sessions. See below for the kinds of session proposals which are appropriate.

Steering AMA

Preselected Sessions

SIG Meetings

Unconference

This is the format used at many DevOps Days, and helps us accommodate changing needs and unpredictable travel schedules.

If you have a topic in mind, feel free to submit it under the Unconference Issue.

Doc Sprint

SIG-Docs will have a full-day Documentation working session during the Summit. If you contribute to the docs – and who doesn’t – or you want to learn to do it better, join them.

CNCF Q&A

The CNCF does its best to build and sustain communities of open source projects. It also does its best to try and stay connected to those contributors that make all of gesture this, possible. So, the CNCF want to connect with y’all and make sure your voices are heard. Join CNCF Staff and have your Questions answered.

Schedule

Kubernetes Contributor Summit Europe 2024

Docs: Contributing to Kubernetes

Mon, 01 Jan 0001 00:00:00 +0000

Contributing

Kubernetes is open source, but many of the people working on it do so as their day job. In order to avoid forcing people to be “at work” effectively 24/7, we want to establish some semi-formal protocols around development. Hopefully, these rules make things go more smoothly. If you find that this is not the case, please complain loudly.

As a potential contributor, your changes and ideas are welcome at any hour of the day or night, weekdays, weekends, and holidays. Please do not ever hesitate to ask a question or send a pull request.

Check out our community guiding principles on how to create great code as a big group.

Beginner focused information can be found below in Open a Pull Request and Code Review.

For quick reference on contributor resources, we have a handy contributor cheatsheet.

Communication

It is best to contact your SIG for issues related to the SIG’s topic. Your SIG will be able to help you much more quickly than a general question would.

For general questions and troubleshooting, use the standard lines of communication and work through the troubleshooting guide.

GitHub workflow

To check out code to work on, please refer to the GitHub Workflow Guide.

The full workflow for a pull request is documented here:

Kubernetes-specific github workflow.

That document is comprehensive and detailed, for purposes of a typical pull request we will cover the initial and simple use case here:

Opening a Pull Request

Pull requests are often called a “PR”. Kubernetes generally follows the standard github pull request process, but there is a layer of additional kubernetes specific (and sometimes SIG specific) differences:

The first difference you’ll see is that a bot will begin applying structured labels to your PR.

The bot may also make some helpful suggestions for commands to run in your PR to facilitate review.
These /command options can be entered in comments to trigger auto-labeling and notifications. Refer to its command reference documentation.

Common new contributor PR issues are:

Not having correctly signed the CLA ahead of your first PR. See the CLA page for troubleshooting help, in some cases you might need to file a ticket with the CNCF to resolve a CLA problem.
Finding the right SIG or reviewer(s) for the PR (see Code Review section) and following any SIG or repository specific contributing guidelines (see Learn about SIGs section)
Dealing with test cases which fail on your PR, unrelated to the changes you introduce (see Test Flakes)
Not following scalability good practices
Include mentions (like @person) and keywords which could close the issue (like fixes #xxxx) in commit messages.

Code Review

For a brief description of the importance of code review, please read On Code Review.
There are two aspects of code review: giving and receiving.

To make it easier for your PR to receive reviews, consider the reviewers will need you to:

Follow the project coding conventions
Write good commit messages
Break large changes into a logical series of smaller patches which individually make easily understandable changes, and in aggregate solve a broader issue
Label PRs with appropriate SIGs and reviewers: to do this read the messages the bot sends you to guide you through the PR process

Reviewers, the people giving the review, are highly encouraged to revisit the Code of Conduct as well as community expectations and must go above and beyond to promote a collaborative, respectful community. When reviewing PRs from others The Gentle Art of Patch Review suggests an iterative series of focuses which is designed to lead new contributors to positive collaboration without inundating them initially with nuances:

Is the idea behind the contribution sound?
Is the contribution architected correctly?
Is the contribution polished?

Note: if your pull request isn’t getting enough attention, you can use the #pr-reviews channel on Slack to get help finding reviewers.

Best practices

Write clear and meaningful git commit messages.
If the PR will completely fix a specific issue, include fixes #123 in the PR body (where 123 is the specific issue number the PR will fix. This will automatically close the issue when the PR is merged.
Make sure you don’t include @mentions or fixes keywords in your git commit messages. These should be included in the PR body instead.
When you make a PR for small change (such as fixing a typo, style change, or grammar fix), please squash your commits so that we can maintain a cleaner git history.
Make sure you include a clear and detailed PR description explaining the reasons for the changes, and ensuring there is sufficient information for the reviewer to understand your PR.
Additional Readings:

Testing

Testing is the responsibility of all contributors and is in part owned by all SIGs, but is also coordinated by sig-testing. Refer to the Testing Guide for more information.

There are multiple types of tests. The location of the test code varies with type, as do the specifics of the environment needed to successfully run the test:

Unit: These confirm that a particular function behaves as intended. Golang includes a native ability for unit testing via the testing package. Unit test source code can be found adjacent to the corresponding source code within a given package. For example: functions defined in kubernetes/cmd/kubeadm/app/util/version.go will have unit tests in kubernetes/cmd/kubeadm/app/util/version_test.go. These are easily run locally by any developer on any OS.
Integration: These tests cover interactions of package components or interactions between kubernetes components and some other non-kubernetes system resource (eg: etcd). An example would be testing whether a piece of code can correctly store data to or retrieve data from etcd. Integration tests are stored in kubernetes/test/integration/. Running these can require the developer set up additional functionality on their development system.
End-to-end (“e2e”): These are broad tests of overall system behavior and coherence. These are more complicated as they require a functional kubernetes cluster built from the sources to be tested. A separate document detailing e2e testing and test cases themselves can be found in kubernetes/test/e2e/.
Conformance: These are a set of testcases, currently a subset of the integration/e2e tests, that the Architecture SIG has approved to define the core set of interoperable features that all Kubernetes deployments must support. For more information on Conformance tests please see the Conformance Testing Document.

Continuous integration will run these tests either as pre-submits on PRs, post-submits against master/release branches, or both.
The results appear on testgrid.

sig-testing is responsible for that official infrastructure and CI. The associated automation is tracked in the test-infra repo. If you’re looking to run e2e tests on your own infrastructure, kubetest is the mechanism.

Security

Security Release Page - outlines the procedures for the handling of security issues.
Security and Disclosure Information - check this page if you wish to report a security vulnerability.

Documentation

Contributing to Documentation

Issues Management or Triage

Have you ever noticed the total number of open issues? Helping to manage or triage these open issues can be a great contribution and a great opportunity to learn about the various areas of the project. Triaging is the word we use to describe the process of adding multiple types of descriptive labels to GitHub issues, in order to speed up routing issues to the right folks. Refer to the Issue Triage Guidelines for more information.

Events: Frequently Asked Questions (FAQ)

Mon, 01 Jan 0001 00:00:00 +0000

Notice

This event has passed. Recordings from the event can be found on the Kubernetes Community YouTube Channel.

General Information

What is the Kubernetes Contributor Celebration?

The Kubernetes Contributor Celebration is an attempt to reclaim that and celebrate our accomplishments. It’s a time for us to relax, chat and do something fun with your fellow contributors!

When is it?

It will be from the afternoon (Pacific Time) December 10th through the weekend, ending on December 13th.

How do I register?

Please fill out the registration form.

Are friends and family allowed?

Allowed and encouraged! Please have them register as a friend or family member and use the email you registered with as the reference. They must agree to abide by the Code of Conduct while attending.

Where is the celebration being held?

The celebration will be hosted on Discord, a hosted online communication platform similar to Slack, but with a focus on voice and video in addition to text base chat. It’s been built to support the hosting of a safe, positive and inclusive space.

When will I get my invite?

Discord server invites will be sent out closer to the event.

What sort of activities are planned?

There will be trivia and other games available. For more information see the activities page.

Discord Information

How do I join?

Please see the How to join page.

Why do I need to verify myself once I connect (complete captcha)?

Spam bots and raids are more common with Discord than other platforms such as slack. Completing the external Captcha helps us keep Discord a safe place to have fun <3

Why do I need to agree to abide by the Code of Conduct?

Much like other communication platforms used by Kubernetes (and other CNCF projects) we want this to be an inclusive and inviting place for everyone. We understand that certain things like profane language are used by many while gaming, please still try to be inclusive and not offensive.

Remember: Don’t be a jerk. :)

Why can I only see the instructions-to-connect and info channels?

You’ve completed the captcha, but haven’t agreed to the code of conduct, head over to the #code-of-conduct channel and accept it, and you’ll be able to see everything. If you need assistance, join the #help channel.

What is this YAGPDB.xyz and why is it messaging me?

YAGPDB (Yet Another General Purpose Discord Bot) is a verified discord bot that we use to manage a variety of services within discord, from verification and moderation to role selection and automation.

How do I display my pronouns in Discord?

In Discord, you can set a nickname per-”server”. We recommend putting your pronouns in your nickname so they are visible at all times in Discord and with overlays. A few examples of what this would look like:

Arty (they/them)
Bob (he/him)
Jamie (she/her)

1 ) To do so, click the server dropdown (Top Left)

2 ) Select “Change Nickname”

3 ) Then follow the template of “nickname (pro/noun)” like so:

What are the `#<channel>-info` channels for?

For games that are popular enough to have their own category, the info channel in them will describe the game, links to where it can be downloaded, and will provide guidance on reporting people for that game/platform.

What are the `#<channel>-links` channels for?

Often when you’re having a conversation in one of the voice channels you’ll want to share a link with the other people on voice. You can’t do this directly in the voice channels, and it can clutter up the main text-chat channels, so the #<channel>-links channels are a scratch-pad for links or other things that are only relevant to the conversation carrying on in voice chat.

How do I know if someone is a Moderator, Staff Member or an Admin?

The member list on the right hand side of Discord will display the active members and which group they are. Mods, Staff Members, and Admins can also be recognized by the color of their username.

Members are blue
Staff members are orange
Moderators are yellow
Admins are red

Someone is spamming/harassing me, what should I do?

If they’re within discord, use the command:

/report <@username> <reason>

You can also ask for assistance in #help. A member of the mod team will reach out.

If it’s within a game and the person is not a part of this event, please use the in game method of reporting / blocking the person.

Discord is running slowly or stuttering, what should I do?

On Mac and occasionally on other platforms, Discord can stutter and consume a significant amount of CPU resources. The current workaround is to disable Hardware Acceleration. You can disable it in your User Settings by clicking on the cog next to your username and navigating to the setting here:

User Settings -> Appearance -> Advanced -> Hardware Acceleration

Help! I have a question?

You can ask in the #help channel and a staff member will try and help.

Events: Frequently Asked Questions (FAQ)

Mon, 01 Jan 0001 00:00:00 +0000

Notice

This event has passed. Recordings from the event can be found on the Kubernetes Community YouTube Channel.

General Information

What is the Kubernetes Contributor Celebration?

The Kubernetes Contributor Celebration is an attempt to reclaim that and celebrate our accomplishments. It’s a time for us to relax, chat and do something fun with your fellow contributors!

When is it?

It will be the week of December 13th.

How do I register?

Please fill out the registration form.

Are friends and family allowed?

Allowed and encouraged! Please have them register as a friend or family member and use the email you registered with as the reference. They must agree to abide by the Code of Conduct while attending.

Where is the celebration being held?

When will I get my invite?

Discord server invites will be sent out closer to the event.

What sort of activities are planned?

There will be trivia and other games available. For more information see the activities page.

Discord Information

How do I join?

Please see the How to join page.

Why do I need to verify myself once I connect (complete captcha)?

Spam bots and raids are more common with Discord than other platforms such as slack. Completing the external Captcha helps us keep Discord a safe place to have fun <3

Why do I need to agree to abide by the Code of Conduct?

Remember: Don’t be a jerk. :)

Why can I only see the instructions-to-connect and info channels?

What is this YAGPDB.xyz and why is it messaging me?

How do I display my pronouns in Discord?

Arty (they/them)
Bob (he/him)
Jamie (she/her)

1 ) To do so, click the server dropdown (Top Left)

2 ) Select “Change Nickname”

3 ) Then follow the template of “nickname (pro/noun)” like so:

Information on each channel in Discord

announcements : Announcements for any new events/updates will be done here
code-of-conduct : Make sure to accept the code of conduct by reacting with the Kubernetes emoji to the message!
instructions-to-connect : Follow the steps mentioned therre to enable all the existing channels
faq : Have a question or having a problem? Your question may be answered here :)
help : Need help? Have a question? Ask them here!
feedback : We would love to here your thoughts on what we can improve on and we can do a better job next time.
general : General chat for folks to chat
awwwwww : Show us pictures of your pets and other fluffy things that are cute. Humans allowed.
food : Show us food pictures and other tasty items around you.
lfg : Looking for a people to play a game with? Post your invite here!
games : Share links to play online games with each other.
board-games : Any board games enthusiast, this is your place to be!
theater : Let’s watch movies and stuff and chat about it here.
links-from-voice : Use this channel to share links from various voice channels.
main-events-chat : Text discussion related to events taking place in the main event channel
main-events : Main events will be kicked off here
hallway-1/hallway-2 : Voice channels for random discussions
games-1/games-2 : People can team up to play online games using these channels
k8s-ttrpg : Kubernetes on the Tabletop RPG event will be kicked off here
+ HORIZONTAL POD AUTOSCALER : Creates your own voice channel

What is the HORIZONTAL VOICE AUTOSCALER channel for?

Under this channel, a + create voice channel channel can be seen, joining which will create your own voice channel (just as similar as creating a pod!). For more information on the bot, check the pinned message in the ac-commands channel.

How do I know if someone is a Moderator, Staff Member or an Admin?

The member list on the right hand side of Discord will display the active members and which group they are. Mods, Staff Members, and Admins can also be recognized by the color of their username.

Members are blue
Staff members are orange
Moderators are yellow
Admins are red

Someone is spamming/harassing me, what should I do?

If they’re within discord, use the command:

/report <@username> <reason>

You can also ask for assistance in #help. A member of the mod team will reach out.

If it’s within a game and the person is not a part of this event, please use the in game method of reporting / blocking the person.

Discord is running slowly or stuttering, what should I do?

User Settings -> Appearance -> Advanced -> Hardware Acceleration

Help! I have a question?

You can ask in the #help channel and a staff member will try and help.

Events: Frequently Asked Questions (FAQ)

Mon, 01 Jan 0001 00:00:00 +0000

When is the summit taking place?

October 11th, the Monday before KubeCon North America.

Where is the summit located?

The in-person location at the JW Marriott LA Live, a 5 minute walk away from the LA Convention Center. See the Location & Venue section for more information.

Will I be able to attend remotely?

As we are not holding a formal event, we encourage you to work with your SIG or subproject to engage over Slack or team Zoom rooms. Any SIG or subproject that holds an event will have the ability to connect with any remote attendees.

Why is vaccination required to attend in-person?

As a co-located event, the summit is required to adhere to KubeCon’s Health & Safety Guidelines. There may be additional restrictions that develop closer to the event, and we will update the event accordingly to follow venue, municipality and CDC guidelines at a minimum.

Why do I need to be a Kubernetes Org member to attend in-person?

With uncertain attendance and staffing, we made this decision to ensure we can put on an event to the best of our ability.

Kubernetes Orgs:

If you are not yet a member, but active within the project, please consider joining! The process of joining is straight forward. See our org membership docs for more information.

What is a sponsored attendee?

NOTE: This applied to attending in person only. Anyone may register and attend remotely.

If you are a SIG lead or subproject owner and there is someone that is not yet an org member or from another project that might take part of a panel, SIG face-to-face meeting etc, you can sponsor them to attend the summit. Please reach out to community@kubernetes.io to make arrangements.

Will there be a New Contributor Workshop?

No, with uncertain attendance and staffing, we made this decision to ensure we can put on an event to the best of our ability. For those that are interested in becoming a contributor, SIG ContribEx plans to launch a course later this year.

Until then, here are you some additional resources you may find useful:

I have a question! How do I contact the event staff?

You can reach out to us directly at community@kubernetes.io or pop into the #contributor-summit slack channel to ask a question. :)

Events: Location & Venue

Mon, 01 Jan 0001 00:00:00 +0000

Feria Valencia

Registration and badge pick-up will be available at the Feria Valencia. You MUST go through vaccination verification and pick up your badge before attending the summit or evening social event.

The summit itself will be on Level 3 of the Feria Valencia Event Center. Masking is required.

Address
Av. de les Fires, s/n, 46035
València, Spain

La Casa de la Mar

The Contributor Social will be held at the La Casa de la Mar several kilometers from the Feria. CNCF will be providing a bus from the Fiera to the venue, and our community will also organize ride-sharing. Details to be posted later. Masking and vaccination are required for the party.

Address
Avenida Vicente Blasco Ibañez Novelist, 8.
CP. 46120 – Alboraya
Valencia, Spain

Events: Location & Venue

Mon, 01 Jan 0001 00:00:00 +0000

Huntington Place

Registration and badge pick-up will be available at the Huntington Place Convention Center. You MUST pick up your badge before attending the summit or evening social event.

Address
1 Washington Blvd
Detroit, MI 48226

Deluxx Fluxx

The evening social will be held at Deluxx Fluxx, a short walk away from the convention center.

Address
1274 Library St
Detroit, MI 48226

Events: Location & Venue

Mon, 01 Jan 0001 00:00:00 +0000

Shanghai Convention & Exhibition Center Of International Sourcing

Registration and badge pick-up will be available at the Shanghai Convention & Exhibition Center Of International Sourcing. You MUST pick up your badge before attending the summit event.

The summit itself will be in the Shanghai Convention & Exhibition Center Of International Sourcing. Masks are recommended, but not required for event attendees. Some masks will be available.

Address
No.2739 West Guangfu Road, Putuo District, Shanghai (200062)

Events: Location & Venue

Mon, 01 Jan 0001 00:00:00 +0000

RAI Amsterdam

Registration and badge pick-up will be available at the RAI Amsterdam. You MUST pick up your badge before attending the summit or evening social event.

The summit itself will be in the RAI Amsterdam Convention Centre. Masks are recommended, but not required for event attendees. Some masks will be available.

Address
Europaplein 24, 1078 GZ
Amsterdam, Netherlands

The Contributor Social will be held at Strandzuid, next to the Convention Centre.

Address
Europaplein 22, 1078 GZ
Amsterdam, Netherlands

Events: Location & Venue

Mon, 01 Jan 0001 00:00:00 +0000

Hyatt Regency McCormick Place

Registration and badge pick-up will be available at the Hyatt Regency McCormick Place. You MUST pick up your badge before attending the summit or evening social event.

The summit will be in the Hyatt Regency McCormick Place. Masks are recommended, but not required for event attendees. Some masks will be available.

Address
2233 South Dr. Martin Luther King Jr. Drive
Chicago, Illinois, 60616-9985, USA

The Contributor Social will be held on the evening of the 6th, at a location to be determined.

Address

Events: Location & Venue

Mon, 01 Jan 0001 00:00:00 +0000

Porte de Paris - Paris Convention Center

You MUST pick up your badge before attending the Contributor Summit or evening social event.

The summit will be in the Porte de Paris - Paris Convention Center. Masks are recommended, but not required for event attendees. Some masks will be available. In Pavilion 7 Floor 3 West

Address
1 Place de la Porte de Versailles
75015 Paris, France

Drop-off The center is located at 1 Place de la Porte de Versailles

Parking Parking F Paris is located right right next to the convention centre.

Public Transportation Paris Convention Centre is available by:
Metro: Line 12, Porte de Versailles station / Line 8, Balard station
Tramway: Lines T2 and T3a, Porte de Versailles–Parc des Expositions stop
Bus: Line 80, Porte de Versailles–Parc des Expositions stop / Line 39, Desnouettes stop
Bicycle: Vélib’ station in avenue Ernest Renan.

The Contributor Social will be held on the evening of Tuesday, 19th March, at La Serre, Paris Expo Porte de Versailles, France.

Address

Events: Location & Venue

Mon, 01 Jan 0001 00:00:00 +0000

Salt Palace Convention Center

Registration and badge pick-up will be available at the Salt Palace Convention Center. You MUST pick up your badge before attending the summit or evening social event.

The summit will be in the Salt Palace Convention Center. Masks are recommended, but not required for event attendees.

Address
90 South West Temple
Salt Lake City, Utah 84101

The Contributor Social will be held from 6pm - 9pm on November 11th, at Flanker.

Address
6 N Rio Grande St Suite 35
Salt Lake City, UT, 84101

Issues with Utah Laws

Earlier this year, the state of Utah passed HB 257. The summit staff team recognizes that HB 257 and related legislation have created an environment that could be hostile to valued members of our community.

We are not lawyers ourselves, and we rely on the interpretations of lawyers and authoritative organizations to understand the effects and risks these bills pose to ourselves and our community. We encourage each individual to assess the risk these laws and their effects pose. Some resources we recommend for better understanding the law and its potential effects include:

In the blog post linked above, the CNCF offers to provide a security escort to any attendee upon request. If any contributor attendees would like to submit a request for security to the CNCF, please contact the CNCF events team directly at events@cncf.io or the KCSNA 2024 summit staff team at summit-team@kubernetes.io.

It has been the Kubernetes’ project’s practice to hold Contributor Summits in places where there are large gatherings of contributors, even if those places have exclusionary laws. By holding Summits around the world, we try to make sure that all contributors able to travel can participate in at least one.

Because of the issues with Utah, the events team assessed the possibility of live streaming at least part of the Summit. Unfortunately, doing so was found to be far too difficult and cannot be offered.

Events: Contributor Social

Mon, 01 Jan 0001 00:00:00 +0000

From 6:30 to 8:30pm (and beyond), Kubernetes contributors will be schmoozing, eating, playing boardgames, and competing in a pub quiz at La Casa Del Mar, a cafe and bar by the beach in Valencia.

The Social is open only to registered attendees of the Kubernetes Contributor Summit and possibly their guests (see below). You must be registered before attending.

Location And Transportation

The Contributor Social will be held at the La Casa de la Mar several kilometers from the Feria.

As such, a bus will leave from The Fira (conference venue) at 6pm on May 16th to take contributors to the Social. The bus will return after 8:30pm.

Some contributors will leave from their hotels; if you want to share a cab from your hotel or another location, sign up on the cab-sharing sheet.

You are also welcome to get there on your own. There aren’t any good public transportation links to the venue.

Activities

Games! Prizes!

Lachlan Evenson will lead a live pub quiz of Kubernetes trivia. Play alone' or in teams; the winning team/player will get prizes.

Contributors are urged to bring boardgames with them to the Social. The venue has many small tables perfect for playing games with a few other contributors.

For first-time Contributor Summit attendees, we’ll also have Bingo Cards intended to help you break the ice with more experienced contributors. The first folks to complete vertical row, horizontal row, and blackout on their bingo cards will win prizes.

Food & Drink

La Casa Del Mar serves American-Spanish hybrid pub food, and we’ll have substantial snacks available for all contributors, as well as alcoholic and non-alcoholic drinks.

Bringing A Guest

Contributors will be able to bring a single family member or partner to the Social. This does not include coworkers or casual friends; our intention is to support domestic partners and close family of contributors by including them.

Guests must be fully vaccinated and adhere to all other KubeCon health & safety requirements.

If you would like to bring a guest, please fill out the request form.

If you have questions about guests, then contact us.

Events: Contributor Social

Mon, 01 Jan 0001 00:00:00 +0000

Join us at Deluxx Fluxx Detroit from 6pm to 9pm for an evening celebration after the Contributor Summit on October 24th!

There will be arcade cabinets, foosball, karaoke, trivia and more!

The contributor social is not a public event. You must be registered in advance to attend the Contributor Summit in order to attend the Social, and must be a Kubernetes contributor. Community members who are not registered and show up at the Social will be turned away.

Location

1274 Library St
Detroit, MI 48226

Bringing A Guest

NOTE: Guests must adhere to all KubeCon health & safety requirements.

To bring a guest, please email community@kubernetes.io with their information by October 17th.

Events: Contributor Social

Mon, 01 Jan 0001 00:00:00 +0000

Join us at Strandzuid from 6pm to 9pm for an evening celebration after the Contributor Summit on April 18th!

There will be food, fresh air, puzzles, and more!

Location

Europaplein 22, 1078 GZ
Amsterdam, Netherlands

Bringing A Guest

NOTE: Guests must adhere to all KubeCon health & safety requirements.

To bring a guest, please email community@kubernetes.io with their information.

Events: Contributor Social

Mon, 01 Jan 0001 00:00:00 +0000

Join us for the Contributor Social from 6pm to 9pm for an evening celebration after the Contributor Summit on November 6th!

There will be food, live music, activities, and more!

Location

Revel Motor Row 2400 S Michigan Ave Chicago, IL 60616

Poetry Slam

This year the contributor summit social will host a Kubernetes themed poetry slam. To register ahead of the event, please add your name to Kubernetes Contributor Summit Social Poetry Slam Registration.

Bringing A Guest

NOTE: Guests must adhere to all KubeCon health & safety requirements.

To bring a guest, please email summit-team@kubernetes.io with their information.

Events: Contributor Social

Mon, 01 Jan 0001 00:00:00 +0000

Join us at La Serre from 6pm to 9pm for an evening celebration after the Contributor Summit on March 19th!

There will be food, fresh air, puzzles, and more!

The Summit will include a social event open only to Contributors (and their family members, see Guests below). This event will take place somewhere near the Summit venue, and will include food, drink, entertainment, and games. More information will be available once the venue is booked.

Contributors must be registered for the Summit in order to attend the Social.

There will be food, live music, activities, and more!

Location

La Serre

2 avenue de la porte de la plaine Pavilion 6 - Paris Expo Porte de Versailles Entrance Door B 75015 Paris

Bringing A Guest

NOTE: Guests must adhere to all KubeCon health & safety requirements.

To bring a guest, please email summit-team@kubernetes.io with their information.

Events: Contributor Social

Mon, 01 Jan 0001 00:00:00 +0000

Join us at Flanker from 6pm to 9pm for an evening celebration after the Contributor Summit on November 11th!

There will be food, live music, activities, and more!

You must bring your Kubecon badge and passport or US ID (see below) to get into the Social.

Location

Flanker

6 N Rio Grande St Suite 35
Salt Lake City, UT, 84101

Bringing A Guest

NOTE: Guests must adhere to all KubeCon health & safety requirements.

To bring a guest, please email summit-team@kubernetes.io with their information no later than Sunday, November 10th at noon Mountain time.

ID Requirements

All attendees must bring acceptable identification as well as their conference badge to enter the social. The Summit Team does not control this and will not be able to make exceptions.

In most cases, this ID will be a US driver’s license, or a non-US passport. See below for more details on what kinds of ID are usable. You must bring ID for each member of your party.

21+ Admission Requirement: Flanker Kitchen & Sporting Club is strictly a 21+ venue. No individual under the age of 21 will be permitted entry, without exception.

Acceptable Identification: In compliance with Utah Code Section 32B-1-102, the following forms of identification are accepted for verifying age:

A valid Driver’s License issued by any U.S. state or territory.
A valid U.S. Military Photo Identification Card.
A valid Passport.
A U.S.-issued Passport Card.

Unacceptable Identification: The following forms of identification are not accepted for entry, as per Utah Code Section 32B-1-102:

Expired or invalid forms of identification.
Foreign or U.S.-issued Driver Privilege Cards.
Any foreign Driver’s Licenses, ID cards, or other government-issued forms of ID, except for foreign passports
Concealed Carry Permits.
Green cards, Consular Cards, or Visas.
Foreign passport cards.
Non-government-issued IDs (including student IDs, membership cards, and payment cards).