2 Dec 2022
Speaker: Geoffrey Cline
The Kubernetes community uses static site generators (Hugo+Docsy, Mkdocs, etc) and markdown to radically simplify managing open source project docs. I'm a huge fan. Some issues remain complex, namely managing different content versions, providing high quality search, and maintaining diagrams. A discussion of these problems, and a look at potential solutions.
The Kubernetes community uses static site generators (Hugo+Docsy, Mkdocs, etc) and markdown to radically simplify managing open source project docs. I'm a huge fan. Some issues remain complex, namely managing different content versions, providing high quality search, and maintaining diagrams. A discussion of these problems, and a look at potential solutions.
- 5 participants
- 20 minutes
2 Dec 2022
speakers: Craig Peters and Rishit Dagli
Contributing to open-source is fun, rewarding, and full of learning but sometimes it could just get really difficult making contributions. Some projects might require you to navigate the labyrinth of setting up a very specific environment to build the project or some high-powered hardware or some test infrastructure or some super complex setup. What if this process could be made easier and faster while solving these pain points?
Enter GitHub Codespaces and .devcontainers
In this talk Rishit, a Kubernetes contributor who often uses GitHub Codespaces, and Craig, a product manager on the GitHub Codespaces team will show how they leverage cloud environments created with Codespaces to contribute to open-source CNCF projects with a special focus on using it to contribute to Kubernetes. They also demonstrate how one can leverage .devcontainers to further customize and standardize using Codespaces. The speakers not only share their personal experiences and tips to make the most out of Codespaces but also be well suited for folks new to Codespaces and demonstrate how it can be used.
Though we greatly focus on how Codespaces make contributing to Kubernetes easier the audience for this talk could also apply these insights to contribute to other open-source projects easily and faster! This talk will have useful content for new contributors, maintainer as well as seasoned contributors.
Contributing to open-source is fun, rewarding, and full of learning but sometimes it could just get really difficult making contributions. Some projects might require you to navigate the labyrinth of setting up a very specific environment to build the project or some high-powered hardware or some test infrastructure or some super complex setup. What if this process could be made easier and faster while solving these pain points?
Enter GitHub Codespaces and .devcontainers
In this talk Rishit, a Kubernetes contributor who often uses GitHub Codespaces, and Craig, a product manager on the GitHub Codespaces team will show how they leverage cloud environments created with Codespaces to contribute to open-source CNCF projects with a special focus on using it to contribute to Kubernetes. They also demonstrate how one can leverage .devcontainers to further customize and standardize using Codespaces. The speakers not only share their personal experiences and tips to make the most out of Codespaces but also be well suited for folks new to Codespaces and demonstrate how it can be used.
Though we greatly focus on how Codespaces make contributing to Kubernetes easier the audience for this talk could also apply these insights to contribute to other open-source projects easily and faster! This talk will have useful content for new contributors, maintainer as well as seasoned contributors.
- 4 participants
- 28 minutes
2 Dec 2022
Speaker: Rob Scott
Gateway API is the next generation set of Kubernetes networking APIs, covering load balancing, routing, mesh, and more. It's already been implemented by more than a dozen projects. In this talk we want to take some time to share our experience building this API, specifically focusing on the CRD experience. We'll cover some of the benefits and drawbacks we've found when using CRDs compared with developing APIs directly in k/k. This will include our concept of release channels, our versioning and compatibility guidelines, and our experiences with validation.
Gateway API is the next generation set of Kubernetes networking APIs, covering load balancing, routing, mesh, and more. It's already been implemented by more than a dozen projects. In this talk we want to take some time to share our experience building this API, specifically focusing on the CRD experience. We'll cover some of the benefits and drawbacks we've found when using CRDs compared with developing APIs directly in k/k. This will include our concept of release channels, our versioning and compatibility guidelines, and our experiences with validation.
- 1 participant
- 27 minutes
2 Dec 2022
Speakers: Shu Mutou and Xie Ziyi
We have held kubernetes upstream training sessions at public events in Japan, e.g. CloudNative Days Tokyo, OpenSourceSummit Japan, etc., 8 times for 4 years and have gotten lots of new contributors.
It's true to get more contributors is something difficult, because of some barriers: language, culture and chance to learn how to contribute.
In the past Kubernetes Contributor Summit 2019 SanDiego, we shared how to hold the upstream training in our own country. This time, we'd like to share how we arranged the training under the COVID-19 situation.
We have held kubernetes upstream training sessions at public events in Japan, e.g. CloudNative Days Tokyo, OpenSourceSummit Japan, etc., 8 times for 4 years and have gotten lots of new contributors.
It's true to get more contributors is something difficult, because of some barriers: language, culture and chance to learn how to contribute.
In the past Kubernetes Contributor Summit 2019 SanDiego, we shared how to hold the upstream training in our own country. This time, we'd like to share how we arranged the training under the COVID-19 situation.
- 2 participants
- 22 minutes
2 Dec 2022
Speakers: Paris Pittman and Tabitha Sable
No one corporation, individual, or organization can save or sustain open source. There is no sweeping solution to sustainability, as we have seen in decades of trying to maintain the commons we all depend on. Project funding, corporate support of full-time contributors, and balance in contributors’ lives are all critical to keep a large project healthy. But this isn’t all doom and gloom: we provide hope for our own future. Join Tabitha and Paris, as they discuss how your intentionality helps our sustainability. As an organization participating or an individual donating their time, how can we help each other successfully let our projects go on without us? How do mutual aid principles apply in open source? Where do corporations fit into the larger “us”? Intentional open source strategies sustain our long term needs by supporting the people doing the work. There isn’t one person or group working on open source sustainability - we all need to in whatever way we can: through participation, sticking around, and having a plan. Walk away with a beautiful idea of how you are contributing to the long term success of Kubernetes and the open source projects that you care about.
No one corporation, individual, or organization can save or sustain open source. There is no sweeping solution to sustainability, as we have seen in decades of trying to maintain the commons we all depend on. Project funding, corporate support of full-time contributors, and balance in contributors’ lives are all critical to keep a large project healthy. But this isn’t all doom and gloom: we provide hope for our own future. Join Tabitha and Paris, as they discuss how your intentionality helps our sustainability. As an organization participating or an individual donating their time, how can we help each other successfully let our projects go on without us? How do mutual aid principles apply in open source? Where do corporations fit into the larger “us”? Intentional open source strategies sustain our long term needs by supporting the people doing the work. There isn’t one person or group working on open source sustainability - we all need to in whatever way we can: through participation, sticking around, and having a plan. Walk away with a beautiful idea of how you are contributing to the long term success of Kubernetes and the open source projects that you care about.
- 2 participants
- 23 minutes
2 Dec 2022
Speaker: Stefan Schimanski
We have CRDs and operators since 2016. Where are we heading as community with them? Are they solving the problems we have today?
We believe: CRDs and the patterns around them block innovation and collaboration in the ecosystem. The problem landscape is not anymore that of 2016. CRDs were never made to connect services of multiple clusters, or to consume APIs of 3rdparty service providers. Kubernetes does not provide the service consumption model of today. The ecosystem has learned to work around this, with lots of toil and complexity.
"kubectl bind" is a vision for a world where SaaS can natively be consumed, without all the complexity of running operators and the immense cost of building them:
$ kubectl krew install bind
$ kubectl bind service https://mangodb.com
BOOM – we can create resources. Vendor neutral. Native. Nocode. Nopods. Nooperators.
We have CRDs and operators since 2016. Where are we heading as community with them? Are they solving the problems we have today?
We believe: CRDs and the patterns around them block innovation and collaboration in the ecosystem. The problem landscape is not anymore that of 2016. CRDs were never made to connect services of multiple clusters, or to consume APIs of 3rdparty service providers. Kubernetes does not provide the service consumption model of today. The ecosystem has learned to work around this, with lots of toil and complexity.
"kubectl bind" is a vision for a world where SaaS can natively be consumed, without all the complexity of running operators and the immense cost of building them:
$ kubectl krew install bind
$ kubectl bind service https://mangodb.com
BOOM – we can create resources. Vendor neutral. Native. Nocode. Nopods. Nooperators.
- 2 participants
- 30 minutes
2 Dec 2022
Speaker: Sergey Kanzhelev
Every Community is defined by its values. It attracts people thinking alike and people evolve these values. In this session we will try to formulate Kubernetes Technical values. When making a technical tradeoff do we care about performance or consistency, opinionated API or generalization, taking dependencies or pushing dependencies. The session will have an intro that will put some structure to the discussion and will be an open discussions forum from there.
Every Community is defined by its values. It attracts people thinking alike and people evolve these values. In this session we will try to formulate Kubernetes Technical values. When making a technical tradeoff do we care about performance or consistency, opinionated API or generalization, taking dependencies or pushing dependencies. The session will have an intro that will put some structure to the discussion and will be an open discussions forum from there.
- 6 participants
- 26 minutes
2 Dec 2022
Speakers: Surya Seetharaman and Andrew Stoycos
Although the NetworkPolicy API allows developers to secure applications, admins have been forced to use out-of-tree APIs to secure clusters. This is evident by the large number of disparate CRDs offered by CNI plugins, such as Cilium’s ClusterWideNetworkPolicy and Calico’s GlobalNetworkPolicy. The SIG Network Policy API subgroup believes that such functionality should be provided by the core Kubernetes community to make cross-vendor portability possible and provide a standard solution for plugins which do not already implement such an API. The AdminNetworkPolicy API, written by a diverse group of community members and designed to specifically meet the needs of the cluster admin, is this solution. To date it has undergone two years of active development and over 800 (and counting) GitHub review comments, highlighting both the challenges and benefits of open source API development. This session will present the new API to the wider community and teach best practices regarding its use. Such learnings will enable the community to quickly adopt the AdminNetworkPolicy API and ensure future iterations include ideas from users throughout the Kubernetes ecosystem.
Although the NetworkPolicy API allows developers to secure applications, admins have been forced to use out-of-tree APIs to secure clusters. This is evident by the large number of disparate CRDs offered by CNI plugins, such as Cilium’s ClusterWideNetworkPolicy and Calico’s GlobalNetworkPolicy. The SIG Network Policy API subgroup believes that such functionality should be provided by the core Kubernetes community to make cross-vendor portability possible and provide a standard solution for plugins which do not already implement such an API. The AdminNetworkPolicy API, written by a diverse group of community members and designed to specifically meet the needs of the cluster admin, is this solution. To date it has undergone two years of active development and over 800 (and counting) GitHub review comments, highlighting both the challenges and benefits of open source API development. This session will present the new API to the wider community and teach best practices regarding its use. Such learnings will enable the community to quickly adopt the AdminNetworkPolicy API and ensure future iterations include ideas from users throughout the Kubernetes ecosystem.
- 3 participants
- 24 minutes
2 Dec 2022
Speakers: Adolfo García Veytia, Benjamin Elder and Arnaud Meukam
In the middle of 2022, the official Kubernetes registry was moved to registry.k8s.io. This change is only the most visible part of big improvements going on behind the scenes led by SIG K8s-Infra to lower our image serving costs.
In this session, Arnaud, Ben, and Puerco will go through some of the challenges involved in distributing the registry and how the new serving mechanism ensures we'll preserve the project's financials better. We'll talk about what the registry change means to projects under the Kubernetes umbrella and to our downstream consumers.
Finally, a reminder that there is still work to do to get KEP-3000 across the finish line! We'll go over a brief overview on what is still missing and how you can help us get there.
In the middle of 2022, the official Kubernetes registry was moved to registry.k8s.io. This change is only the most visible part of big improvements going on behind the scenes led by SIG K8s-Infra to lower our image serving costs.
In this session, Arnaud, Ben, and Puerco will go through some of the challenges involved in distributing the registry and how the new serving mechanism ensures we'll preserve the project's financials better. We'll talk about what the registry change means to projects under the Kubernetes umbrella and to our downstream consumers.
Finally, a reminder that there is still work to do to get KEP-3000 across the finish line! We'll go over a brief overview on what is still missing and how you can help us get there.
- 9 participants
- 26 minutes