Kubernetes SIG Node Intro and Deep Dive

These are exciting times for Kubernetes SIG Node. Come to our maintainers‘ track session to learn about the just released version 1.34 of Kubernetes, full of exciting improvements, and get a glance into the SIG Node roadmap. SIG Node owns components that control interactions between pods and host resources, including the Kubelet, Container Runtime Interface (CRI), and Node API. SIG Node is responsible for the Pod’s lifecycle from allocation to teardown, to liveness checks and shared resource management. We work with the various container runtimes, kernels, networking, storage, and more; anything a pod touches is SIG Node’s responsibility!

We will make a deep dive into the area of pod lifecycle starting with developments like evented PLEG as well as well established things like probes and handling the resource management when pod scaling.

Join this session to learn more about our SIG, and how you might get involved to make Node even better!

Kubernetes New Contributor Orientation

This meeting is meant to orient you in the Kubernetes community.

Part 1: Presentation and Intro
● Welcome to Kubernetes!
● What is Kubernetes?
● Kubernetes Community Structure
● What does it mean to be a “Contributor”?
● How to Start Contributing
● Current Work Opportunities
● Contribution Pitfalls

Part 2: New contributors journey
We will invite some new contributors in the community to share their fresh experience and tips to you.
● How did I get involved with Kubernetes?
● What is most important in participating in Kubernetes community journey?
● Some tip to participate in Kubernetes community
● How to submit a "polite" PR?

A Huge Cluster or Multi-Clusters? Identifying the Bottleneck

The increasing complexity of Kubernetes deployments has sparked a debate between scaling single clusters to enormous sizes and managing multiple clusters. At KubeCon NA24, the CNCF Tech Landscape Radar unveiled insights into multicluster application management, while Google showcased a 65000-node cluster powered by Spanner, bypassing etcd's limitations. Similarly, ByteDance has achieved multi-tenancy at scale with Kubebrain.

This talk examines the challenges of large clusters (5,000+ nodes and beyond) and the trade-offs of multicluster solutions. Key topics include API server options, etcd tuning and alternatives (e.g., Kubebrain, kine), and operational concerns such as multi-tenancy models (vCluster, kubezoo, HNC), and operator version control. In parallel, multicluster management solutions like Karmada, Clusternet, and networking challenges with tools like Submariner are explored.

Attendees will gain actionable insights into selecting the most appropriate strategy for their needs.

Kubernetes 社区： 从新手到影响者

圆桌讨论：我们需要什么样的开源教育

Manage your cluster in the easy way!

Kubernetes has the rhythm of 3~4 releases each year, and users are suffering to keep upgrading their increasing clusters and larger clusters. Besides this, how to manage the CA in a cluster and upgrade the cluster config on-the-fly is also what the end-user is looking for.

In this session, we will bring some updates from wg-lts (long term support), particularly, the strategies like how long will the kubernetes community support a version officially and what is the scope of the LTS version, we will take a close look at klts [1] as well.

We will compare a couple of available solutions for how to manage Kubernetes cluster effectively, cluster-api, kops etc.

Also, we will take a glance over an on-going in-house project kubeadm-operator for how to upgrade k8s cluster with declarative language, and the support of the certificate renewal, certificate authority rotation, update the cluster config across different nodes in your cluster！

[1] https://github.com/klts-io/kubernetes-lts

Deep Dive into Kernel Requirements: strengthening Cloud-Native with new kernel features

- Kubernetes 1.31: Moving cgroup v1 Support into Maintenance Mode: making cgroup v2 (kernel 5.8+) a key requirement.
- Linux Kernel Version Requirements shows kernel requirements of Kubernetes features
- eBPF and Modern Networking and observibility

This talk will provide a detailed look at the kernel version requirements for Kubernetes, with a focus on evolving trends in AI infrastructure, SIG-Node, and SIG-Network. We will explore how different kernel versions influence Kubernetes cluster operations, especially in the areas of network performance, resource management, and security enhancements. This session will also highlight some of the rising star projects in the cloud-native ecosystem, including Cilium, Falco, Pyroscope, Kepler and DeepFlow.

Key Topics:
- AI Infrastructure(device related)
- Kubernetes SIG-Node(cgroup)
- Kubernetes SIG-Network(nftables)
- eBPF-based Projects requirements
- Is kernel version checked enough?
- Dependencies/Ecosystem Maintenance

Kubernetes Community Panel: A Decade of Evolution and Future Trends

Join us in celebrating the 10th anniversary of Kubernetes with a panel featuring some of the community's most influential contributors and maintainers from China. Over the past decade, Kubernetes has grown to the cornerstone of cloud-native infra, thanks to the dedication and innovation of its community members. In this panel, we will talk about our journeys with Kubernetes, share stories and experience, and discuss the future of Kubernetes in the next decade. Our panelists include current and previous owners, tech leads and maintainers. Feel free to join the panel to share your perspectives on the past and next decade of the Kubernetes community and ask anything about the community.

How the Kubernetes Release Shadow Program Enables Contributors To Manage Releases Effectively?

Ever wondered how a community of volunteers maintains the world's most popular container orchestration system? From addressing the ever-challenging cloud security concerns to bringing new features to the table to helping develop an inclusive network of like-minded folks, the Kubernetes community manages to do it all.
Amid this, the Kubernetes Release Shadow Program stands out as a chance for contributors to be a part of a time-bound commitment in the release process. Also, understand the nuances of sustaining the project, including shadow roles and multiple releases before the final cut.
This talk explores how the program is an ideal means for all experienced and new contributors to become acquainted with various components of the release and various SIGs within the ecosystem. We'll also talk about how the program serves as a guide for other OSS projects, regardless of scale, so they can use all the knowledge gained so far and utilize it to their benefit.

Kubernetes SIG Node Intro and Deep Dive

These are exciting times for Kubernetes SIG Node. Come to our maintainers‘ track session to learn about the just released version 1.28 of Kubernetes, full of exciting improvements, and get a glance into the SIG Node roadmap.

SIG Node owns components that control interactions between pods and host resources, including the Kubelet, Container Runtime Interface (CRI), and Node API. SIG Node is responsible for the Pod’s lifecycle from allocation to teardown, to liveness checks and shared resource management. We work with the various container runtimes, kernels, networking, storage, and more; anything a pod touches is SIG Node’s responsibility!

We will discuss how kubelet handles pod lifecycle including probes and hooks, how node and pod gracefully shutdown as well as many other improvements.

Join this session to learn more about our SIG, and how you might get involved to make Node even better!

How can Pod start-up be accelerated on nodes in large clusters?

The idea came from my recently written blog [Kubernetes 1.27: updates on speeding up Pod startup](https://kubernetes.io/blog/2023/05/15/speed-up-pod-startup/).

This is a common issue that cluster administrators may face.
This session will show you the process of pod startup and everything about how to speed up the startup of pods.

1. API: the creation time of pods by controller-manager, KCM: PV & PVC binding and webhooks.
2. Scheduling: GPU Topology-aware, node load aware
3. Node level from the kubelet side: Image Pulling, Sidecar, API QPS & Burs, Event-Driven PLEG, Throttling, Disk and Volume driver, Static CPU Policy, Container Runtime
4. GPU Management: Topology not only NUMA, Sharing, and Monitoring
5. Data load: data preload & local storage or distributed storage
6. Observability: How to check why the pod starts up slowly?