<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Contributor Blog on Kubernetes Contributors</title><link>https://www.kubernetes.dev/blog/</link><description>Recent content in Contributor Blog on Kubernetes Contributors</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 28 Jul 2026 10:00:00 -0800</lastBuildDate><atom:link href="https://www.kubernetes.dev/blog/index.xml" rel="self" type="application/rss+xml"/><item><title>KCD Around the World: New York</title><link>https://www.kubernetes.dev/blog/2026/07/28/kcd-around-the-world-new-york/</link><pubDate>Tue, 28 Jul 2026 10:00:00 -0800</pubDate><guid>https://www.kubernetes.dev/blog/2026/07/28/kcd-around-the-world-new-york/</guid><description>&lt;p>Welcome to KCD Around the World, a new series where we explore &lt;a href="https://www.cncf.io/kcds/"
 
 target="_blank" rel="noopener">Kubernetes Community Days&lt;/a>
 from every corner of the globe. When most people think of KCD, they think about talks and technical sessions, but behind every event is a community of volunteers, contributors, organizers and attendees who make it all happen. Through conversations with the people behind each KCD, we&amp;rsquo;ll share what makes it unique.&lt;/p>
&lt;p>Our first stop: New York City. To learn what made this year&amp;rsquo;s event special, we interview Christopher Tineo, one of the organizers for KCD NY 2026.&lt;/p></description></item><item><title>Human-Centered Automation for Kubernetes Localization in the AI Era</title><link>https://www.kubernetes.dev/blog/2026/06/26/human-centered-automation-kubernetes-localization-ai-era/</link><pubDate>Fri, 26 Jun 2026 14:00:00 -0800</pubDate><guid>https://www.kubernetes.dev/blog/2026/06/26/human-centered-automation-kubernetes-localization-ai-era/</guid><description>&lt;p>This year, the Kubernetes localization subproject participated in LFX Mentorship for the first time through the project &lt;a href="https://mentorship.lfx.linuxfoundation.org/project/c71fdb2a-8e77-447d-ae8b-3e977e0fd86a"
 
 target="_blank" rel="noopener">&amp;ldquo;CNCF - Kubernetes: SIG Docs Localization: AI-era localization automation&amp;rdquo;&lt;/a>
. The work was also tracked in &lt;a href="https://github.com/kubernetes/website/issues/54075"
 
 target="_blank" rel="noopener">kubernetes/website#54075&lt;/a>
.&lt;/p>
&lt;p>As the mentee on this project, I worked with Kubernetes SIG Docs localization mentors on a practical maintenance question:&lt;/p>
&lt;blockquote>
&lt;p>In an era of rapidly improving AI translation tools, what kind of automation actually helps localization maintainers?&lt;/p>&lt;/blockquote>
&lt;p>Kubernetes documentation is used by readers around the world. Localization helps make the project more accessible to users and contributors by providing content in their native languages. But localization is not only about translating pages once. It is also about maintaining those pages as Kubernetes changes.&lt;/p></description></item><item><title>Open source maintainership in the age of AI</title><link>https://www.kubernetes.dev/blog/2026/06/26/open-source-maintainership-in-the-age-of-ai/</link><pubDate>Fri, 26 Jun 2026 10:00:00 -0800</pubDate><guid>https://www.kubernetes.dev/blog/2026/06/26/open-source-maintainership-in-the-age-of-ai/</guid><description>&lt;p>AI has really changed the game around software development.
More people are leveraging AI than ever to contribute patches to projects they use.
To me, this is a good thing as more folks will contribute patches rather than fork or not fix them.
The main problem is that AI has made generating code fast but there has been very little improvement in maintaining code bases.
In this post, we will highlight the ways the Kubernetes community is adapting to the world of AI assisted coding.&lt;/p></description></item><item><title>Spotlight on WG Device Management</title><link>https://www.kubernetes.dev/blog/2026/06/24/wg-device-management-spotlight-2026/</link><pubDate>Wed, 24 Jun 2026 10:00:00 -0800</pubDate><guid>https://www.kubernetes.dev/blog/2026/06/24/wg-device-management-spotlight-2026/</guid><description>&lt;p>The rising popularity of AI, Edge, and Telecommunications workloads on Kubernetes has led to new requirements for hardware management. We now need hardware specification beyond CPU time and memory allocations. This includes allocating GPUs, TPUs, network interfaces, and other hardware, sometimes after pod start and occasionally through time-sharing.&lt;/p>
&lt;p>Efficiently managing this specialized hardware is the mission of the &lt;strong>&lt;a href="https://www.kubernetes.dev/community/community-groups/wg/device-management/"
 
 target="_blank" rel="noopener">Device Management Working Group&lt;/a>
&lt;/strong>. Their cornerstone project, &lt;strong>&lt;a href="https://kubernetes.io/docs/concepts/scheduling-eviction/dynamic-resource-allocation/"
 
 target="_blank" rel="noopener">Dynamic Resource Allocation (DRA)&lt;/a>
&lt;/strong>, recently graduated to GA, marking a fundamental shift in how the project handles hardware-intensive workloads at scale.&lt;/p></description></item><item><title>Spotlight on SIG Storage</title><link>https://www.kubernetes.dev/blog/2026/06/15/sig-storage-spotlight-2026/</link><pubDate>Mon, 15 Jun 2026 00:00:00 +0000</pubDate><guid>https://www.kubernetes.dev/blog/2026/06/15/sig-storage-spotlight-2026/</guid><description>&lt;p>In our ongoing SIG Spotlight series, we shine a light on the groups that keep the Kubernetes project
moving forward. This time, we catch up with &lt;strong>&lt;a href="https://github.com/kubernetes/community/tree/main/sig-storage"
 
 target="_blank" rel="noopener">SIG
Storage&lt;/a>
&lt;/strong>, the group responsible
for persistent data, volume management, and the interfaces that connect Kubernetes workloads to the
storage systems beneath them.&lt;/p>
&lt;p>We spoke with &lt;a href="https://github.com/xing-yang"
 
 target="_blank" rel="noopener">Xing Yang&lt;/a>
, Co-Chair of SIG Storage and Software
Engineer at VMware by Broadcom, about the SIG&amp;rsquo;s history, the features shipping in recent Kubernetes
releases, and where storage in Kubernetes is headed as AI workloads become the norm.&lt;/p></description></item><item><title>Eliminating Kubernetes Image Signature Replication</title><link>https://www.kubernetes.dev/blog/2026/06/05/image-signature-routing/</link><pubDate>Fri, 05 Jun 2026 00:00:00 +0000</pubDate><guid>https://www.kubernetes.dev/blog/2026/06/05/image-signature-routing/</guid><description>&lt;p>The &lt;a href="https://kubernetes.io/blog/2026/03/17/image-promoter-rewrite/"
 
 target="_blank" rel="noopener">image promoter rewrite&lt;/a>
 laid the
groundwork for simplifying how Kubernetes delivers container image signatures.
One of the rewrite phases (Phase 6) separated image signing from signature
replication into distinct pipeline stages. This follow-up covers the next step:
eliminating signature replication entirely.&lt;/p>
&lt;h2 id="the-problem">The problem&lt;/h2>
&lt;p>After promoting container images to &lt;code>registry.k8s.io&lt;/code>, the promoter signs them
using &lt;a href="https://github.com/sigstore/cosign"
 
 target="_blank" rel="noopener">cosign&lt;/a>
 with keyless (OIDC)
signatures. These signatures are stored as OCI artifacts alongside the images,
tagged with the convention &lt;code>sha256-&amp;lt;digest&amp;gt;.sig&lt;/code> and &lt;code>sha256-&amp;lt;digest&amp;gt;.att&lt;/code>.&lt;/p></description></item><item><title>Announcing the AI Gateway Working Group</title><link>https://www.kubernetes.dev/blog/2026/03/09/announcing-ai-gateway-wg/</link><pubDate>Mon, 09 Mar 2026 00:00:00 +0000</pubDate><guid>https://www.kubernetes.dev/blog/2026/03/09/announcing-ai-gateway-wg/</guid><description>&lt;p>The community around Kubernetes includes a number of Special Interest Groups (SIGs) and Working Groups (WGs) facilitating discussions on important topics between interested contributors. Today, we&amp;rsquo;re excited to announce the formation of the &lt;a href="https://github.com/kubernetes-sigs/wg-ai-gateway"
 
 target="_blank" rel="noopener">AI Gateway Working Group&lt;/a>
, a new initiative focused on developing standards and best practices for networking infrastructure that supports AI workloads in Kubernetes environments.&lt;/p>
&lt;h2 id="what-is-an-ai-gateway">What is an AI Gateway?&lt;/h2>
&lt;p>In a Kubernetes context, an &lt;em>AI Gateway&lt;/em> refers to network gateway infrastructure (including proxy servers, load-balancers, etc.) that generally implements the &lt;a href="https://gateway-api.sigs.k8s.io/"
 
 target="_blank" rel="noopener">Gateway API&lt;/a>
 specification with enhanced capabilities for AI workloads. Rather than defining a distinct product category, AI Gateways describe infrastructure designed to enforce policy on AI traffic, including:&lt;/p></description></item><item><title>Spotlight on SIG Architecture: API Governance</title><link>https://www.kubernetes.dev/blog/2026/02/12/sig-architecture-api/</link><pubDate>Thu, 12 Feb 2026 00:00:00 +0000</pubDate><guid>https://www.kubernetes.dev/blog/2026/02/12/sig-architecture-api/</guid><description>&lt;p>&lt;em>This is the fifth interview of a SIG Architecture Spotlight series that covers the different
subprojects, and we will be covering &lt;a href="https://github.com/kubernetes/community/blob/main/sig-architecture/README.md#architecture-and-api-governance-1"
 
 target="_blank" rel="noopener">SIG Architecture: API
Governance&lt;/a>
.&lt;/em>&lt;/p>
&lt;p>In this SIG Architecture spotlight we talked with &lt;a href="https://github.com/liggitt"
 
 target="_blank" rel="noopener">Jordan Liggitt&lt;/a>
, lead
of the API Governance sub-project.&lt;/p>
&lt;h2 id="introduction">Introduction&lt;/h2>
&lt;p>&lt;strong>FM: Hello Jordan, thank you for your availability. Tell us a bit about yourself, your role and how
you got involved in Kubernetes.&lt;/strong>&lt;/p>
&lt;p>&lt;strong>JL&lt;/strong>: My name is Jordan Liggitt. I&amp;rsquo;m a Christian, husband, father of four, software engineer at
&lt;a href="https://about.google/"
 
 target="_blank" rel="noopener">Google&lt;/a>
 by day, and &lt;a href="https://www.youtube.com/watch?v=UDdr-VIWQwo"
 
 target="_blank" rel="noopener">amateur musician&lt;/a>
 by stealth. I was born in Texas (and still
like to claim it as my point of origin), but I&amp;rsquo;ve lived in North Carolina for most of my life.&lt;/p></description></item><item><title>Announcing the Checkpoint/Restore Working Group</title><link>https://www.kubernetes.dev/blog/2026/01/21/introducing-checkpoint-restore-wg/</link><pubDate>Wed, 21 Jan 2026 00:00:00 +0000</pubDate><guid>https://www.kubernetes.dev/blog/2026/01/21/introducing-checkpoint-restore-wg/</guid><description>&lt;p>The community around Kubernetes includes a number of Special Interest Groups (SIGs) and Working Groups (WGs) facilitating discussions on important topics between interested contributors. Today we would like to announce the new &lt;a href="https://github.com/kubernetes/community/tree/main/wg-checkpoint-restore"
 
 target="_blank" rel="noopener">Kubernetes Checkpoint Restore WG&lt;/a>
 focusing on the integration of Checkpoint/Restore functionality into Kubernetes.&lt;/p>
&lt;h2 id="motivation-and-use-cases">Motivation and use cases&lt;/h2>
&lt;p>There are several high-level scenarios discussed in the working group:&lt;/p>
&lt;ul>
&lt;li>Optimizing resource utilization for interactive workloads, such as Jupyter notebooks and AI chatbots&lt;/li>
&lt;li>Accelerating startup of applications with long initialization times, including Java applications and &lt;a href="https://doi.org/10.1145/3731599.3767354"
 
 target="_blank" rel="noopener">LLM inference services&lt;/a>
&lt;/li>
&lt;li>Using periodic checkpointing to enable fault-tolerance for long-running workloads, such as distributed model training&lt;/li>
&lt;li>Providing &lt;a href="https://doi.org/10.1007/978-3-032-10507-3_3"
 
 target="_blank" rel="noopener">interruption-aware scheduling&lt;/a>
 with transparent checkpoint/restore, allowing lower-priority Pods to be preempted while preserving the runtime state of applications&lt;/li>
&lt;li>Facilitating Pod migration across nodes for load balancing and maintenance, without disrupting workloads.&lt;/li>
&lt;li>Enabling forensic checkpointing to investigate and analyze security incidents such as cyberattacks, data breaches, and unauthorized access.&lt;/li>
&lt;/ul>
&lt;p>Across these scenarios, the goal is to help facilitate discussions of ideas between the Kubernetes community and the growing Checkpoint/Restore in Userspace (CRIU) ecosystem. The CRIU community includes several projects that support these use cases, including:&lt;/p></description></item><item><title>Ingress NGINX Retirement: What You Need to Know</title><link>https://www.kubernetes.dev/blog/2025/11/12/ingress-nginx-retirement/</link><pubDate>Wed, 12 Nov 2025 12:00:00 -0500</pubDate><guid>https://www.kubernetes.dev/blog/2025/11/12/ingress-nginx-retirement/</guid><description>&lt;p>To prioritize the safety and security of the ecosystem, Kubernetes SIG Network and the Security Response Committee are announcing the upcoming retirement of &lt;a href="https://github.com/kubernetes/ingress-nginx/"
 
 target="_blank" rel="noopener">Ingress NGINX&lt;/a>
. Best-effort maintenance will continue until March 2026. Afterward, there will be no further releases, no bugfixes, and no updates to resolve any security vulnerabilities that may be discovered. &lt;strong>Existing deployments of Ingress NGINX will continue to function and installation artifacts will remain available.&lt;/strong>&lt;/p>
&lt;p>We recommend migrating to one of the many alternatives. Consider &lt;a href="https://gateway-api.sigs.k8s.io/guides/"
 
 target="_blank" rel="noopener">migrating to Gateway API&lt;/a>
, the modern replacement for Ingress. If you must continue using Ingress, many alternative Ingress controllers are &lt;a href="https://kubernetes.io/docs/concepts/services-networking/ingress-controllers/"
 
 target="_blank" rel="noopener">listed in the Kubernetes documentation&lt;/a>
. Continue reading for further information about the history and current state of Ingress NGINX, as well as next steps.&lt;/p></description></item><item><title>Announcing the 2025 Steering Committee Election Results</title><link>https://www.kubernetes.dev/blog/2025/11/09/steering-committee-results-2025/</link><pubDate>Sun, 09 Nov 2025 15:10:00 -0500</pubDate><guid>https://www.kubernetes.dev/blog/2025/11/09/steering-committee-results-2025/</guid><description>&lt;p>The &lt;a href="https://github.com/kubernetes/community/tree/main/elections/steering/2025"
 
 target="_blank" rel="noopener">2025 Steering Committee Election&lt;/a>
 is now complete. The Kubernetes Steering Committee consists of 7 seats, 4 of which were up for election in 2025. Incoming committee members serve a term of 2 years, and all members are elected by the Kubernetes Community.&lt;/p>
&lt;p>The Steering Committee oversees the governance of the entire Kubernetes project. With that great power comes great responsibility. You can learn more about the steering committee’s role in their &lt;a href="https://github.com/kubernetes/steering/blob/main/charter.md"
 
 target="_blank" rel="noopener">charter&lt;/a>
.&lt;/p></description></item><item><title>Spotlight on Policy Working Group</title><link>https://www.kubernetes.dev/blog/2025/10/18/wg-policy-spotlight-2025/</link><pubDate>Sat, 18 Oct 2025 00:00:00 +0000</pubDate><guid>https://www.kubernetes.dev/blog/2025/10/18/wg-policy-spotlight-2025/</guid><description>&lt;p>&lt;em>(Note: The Policy Working Group has completed its mission and is no longer active. This article reflects its work, accomplishments, and insights into how a working group operates.)&lt;/em>&lt;/p>
&lt;p>In the complex world of Kubernetes, policies play a crucial role in managing and securing clusters. But have you ever wondered how these policies are developed, implemented, and standardized across the Kubernetes ecosystem? To answer that, let&amp;rsquo;s take a look back at the work of the Policy Working Group.&lt;/p></description></item><item><title>Spotlight on the Kubernetes Steering Committee</title><link>https://www.kubernetes.dev/blog/2025/09/22/k8s-steering-spotlight-2025/</link><pubDate>Mon, 22 Sep 2025 00:00:00 +0000</pubDate><guid>https://www.kubernetes.dev/blog/2025/09/22/k8s-steering-spotlight-2025/</guid><description>&lt;p>&lt;em>This interview was conducted in August 2024, and due to the dynamic nature of the Steering
Committee membership and election process it might not represent the actual composition accurately.
The topics covered are, however, overwhelmingly relevant to understand its scope of work. As we
approach the Steering Committee elections, it provides useful insights into the workings of the
Committee.&lt;/em>&lt;/p>
&lt;p>The &lt;a href="https://github.com/kubernetes/steering"
 
 target="_blank" rel="noopener">Kubernetes Steering Committee&lt;/a>
 is the backbone of the
Kubernetes project, ensuring that its vibrant community and governance structures operate smoothly
and effectively. While the technical brilliance of Kubernetes is often spotlighted through its
&lt;a href="https://github.com/kubernetes/community"
 
 target="_blank" rel="noopener">Special Interest Groups (SIGs) and Working Groups (WGs)&lt;/a>
,
the unsung heroes quietly steering the ship are the members of the Steering Committee. They tackle
complex organizational challenges, empower contributors, and foster the thriving open source
ecosystem that Kubernetes is celebrated for.&lt;/p></description></item><item><title>Post-Quantum Cryptography in Kubernetes</title><link>https://www.kubernetes.dev/blog/2025/07/18/pqc-in-k8s/</link><pubDate>Fri, 18 Jul 2025 00:00:00 +0000</pubDate><guid>https://www.kubernetes.dev/blog/2025/07/18/pqc-in-k8s/</guid><description>&lt;p>The world of cryptography is on the cusp of a major shift with the advent of
quantum computing. While powerful quantum computers are still largely
theoretical for many applications, their potential to break current
cryptographic standards is a serious concern, especially for long-lived
systems. This is where &lt;em>Post-Quantum Cryptography&lt;/em> (PQC) comes in. In this
article, I'll dive into what PQC means for TLS and, more specifically, for the
Kubernetes ecosystem. I&amp;rsquo;ll explain what the (suprising) state of PQC in
Kubernetes is and what the implications are for current and future clusters.&lt;/p></description></item><item><title>Changes to Kubernetes Slack</title><link>https://www.kubernetes.dev/blog/2025/06/16/changes-to-kubernetes-slack-2025/</link><pubDate>Mon, 16 Jun 2025 00:00:00 +0000</pubDate><guid>https://www.kubernetes.dev/blog/2025/06/16/changes-to-kubernetes-slack-2025/</guid><description>&lt;p>&lt;strong>UPDATE&lt;/strong>: We’ve received notice from Salesforce that our Slack workspace &lt;strong>WILL NOT BE DOWNGRADED&lt;/strong> on June 20th. Stand by for more details, but for now, there is no urgency to back up private channels or direct messages.&lt;/p>
&lt;p>&lt;del>Kubernetes Slack will lose its special status and will be changing into a standard free Slack on June 20, 2025&lt;/del>. Sometime later this year, our community may move to a new platform. If you are responsible for a channel or private channel, or a member of a User Group, you will need to take some actions as soon as you can.&lt;/p></description></item><item><title>Spotlight on SIG Apps</title><link>https://www.kubernetes.dev/blog/2025/03/12/sig-apps-spotlight-2025/</link><pubDate>Wed, 12 Mar 2025 00:00:00 +0000</pubDate><guid>https://www.kubernetes.dev/blog/2025/03/12/sig-apps-spotlight-2025/</guid><description>&lt;p>In our ongoing SIG Spotlight series, we dive into the heart of the Kubernetes project by talking to
the leaders of its various Special Interest Groups (SIGs). This time, we focus on
&lt;strong>&lt;a href="https://github.com/kubernetes/community/tree/main/sig-apps#apps-special-interest-group"
 
 target="_blank" rel="noopener">SIG Apps&lt;/a>
&lt;/strong>,
the group responsible for everything related to developing, deploying, and operating applications on
Kubernetes. &lt;a href="https://www.linkedin.com/in/sandipanpanda"
 
 target="_blank" rel="noopener">Sandipan Panda&lt;/a>

(&lt;a href="https://www.devzero.io/"
 
 target="_blank" rel="noopener">DevZero&lt;/a>
) had the opportunity to interview &lt;a href="https://github.com/soltysh"
 
 target="_blank" rel="noopener">Maciej
Szulik&lt;/a>
 (&lt;a href="https://defenseunicorns.com/"
 
 target="_blank" rel="noopener">Defense Unicorns&lt;/a>
) and &lt;a href="https://github.com/janetkuo"
 
 target="_blank" rel="noopener">Janet
Kuo&lt;/a>
 (&lt;a href="https://about.google/"
 
 target="_blank" rel="noopener">Google&lt;/a>
), the chairs and tech leads of
SIG Apps. They shared their experiences, challenges, and visions for the future of application
management within the Kubernetes ecosystem.&lt;/p></description></item><item><title>Spotlight on SIG etcd</title><link>https://www.kubernetes.dev/blog/2025/03/04/sig-etcd-spotlight/</link><pubDate>Tue, 04 Mar 2025 00:00:00 +0000</pubDate><guid>https://www.kubernetes.dev/blog/2025/03/04/sig-etcd-spotlight/</guid><description>&lt;p>In this SIG etcd spotlight we talked with &lt;a href="https://github.com/jmhbnz"
 
 target="_blank" rel="noopener">James Blair&lt;/a>
, &lt;a href="https://github.com/serathius"
 
 target="_blank" rel="noopener">Marek
Siarkowicz&lt;/a>
, &lt;a href="https://github.com/wenjiaswe"
 
 target="_blank" rel="noopener">Wenjia Zhang&lt;/a>
, and
&lt;a href="https://github.com/ahrtr"
 
 target="_blank" rel="noopener">Benjamin Wang&lt;/a>
 to learn a bit more about this Kubernetes Special Interest
Group.&lt;/p>
&lt;h2 id="introducing-sig-etcd">Introducing SIG etcd&lt;/h2>
&lt;p>&lt;strong>Frederico: Hello, thank you for the time! Let’s start with some introductions, could you tell us a
bit about yourself, your role and how you got involved in Kubernetes.&lt;/strong>&lt;/p>
&lt;p>&lt;strong>Benjamin:&lt;/strong> Hello, I am Benjamin. I am a SIG etcd Tech Lead and one of the etcd maintainers. I
work for VMware, which is part of the Broadcom group. I got involved in Kubernetes &amp;amp; etcd &amp;amp; CSI
(&lt;a href="https://github.com/container-storage-interface/spec/blob/master/spec.md"
 
 target="_blank" rel="noopener">Container Storage Interface&lt;/a>
)
because of work and also a big passion for open source. I have been working on Kubernetes &amp;amp; etcd
(and also CSI) since 2020.&lt;/p></description></item><item><title>Spotlight on SIG Architecture: Enhancements</title><link>https://www.kubernetes.dev/blog/2025/01/21/sig-architecture-enhancements/</link><pubDate>Tue, 21 Jan 2025 00:00:00 +0000</pubDate><guid>https://www.kubernetes.dev/blog/2025/01/21/sig-architecture-enhancements/</guid><description>&lt;p>&lt;em>This is the fourth interview of a SIG Architecture Spotlight series that will cover the different
subprojects, and we will be covering &lt;a href="https://github.com/kubernetes/community/blob/main/sig-architecture/README.md#enhancements"
 
 target="_blank" rel="noopener">SIG Architecture:
Enhancements&lt;/a>
.&lt;/em>&lt;/p>
&lt;p>In this SIG Architecture spotlight we talked with &lt;a href="https://github.com/kikisdeliveryservice"
 
 target="_blank" rel="noopener">Kirsten
Garrison&lt;/a>
, lead of the Enhancements subproject.&lt;/p>
&lt;h2 id="the-enhancements-subproject">The Enhancements subproject&lt;/h2>
&lt;p>&lt;strong>Frederico (FSM): Hi Kirsten, very happy to have the opportunity to talk about the Enhancements
subproject. Let&amp;rsquo;s start with some quick information about yourself and your role.&lt;/strong>&lt;/p></description></item><item><title>Spotlight on Kubernetes Upstream Training in Japan</title><link>https://www.kubernetes.dev/blog/2024/10/28/k8s-upstream-training-japan-spotlight/</link><pubDate>Mon, 28 Oct 2024 00:00:00 +0000</pubDate><guid>https://www.kubernetes.dev/blog/2024/10/28/k8s-upstream-training-japan-spotlight/</guid><description>&lt;p>We are organizers of &lt;a href="https://github.com/kubernetes-sigs/contributor-playground/tree/master/japan"
 
 target="_blank" rel="noopener">Kubernetes Upstream Training in Japan&lt;/a>
.
Our team is composed of members who actively contribute to Kubernetes, including individuals who hold roles such as member, reviewer, approver, and chair.&lt;/p>
&lt;p>Our goal is to increase the number of Kubernetes contributors and foster the growth of the community.
While Kubernetes community is friendly and collaborative, newcomers may find the first step of contributing to be a bit challenging.
Our training program aims to lower that barrier and create an environment where even beginners can participate smoothly.&lt;/p></description></item><item><title>Announcing the 2024 Steering Committee Election Results</title><link>https://www.kubernetes.dev/blog/2024/10/02/steering-committee-results-2024/</link><pubDate>Wed, 02 Oct 2024 15:10:00 -0500</pubDate><guid>https://www.kubernetes.dev/blog/2024/10/02/steering-committee-results-2024/</guid><description>&lt;p>The &lt;a href="https://github.com/kubernetes/community/tree/main/elections/steering/2024"
 
 target="_blank" rel="noopener">2024 Steering Committee Election&lt;/a>
 is now complete. The Kubernetes Steering Committee consists of 7 seats, 3 of which were up for election in 2024. Incoming committee members serve a term of 2 years, and all members are elected by the Kubernetes Community.&lt;/p>
&lt;p>This community body is significant since it oversees the governance of the entire Kubernetes project. With that great power comes great responsibility. You can learn more about the steering committee’s role in their &lt;a href="https://github.com/kubernetes/steering/blob/main/charter.md"
 
 target="_blank" rel="noopener">charter&lt;/a>
.&lt;/p></description></item><item><title>Spotlight on CNCF Deaf and Hard-of-hearing Working Group (DHHWG)</title><link>https://www.kubernetes.dev/blog/2024/09/30/cncf-deaf-and-hard-of-hearing-working-group-spotlight/</link><pubDate>Mon, 30 Sep 2024 00:00:00 +0000</pubDate><guid>https://www.kubernetes.dev/blog/2024/09/30/cncf-deaf-and-hard-of-hearing-working-group-spotlight/</guid><description>&lt;p>&lt;em>In recognition of Deaf Awareness Month and the importance of inclusivity in the tech community, we are spotlighting &lt;a href="https://www.linkedin.com/in/catherinepaganini/"
 
 target="_blank" rel="noopener">Catherine Paganini&lt;/a>
, facilitator and one of the founding members of &lt;a href="https://contribute.cncf.io/about/deaf-and-hard-of-hearing/"
 
 target="_blank" rel="noopener">CNCF Deaf and Hard-of-Hearing Working Group&lt;/a>
 (DHHWG). In this interview, &lt;a href="https://www.linkedin.com/in/sandeepkanabar/"
 
 target="_blank" rel="noopener">Sandeep Kanabar&lt;/a>
, a deaf member of the DHHWG and part of the Kubernetes &lt;a href="https://github.com/kubernetes/community/blob/main/sig-contributor-experience/README.md#contributor-comms"
 
 target="_blank" rel="noopener">SIG ContribEx Communications team&lt;/a>
, sits down with Catherine to explore the impact of the DHHWG on cloud native projects like Kubernetes.&lt;/em>&lt;/p></description></item><item><title>Spotlight on SIG Scheduling</title><link>https://www.kubernetes.dev/blog/2024/09/24/sig-scheduling-spotlight-2024/</link><pubDate>Tue, 24 Sep 2024 00:00:00 +0000</pubDate><guid>https://www.kubernetes.dev/blog/2024/09/24/sig-scheduling-spotlight-2024/</guid><description>&lt;p>In this SIG Scheduling spotlight we talked with &lt;a href="https://github.com/sanposhiho/"
 
 target="_blank" rel="noopener">Kensei Nakada&lt;/a>
, an
approver in SIG Scheduling.&lt;/p>
&lt;h2 id="introductions">Introductions&lt;/h2>
&lt;p>&lt;strong>Arvind:&lt;/strong> &lt;strong>Hello, thank you for the opportunity to learn more about SIG Scheduling! Would you
like to introduce yourself and tell us a bit about your role, and how you got involved with
Kubernetes?&lt;/strong>&lt;/p>
&lt;p>&lt;strong>Kensei&lt;/strong>: Hi, thanks for the opportunity! I’m Kensei Nakada
(&lt;a href="https://github.com/sanposhiho/"
 
 target="_blank" rel="noopener">@sanposhiho&lt;/a>
), a software engineer at
&lt;a href="https://tetrate.io/"
 
 target="_blank" rel="noopener">Tetrate.io&lt;/a>
. I have been contributing to Kubernetes in my free time for more
than 3 years, and now I’m an approver of SIG Scheduling in Kubernetes. Also, I’m a founder/owner of
two SIG subprojects,
&lt;a href="https://github.com/kubernetes-sigs/kube-scheduler-simulator"
 
 target="_blank" rel="noopener">kube-scheduler-simulator&lt;/a>
 and
&lt;a href="https://github.com/kubernetes-sigs/kube-scheduler-wasm-extension"
 
 target="_blank" rel="noopener">kube-scheduler-wasm-extension&lt;/a>
.&lt;/p></description></item><item><title>Spotlight on SIG API Machinery</title><link>https://www.kubernetes.dev/blog/2024/08/07/sig-api-machinery-spotlight-2024/</link><pubDate>Wed, 07 Aug 2024 00:00:00 +0000</pubDate><guid>https://www.kubernetes.dev/blog/2024/08/07/sig-api-machinery-spotlight-2024/</guid><description>&lt;p>We recently talked with &lt;a href="https://github.com/fedebongio"
 
 target="_blank" rel="noopener">Federico Bongiovanni&lt;/a>
 (Google) and &lt;a href="https://github.com/deads2k"
 
 target="_blank" rel="noopener">David
Eads&lt;/a>
 (Red Hat), Chairs of SIG API Machinery, to know a bit more about
this Kubernetes Special Interest Group.&lt;/p>
&lt;h2 id="introductions">Introductions&lt;/h2>
&lt;p>&lt;strong>Frederico (FSM): Hello, and thank your for your time. To start with, could you tell us about
yourselves and how you got involved in Kubernetes?&lt;/strong>&lt;/p>
&lt;p>&lt;strong>David&lt;/strong>: I started working on
&lt;a href="https://www.redhat.com/en/technologies/cloud-computing/openshift"
 
 target="_blank" rel="noopener">OpenShift&lt;/a>
 (the Red Hat
distribution of Kubernetes) in the fall of 2014 and got involved pretty quickly in API Machinery. My
first PRs were fixing kube-apiserver error messages and from there I branched out to &lt;code>kubectl&lt;/code>
(&lt;em>kubeconfigs&lt;/em> are my fault!), &lt;code>auth&lt;/code> (&lt;a href="https://kubernetes.io/docs/reference/access-authn-authz/rbac/"
 
 target="_blank" rel="noopener">RBAC&lt;/a>
 and &lt;code>*Review&lt;/code> APIs are ports
from OpenShift), &lt;code>apps&lt;/code> (&lt;em>workqueues&lt;/em> and &lt;em>sharedinformers&lt;/em> for example). Don’t tell the others,
but API Machinery is still my favorite :)&lt;/p></description></item><item><title>Spotlight on SIG Node</title><link>https://www.kubernetes.dev/blog/2024/06/20/sig-node-spotlight-2024/</link><pubDate>Thu, 20 Jun 2024 00:00:00 +0000</pubDate><guid>https://www.kubernetes.dev/blog/2024/06/20/sig-node-spotlight-2024/</guid><description>&lt;p>In the world of container orchestration, &lt;a href="https://kubernetes.io/"
 
 target="_blank" rel="noopener">Kubernetes&lt;/a>
 reigns
supreme, powering some of the most complex and dynamic applications across the globe. Behind the
scenes, a network of Special Interest Groups (SIGs) drives Kubernetes&amp;rsquo; innovation and stability.&lt;/p>
&lt;p>Today, I have the privilege of speaking with
&lt;a href="https://www.linkedin.com/in/matthias-bertschy-b427b815/"
 
 target="_blank" rel="noopener">Matthias Bertschy&lt;/a>
,
&lt;a href="https://www.linkedin.com/in/gunju-kim-916b33190/"
 
 target="_blank" rel="noopener">Gunju Kim&lt;/a>
, and
&lt;a href="https://www.linkedin.com/in/sergeykanzhelev/"
 
 target="_blank" rel="noopener">Sergey Kanzhelev&lt;/a>
, members of
&lt;a href="https://github.com/kubernetes/community/blob/main/sig-node/README.md"
 
 target="_blank" rel="noopener">SIG Node&lt;/a>
,
who will shed some light on their roles, challenges, and the exciting developments within SIG Node.&lt;/p></description></item><item><title>Introducing Hydrophone</title><link>https://www.kubernetes.dev/blog/2024/05/23/introducing-hydrophone/</link><pubDate>Thu, 23 May 2024 00:00:00 +0000</pubDate><guid>https://www.kubernetes.dev/blog/2024/05/23/introducing-hydrophone/</guid><description>&lt;p>In the ever-changing landscape of Kubernetes, ensuring that clusters operate as intended is
essential. This is where conformance testing becomes crucial, verifying that a Kubernetes cluster
meets the required standards set by the community. Today, we&amp;rsquo;re thrilled to introduce
&lt;a href="https://github.com/kubernetes-sigs/hydrophone/"
 
 target="_blank" rel="noopener">&lt;em>Hydrophone&lt;/em>&lt;/a>
, a lightweight runner designed to
streamline Kubernetes tests using the official conformance images released by the Kubernetes release
team.&lt;/p>
&lt;h2 id="simplified-kubernetes-testing-with-hydrophone">Simplified Kubernetes testing with Hydrophone&lt;/h2>
&lt;p>Hydrophone&amp;rsquo;s design philosophy centers around ease of use. By starting the conformance image as a
pod within the &lt;em>conformance&lt;/em> namespace, Hydrophone waits for the tests to conclude, then prints and
exports the results. This approach offers a hassle-free method for running either individual tests
or the entire &lt;a href="https://github.com/kubernetes/community/blob/main/contributors/devel/sig-architecture/conformance-tests.md"
 
 target="_blank" rel="noopener">Conformance Test
Suite&lt;/a>
.&lt;/p></description></item><item><title>Spotlight on SIG Architecture: Code Organization</title><link>https://www.kubernetes.dev/blog/2024/04/11/sig-architecture-code-spotlight-2024/</link><pubDate>Thu, 11 Apr 2024 00:00:00 +0000</pubDate><guid>https://www.kubernetes.dev/blog/2024/04/11/sig-architecture-code-spotlight-2024/</guid><description>&lt;p>&lt;em>This is the third interview of a SIG Architecture Spotlight series that will cover the different
subprojects. We will cover &lt;a href="https://github.com/kubernetes/community/blob/e44c2c9d0d3023e7111d8b01ac93d54c8624ee91/sig-architecture/README.md#code-organization"
 
 target="_blank" rel="noopener">SIG Architecture: Code Organization&lt;/a>
.&lt;/em>&lt;/p>
&lt;p>In this SIG Architecture spotlight I talked with &lt;a href="https://github.com/MadhavJivrajani"
 
 target="_blank" rel="noopener">Madhav Jivrajani&lt;/a>

(VMware), a member of the Code Organization subproject.&lt;/p>
&lt;h2 id="introducing-the-code-organization-subproject">Introducing the Code Organization subproject&lt;/h2>
&lt;p>&lt;strong>Frederico (FSM)&lt;/strong>: Hello Madhav, thank you for your availability. Could you start by telling us a
bit about yourself, your role and how you got involved in Kubernetes?&lt;/p></description></item><item><title>Using Go workspaces in Kubernetes</title><link>https://www.kubernetes.dev/blog/2024/03/19/go-workspaces-in-kubernetes/</link><pubDate>Tue, 19 Mar 2024 08:30:00 -0800</pubDate><guid>https://www.kubernetes.dev/blog/2024/03/19/go-workspaces-in-kubernetes/</guid><description>&lt;p>The &lt;a href="https://go.dev/"
 
 target="_blank" rel="noopener">Go programming language&lt;/a>
 has played a huge role in the
success of Kubernetes. As Kubernetes has grown, matured, and pushed the bounds
of what &amp;ldquo;regular&amp;rdquo; projects do, the Go project team has also grown and evolved
the language and tools. In recent releases, Go introduced a feature called
&amp;ldquo;workspaces&amp;rdquo; which was aimed at making projects like Kubernetes easier to
manage.&lt;/p>
&lt;p>We&amp;rsquo;ve just completed a major effort to adopt workspaces in Kubernetes, and the
results are great. Our codebase is simpler and less error-prone, and we&amp;rsquo;re no
longer off on our own technology island.&lt;/p></description></item><item><title>Spotlight on SIG Cloud Provider</title><link>https://www.kubernetes.dev/blog/2024/03/01/sig-cloud-provider-spotlight-2024/</link><pubDate>Fri, 01 Mar 2024 00:00:00 +0000</pubDate><guid>https://www.kubernetes.dev/blog/2024/03/01/sig-cloud-provider-spotlight-2024/</guid><description>&lt;p>One of the most popular ways developers use Kubernetes-related services is via cloud providers, but
have you ever wondered how cloud providers can do that? How does this whole process of integration
of Kubernetes to various cloud providers happen? To answer that, let&amp;rsquo;s put the spotlight on &lt;a href="https://github.com/kubernetes/community/blob/main/sig-cloud-provider/README.md"
 
 target="_blank" rel="noopener">SIG
Cloud Provider&lt;/a>
.&lt;/p>
&lt;p>SIG Cloud Provider works to create seamless integrations between Kubernetes and various cloud
providers. Their mission? Keeping the Kubernetes ecosystem fair and open for all. By setting clear
standards and requirements, they ensure every cloud provider plays nicely with Kubernetes. It is
their responsibility to configure cluster components to enable cloud provider integrations.&lt;/p></description></item><item><title>A look into the Kubernetes Book Club</title><link>https://www.kubernetes.dev/blog/2024/02/22/k8s-book-club/</link><pubDate>Thu, 22 Feb 2024 00:00:00 +0000</pubDate><guid>https://www.kubernetes.dev/blog/2024/02/22/k8s-book-club/</guid><description>&lt;p>Learning Kubernetes and the entire ecosystem of technologies around it is not without its
challenges. In this interview, we will talk with &lt;a href="https://www.linkedin.com/in/csantanapr/"
 
 target="_blank" rel="noopener">Carlos Santana
(AWS)&lt;/a>
 to learn a bit more about how he created the
&lt;a href="https://community.cncf.io/kubernetes-virtual-book-club/"
 
 target="_blank" rel="noopener">Kubernetes Book Club&lt;/a>
, how it works, and
how anyone can join in to take advantage of a community-based learning experience.&lt;/p>
&lt;p>&lt;img src="https://www.kubernetes.dev/blog/2024/k8s-book-club/csantana_k8s_book_club.jpg" alt="Carlos Santana speaking at KubeCon NA 2023">&lt;/p>
&lt;p>&lt;strong>Frederico Muñoz (FSM)&lt;/strong>: Hello Carlos, thank you so much for your availability. To start with,
could you tell us a bit about yourself?&lt;/p></description></item><item><title>Spotlight on SIG Release (Release Team Subproject)</title><link>https://www.kubernetes.dev/blog/2024/01/15/sig-release-spotlight-2023/</link><pubDate>Mon, 15 Jan 2024 00:00:00 +0000</pubDate><guid>https://www.kubernetes.dev/blog/2024/01/15/sig-release-spotlight-2023/</guid><description>&lt;p>The Release Special Interest Group (SIG Release), where Kubernetes sharpens its blade
with cutting-edge features and bug fixes every 4 months. Have you ever considered how such a big
project like Kubernetes manages its timeline so efficiently to release its new version, or how
the internal workings of the Release Team look like? If you&amp;rsquo;re curious about these questions or
want to know more and get involved with the work SIG Release does, read on!&lt;/p></description></item><item><title>Blixt - A load-balancer written in Rust, using eBPF, born from Gateway API</title><link>https://www.kubernetes.dev/blog/2024/01/08/blixt-load-balancer-rust-ebpf-gateway-api/</link><pubDate>Mon, 08 Jan 2024 00:00:00 +0000</pubDate><guid>https://www.kubernetes.dev/blog/2024/01/08/blixt-load-balancer-rust-ebpf-gateway-api/</guid><description>&lt;p>In &lt;a href="https://github.com/kubernetes/community/tree/main/sig-network"
 
 target="_blank" rel="noopener">SIG Network&lt;/a>
 we now have a layer 4 (“L4”) load balancer named &lt;a href="https://github.com/kubernetes-sigs/blixt"
 
 target="_blank" rel="noopener">Blixt&lt;/a>
. This
project started as a fun experiment using emerging technologies and is intended
to become a utility for CI and testing to help facilitate the continued
development of &lt;a href="https://kubernetes.io/docs/concepts/services-networking/gateway/"
 
 target="_blank" rel="noopener">Gateway API&lt;/a>
. Are you interested in developing networking
tools in &lt;a href="https://www.rust-lang.org/"
 
 target="_blank" rel="noopener">Rust&lt;/a>
 and &lt;a href="https://www.kernel.org/doc/html/latest/bpf/index.html"
 
 target="_blank" rel="noopener">eBPF&lt;/a>
? Or perhaps you&amp;rsquo;re specifically
interested in Gateway API? We&amp;rsquo;ll tell you a bit about the project and how it
might benefit you.&lt;/p></description></item><item><title>Kubernetes supports running kube-proxy in an unprivileged container</title><link>https://www.kubernetes.dev/blog/2024/01/05/kube-proxy-non-privileged/</link><pubDate>Fri, 05 Jan 2024 00:00:00 +0000</pubDate><guid>https://www.kubernetes.dev/blog/2024/01/05/kube-proxy-non-privileged/</guid><description>&lt;p>This post describes how the &lt;code>--init-only&lt;/code> flag to &lt;code>kube-proxy&lt;/code> can be
used to run the main kube-proxy container in a stricter
&lt;code>securityContext&lt;/code>, by performing the configuration that requires
privileged mode in a separate &lt;a href="https://kubernetes.io/docs/concepts/workloads/pods/init-containers/"
 
 target="_blank" rel="noopener">init container&lt;/a>
.
Since
Windows doesn&amp;rsquo;t have the equivalent of &lt;code>capabilities&lt;/code>, this only works
on Linux.&lt;/p>
&lt;p>The &lt;code>kube-proxy&lt;/code> Pod still only meets the &lt;em>privileged&lt;/em> &lt;a href="https://kubernetes.io/docs/concepts/security/pod-security-standards/"
 
 target="_blank" rel="noopener">Pod Security
Standard&lt;/a>
,
but there is still an improvement because the running container doesn&amp;rsquo;t
need to run privileged.&lt;/p></description></item><item><title>Contextual logging in Kubernetes 1.29: Better troubleshooting and enhanced logging</title><link>https://www.kubernetes.dev/blog/2023/12/20/contextual-logging/</link><pubDate>Wed, 20 Dec 2023 09:30:00 -0800</pubDate><guid>https://www.kubernetes.dev/blog/2023/12/20/contextual-logging/</guid><description>&lt;p>On behalf of the &lt;a href="https://github.com/kubernetes/community/blob/main/archive/wg-structured-logging/README.md"
 
 target="_blank" rel="noopener">Structured Logging Working Group&lt;/a>

and &lt;a href="https://github.com/kubernetes/community/tree/main/sig-instrumentation#readme"
 
 target="_blank" rel="noopener">SIG Instrumentation&lt;/a>
,
we are pleased to announce that the contextual logging feature
introduced in Kubernetes v1.24 has now been successfully migrated to
two components (kube-scheduler and kube-controller-manager)
as well as some directories. This feature aims to provide more useful logs
for better troubleshooting of Kubernetes and to empower developers to enhance Kubernetes.&lt;/p>
&lt;h2 id="what-is-contextual-logging">What is contextual logging?&lt;/h2>
&lt;p>&lt;a href="https://github.com/kubernetes/enhancements/tree/master/keps/sig-instrumentation/3077-contextual-logging"
 
 target="_blank" rel="noopener">Contextual logging&lt;/a>

is based on the &lt;a href="https://github.com/go-logr/logr#a-minimal-logging-api-for-go"
 
 target="_blank" rel="noopener">go-logr&lt;/a>
 API.
The key idea is that libraries are passed a logger instance by their caller
and use that for logging instead of accessing a global logger.
The binary decides the logging implementation, not the libraries.
The go-logr API is designed around structured logging and supports attaching
additional information to a logger.&lt;/p></description></item><item><title>Spotlight on SIG Testing</title><link>https://www.kubernetes.dev/blog/2023/11/24/sig-testing-spotlight-2023/</link><pubDate>Fri, 24 Nov 2023 00:00:00 +0000</pubDate><guid>https://www.kubernetes.dev/blog/2023/11/24/sig-testing-spotlight-2023/</guid><description>&lt;p>Welcome to another edition of the &lt;em>SIG spotlight&lt;/em> blog series, where we
highlight the incredible work being done by various Special Interest
Groups (SIGs) within the Kubernetes project. In this edition, we turn
our attention to &lt;a href="https://github.com/kubernetes/community/tree/main/sig-testing#readme"
 
 target="_blank" rel="noopener">SIG Testing&lt;/a>
,
a group interested in effective testing of Kubernetes and automating
away project toil. SIG Testing focus on creating and running tools and
infrastructure that make it easier for the community to write and run
tests, and to contribute, analyze and act upon test results.&lt;/p></description></item><item><title>Kubernetes Contributor Summit: Behind-the-scenes</title><link>https://www.kubernetes.dev/blog/2023/11/03/k8s-contributor-summit-behind-the-scenes/</link><pubDate>Fri, 03 Nov 2023 00:00:00 +0000</pubDate><guid>https://www.kubernetes.dev/blog/2023/11/03/k8s-contributor-summit-behind-the-scenes/</guid><description>&lt;p>Every year, just before the official start of KubeCon+CloudNativeCon, there&amp;rsquo;s a special event that
has a very special place in the hearts of those organizing and participating in it: the Kubernetes
Contributor Summit. To find out why, and to provide a behind-the-scenes perspective, we interview
Noah Abrahams, whom amongst other roles was the co-lead for the Kubernetes Contributor Summit in
2023.&lt;/p>
&lt;p>&lt;strong>Frederico Muñoz (FSM)&lt;/strong>: Hello Noah, and welcome. Could you start by introducing yourself and
telling us how you got involved in Kubernetes?&lt;/p></description></item><item><title>Spotlight on SIG Architecture: Production Readiness</title><link>https://www.kubernetes.dev/blog/2023/11/02/sig-architecture-production-readiness-spotlight-2023/</link><pubDate>Thu, 02 Nov 2023 00:00:00 +0000</pubDate><guid>https://www.kubernetes.dev/blog/2023/11/02/sig-architecture-production-readiness-spotlight-2023/</guid><description>&lt;p>&lt;em>This is the second interview of a SIG Architecture Spotlight series that will cover the different
subprojects. In this blog, we will cover the &lt;a href="https://github.com/kubernetes/community/blob/main/sig-architecture/README.md#production-readiness-1"
 
 target="_blank" rel="noopener">SIG Architecture: Production Readiness
subproject&lt;/a>
&lt;/em>.&lt;/p>
&lt;p>In this SIG Architecture spotlight, we talked with &lt;a href="https://github.com/wojtek-t"
 
 target="_blank" rel="noopener">Wojciech Tyczynski&lt;/a>

(Google), lead of the Production Readiness subproject.&lt;/p>
&lt;h2 id="about-sig-architecture-and-the-production-readiness-subproject">About SIG Architecture and the Production Readiness subproject&lt;/h2>
&lt;p>&lt;strong>Frederico (FSM)&lt;/strong>: Hello Wojciech, could you tell us a bit about yourself, your role and how you
got involved in Kubernetes?&lt;/p></description></item><item><title>A Quick Recap of 2023 China Kubernetes Contributor Summit</title><link>https://www.kubernetes.dev/blog/2023/10/20/kcs-shanghai/</link><pubDate>Fri, 20 Oct 2023 00:00:00 +0000</pubDate><guid>https://www.kubernetes.dev/blog/2023/10/20/kcs-shanghai/</guid><description>&lt;p>On September 26, 2023, the first day of
&lt;a href="https://www.lfasiallc.com/kubecon-cloudnativecon-open-source-summit-china/"
 
 target="_blank" rel="noopener">KubeCon + CloudNativeCon + Open Source Summit China 2023&lt;/a>
,
nearly 50 contributors gathered in Shanghai for the Kubernetes Contributor Summit.&lt;/p>

&lt;figure>
 &lt;img src="https://www.kubernetes.dev/blog/2023/10/20/kcs-shanghai/kcs04.jpeg"
 alt="Kubernetes contributors posing for a group photo"/> &lt;figcaption>
 &lt;p>All participants in the 2023 Kubernetes Contributor Summit&lt;/p>
 &lt;/figcaption>
&lt;/figure>

&lt;p>This marked the first in-person offline gathering held in China after three years of the pandemic.&lt;/p>
&lt;h2 id="a-joyful-meetup">A joyful meetup&lt;/h2>
&lt;p>The event began with welcome speeches from &lt;a href="https://github.com/kevin-wangzefeng"
 
 target="_blank" rel="noopener">Kevin Wang&lt;/a>
 from Huawei Cloud,
one of the co-chairs of KubeCon, and &lt;a href="https://github.com/puja108"
 
 target="_blank" rel="noopener">Puja&lt;/a>
 from Giant Swarm.&lt;/p></description></item><item><title>Spotlight on SIG Architecture: Conformance</title><link>https://www.kubernetes.dev/blog/2023/10/05/sig-architecture-conformance-spotlight-2023/</link><pubDate>Thu, 05 Oct 2023 00:00:00 +0000</pubDate><guid>https://www.kubernetes.dev/blog/2023/10/05/sig-architecture-conformance-spotlight-2023/</guid><description>&lt;p>&lt;em>This is the first interview of a SIG Architecture Spotlight series
that will cover the different subprojects. We start with the SIG
Architecture: Conformance subproject&lt;/em>&lt;/p>
&lt;p>In this &lt;a href="https://github.com/kubernetes/community/blob/main/sig-architecture/README.md"
 
 target="_blank" rel="noopener">SIG
Architecture&lt;/a>

spotlight, we talked with &lt;a href="https://github.com/Riaankl"
 
 target="_blank" rel="noopener">Riaan
Kleinhans&lt;/a>
 (ii-Team), Lead for the
&lt;a href="https://github.com/kubernetes/community/blob/main/sig-architecture/README.md#conformance-definition-1"
 
 target="_blank" rel="noopener">Conformance
sub-project&lt;/a>
.&lt;/p>
&lt;h2 id="about-sig-architecture-and-the-conformance-subproject">About SIG Architecture and the Conformance subproject&lt;/h2>
&lt;p>&lt;strong>Frederico (FSM)&lt;/strong>: Hello Riaan, and welcome! For starters, tell us a
bit about yourself, your role and how you got involved in Kubernetes.&lt;/p>
&lt;p>&lt;strong>Riaan Kleinhans (RK)&lt;/strong>: Hi! My name is Riaan Kleinhans and I live in
South Africa. I am the Project manager for the &lt;a href="ii.nz"
 
 >ii-Team&lt;/a>
 in New
Zealand. When I joined ii the plan was to move to New Zealand in April
2020 and then Covid happened. Fortunately, being a flexible and
dynamic team we were able to make it work remotely and in very
different time zones.&lt;/p></description></item><item><title>Announcing the 2023 Steering Committee Election Results</title><link>https://www.kubernetes.dev/blog/2023/10/02/steering-committee-results-2023/</link><pubDate>Mon, 02 Oct 2023 00:00:00 +0000</pubDate><guid>https://www.kubernetes.dev/blog/2023/10/02/steering-committee-results-2023/</guid><description>&lt;p>The &lt;a href="https://github.com/kubernetes/community/tree/main/elections/steering/2023"
 
 target="_blank" rel="noopener">2023 Steering Committee Election&lt;/a>
 is now complete. The Kubernetes Steering Committee consists of 7 seats, 4 of which were up for election in 2023. Incoming committee members serve a term of 2 years, and all members are elected by the Kubernetes Community.&lt;/p>
&lt;p>This community body is significant since it oversees the governance of the entire Kubernetes project. With that great power comes great responsibility. You can learn more about the steering committee’s role in their &lt;a href="https://github.com/kubernetes/steering/blob/main/charter.md"
 
 target="_blank" rel="noopener">charter&lt;/a>
.&lt;/p></description></item><item><title>Spotlight on SIG ContribEx</title><link>https://www.kubernetes.dev/blog/2023/08/14/sig-contribex-spotlight-2023/</link><pubDate>Mon, 14 Aug 2023 00:00:00 +0000</pubDate><guid>https://www.kubernetes.dev/blog/2023/08/14/sig-contribex-spotlight-2023/</guid><description>&lt;p>&lt;strong>Author&lt;/strong>: Fyka Ansari&lt;/p>
&lt;p>Welcome to the world of Kubernetes and its vibrant contributor
community! In this blog post, we&amp;rsquo;ll be shining a spotlight on the
&lt;a href="https://github.com/kubernetes/community/blob/main/sig-contributor-experience/README.md"
 
 target="_blank" rel="noopener">Special Interest Group for Contributor
Experience&lt;/a>

(SIG ContribEx), an essential component of the Kubernetes project.&lt;/p>
&lt;p>SIG ContribEx in Kubernetes is responsible for developing and
maintaining a healthy and productive community of contributors to the
project. This involves identifying and addressing bottlenecks that may
hinder the project&amp;rsquo;s growth and feature velocity, such as pull request
latency and the number of open pull requests and issues.&lt;/p></description></item><item><title>Spotlight on SIG CLI</title><link>https://www.kubernetes.dev/blog/2023/07/20/sig-cli-spotlight-2023/</link><pubDate>Thu, 20 Jul 2023 00:00:00 +0000</pubDate><guid>https://www.kubernetes.dev/blog/2023/07/20/sig-cli-spotlight-2023/</guid><description>&lt;p>In the world of Kubernetes, managing containerized applications at
scale requires powerful and efficient tools. The command-line
interface (CLI) is an integral part of any developer or operator’s
toolkit, offering a convenient and flexible way to interact with a
Kubernetes cluster.&lt;/p>
&lt;p>SIG CLI plays a crucial role in improving the &lt;a href="https://github.com/kubernetes/community/tree/main/sig-cli"
 
 target="_blank" rel="noopener">Kubernetes
CLI&lt;/a>

experience by focusing on the development and enhancement of
&lt;code>kubectl&lt;/code>, the primary command-line tool for Kubernetes.&lt;/p>
&lt;p>In this SIG CLI Spotlight, Arpit Agrawal, SIG ContribEx-Comms team
member, talked with &lt;a href="https://github.com/KnVerey"
 
 target="_blank" rel="noopener">Katrina Verey&lt;/a>
, Tech
Lead &amp;amp; Chair of SIG CLI,and &lt;a href="https://github.com/soltysh"
 
 target="_blank" rel="noopener">Maciej
Szulik&lt;/a>
, SIG CLI Batch Lead, about SIG
CLI, current projects, challenges and how anyone can get involved.&lt;/p></description></item><item><title>Spotlight on SIG Network</title><link>https://www.kubernetes.dev/blog/2023/05/09/sig-network-spotlight-2023/</link><pubDate>Tue, 09 May 2023 00:00:00 +0000</pubDate><guid>https://www.kubernetes.dev/blog/2023/05/09/sig-network-spotlight-2023/</guid><description>&lt;p>Networking is one of the core pillars of Kubernetes, and the Special Interest
Group for Networking (SIG Network) is responsible for developing and maintaining
the networking features of Kubernetes. It covers all aspects to ensure
Kubernetes provides a reliable and scalable network infrastructure for
containerized applications.&lt;/p>
&lt;p>In this SIG Network spotlight, &lt;a href="https://twitter.com/Sujaystwt"
 
 target="_blank" rel="noopener">Sujay Dey&lt;/a>
 talked
with &lt;a href="https://twitter.com/ShaneUtt"
 
 target="_blank" rel="noopener">Shane Utt&lt;/a>
, Software Engineer at Kong, chair
of SIG Network and maintainer of Gateway API, on different aspects of the SIG,
what are the exciting things going on and how anyone can get involved and
contribute here.&lt;/p></description></item><item><title>E2E Testing Best Practices, Reloaded</title><link>https://www.kubernetes.dev/blog/2023/04/12/e2e-testing-best-practices-reloaded/</link><pubDate>Wed, 12 Apr 2023 00:00:00 +0000</pubDate><guid>https://www.kubernetes.dev/blog/2023/04/12/e2e-testing-best-practices-reloaded/</guid><description>&lt;p>End-to-end (E2E) testing in Kubernetes is how the project validates
functionality with real clusters. Contributors sooner or later encounter it
when asked to write E2E tests for new features or to help with debugging test
failures. Cluster admins or vendors might run the conformance tests, a subset
of all tests in the &lt;a href="https://github.com/kubernetes/kubernetes/tree/v1.27.0-rc.0/test/e2e"
 
 target="_blank" rel="noopener">E2E test
suite&lt;/a>
.&lt;/p>
&lt;p>The underlying &lt;a href="https://github.com/kubernetes/kubernetes/tree/v1.27.0-rc.0/test/e2e/framework"
 
 target="_blank" rel="noopener">E2E
framework&lt;/a>

for writing these E2E tests has been around for a long
time. Functionality was added to it as needed, leading to code that became hard
to maintain and use. The &lt;a href="https://github.com/kubernetes/community/blob/main/sig-testing/README.md#testing-commons"
 
 target="_blank" rel="noopener">testing commons
WG&lt;/a>

started cleaning it up, but dissolved before completely achieving their
goals.&lt;/p></description></item><item><title>From Zero to Kubernets Subproject Lead</title><link>https://www.kubernetes.dev/blog/2023/03/29/from-zero-to-k8s-subproject-lead/</link><pubDate>Wed, 29 Mar 2023 00:00:00 +0000</pubDate><guid>https://www.kubernetes.dev/blog/2023/03/29/from-zero-to-k8s-subproject-lead/</guid><description>&lt;p>Getting started in any open-source community can be daunting, especially if it’s a big one like
Kubernetes. I wrote this post to share my experience and encourage others to join up. All
it takes is some curiosity and a willingness to show up!&lt;/p>
&lt;p>Here’s how my journey unfolded at a high level:&lt;/p>
&lt;ol>
&lt;li>What am I interested in? Is there a SIG (Special Interest Group) or a WG (Working Group) that is
dedicated to that topic, or something similar? &lt;/li>
&lt;li>Sign up for their mailing list and start hopping on meetings.&lt;/li>
&lt;li>When (never if!) there are opportunities to help out and it aligns with your skills and desired
growth areas, raise your hand.&lt;/li>
&lt;li>Ask for lots of help and don’t be shy about not knowing everything (or anything!)&lt;/li>
&lt;li>Keep plugging along, even if progress isn’t as fast as you would like it to be.&lt;/li>
&lt;/ol>
&lt;h2 id="starting-up">Starting up&lt;/h2>
&lt;p>First things first. What are you interested in learning more about? There are so many wonderful SIGs
and working groups in the Kubernetes community: there’s something for everyone. And continuing to
show up and participate will be so much easier if you think what you are doing is
interesting. Likewise, continued participation is what keeps the community thriving, so that
interest will drive you to have more of an impact. &lt;/p></description></item><item><title>Introducing KWOK: Kubernetes WithOut Kubelet</title><link>https://www.kubernetes.dev/blog/2023/03/01/introducing-kwok/</link><pubDate>Wed, 01 Mar 2023 00:00:00 +0000</pubDate><guid>https://www.kubernetes.dev/blog/2023/03/01/introducing-kwok/</guid><description>&lt;p>&lt;strong>Author:&lt;/strong> Shiming Zhang (DaoCloud), Wei Huang (Apple), Yibo Zhuang (Apple)&lt;/p>
&lt;img style="float: right; display: inline-block; margin-left: 2em; max-width: 15em;" src="https://www.kubernetes.dev/blog/2023/03/01/introducing-kwok/kwok.svg" alt="KWOK logo" />
&lt;p>Have you ever wondered how to set up a cluster of thousands of nodes just in seconds, how to simulate real nodes with a low resource footprint, and how to test your Kubernetes controller at scale without spending much on infrastructure?&lt;/p>
&lt;p>If you answered &amp;ldquo;yes&amp;rdquo; to any of these questions, then you might be interested in KWOK, a toolkit that enables you to create a cluster of thousands of nodes in seconds.&lt;/p></description></item><item><title>Spotlight on SIG Instrumentation</title><link>https://www.kubernetes.dev/blog/2023/02/03/sig-instrumentation-spotlight-2023/</link><pubDate>Fri, 03 Feb 2023 00:00:00 +0000</pubDate><guid>https://www.kubernetes.dev/blog/2023/02/03/sig-instrumentation-spotlight-2023/</guid><description>&lt;p>Observability requires the right data at the right time for the right consumer (human or piece of software) to make the right decision. In the context of Kubernetes, having best practices for cluster observability across all Kubernetes components is crucial.&lt;/p>
&lt;p>SIG Instrumentation helps to address this issue by providing best practices and tools that all other SIGs use to instrument Kubernetes components-like the &lt;em>API server&lt;/em>, &lt;em>scheduler&lt;/em>, &lt;em>kubelet&lt;/em> and &lt;em>kube-controller-manager&lt;/em>.&lt;/p>
&lt;p>In this SIG Instrumentation spotlight, &lt;a href="https://www.linkedin.com/in/imrannoormohamed/"
 
 target="_blank" rel="noopener">Imran Noor Mohamed&lt;/a>
, SIG ContribEx-Comms tech lead talked with &lt;a href="https://twitter.com/ehashdn"
 
 target="_blank" rel="noopener">Elana Hashman&lt;/a>
, and &lt;a href="https://www.linkedin.com/in/hankang"
 
 target="_blank" rel="noopener">Han Kang&lt;/a>
, chairs of SIG Instrumentation, on how the SIG is organized, what are the current challenges and how anyone can get involved and contribute.&lt;/p></description></item><item><title>Prow and Tide for Kubernetes Contributors</title><link>https://www.kubernetes.dev/blog/2022/12/12/prow-and-tide-for-kubernetes-contributors/</link><pubDate>Mon, 12 Dec 2022 00:00:00 +0000</pubDate><guid>https://www.kubernetes.dev/blog/2022/12/12/prow-and-tide-for-kubernetes-contributors/</guid><description>&lt;p>&lt;strong>Authors:&lt;/strong> &lt;a href="https://github.com/chris-short"
 
 target="_blank" rel="noopener">Chris Short&lt;/a>
, &lt;a href="https://github.com/fsmunoz"
 
 target="_blank" rel="noopener">Frederico Muñoz&lt;/a>
&lt;/p>
&lt;hr>
&lt;p>In my work in the Kubernetes world, I look up a label or Prow command often. The systems behind the scenes
(&lt;a href="https://prow.kubernetes.io/"
 
 target="_blank" rel="noopener">Prow&lt;/a>
 and
&lt;a href="https://pkg.go.dev/k8s.io/test-infra/prow/cmd/tide#section-readme"
 
 target="_blank" rel="noopener">Tide&lt;/a>
) are here to help Kubernetes
Contributors get stuff done.&lt;/p>
&lt;p>Labeling which SIG, WG, or subproject is as important as the issue or PR having someone assigned. To quote
&lt;a href="https://docs.prow.k8s.io/docs/components/core/tide/"
 
 target="_blank" rel="noopener">the docs&lt;/a>
, &amp;ldquo;Tide is a
&lt;a href="https://docs.prow.k8s.io/docs/"
 
 target="_blank" rel="noopener">Prow&lt;/a>
 component for managing a pool of GitHub PRs that match a given set of
criteria. It will automatically retest PRs that meet the criteria (&amp;rsquo;tide comes in&amp;rsquo;) and automatically merge
them when they have up-to-date passing test results (&amp;rsquo;tide goes out&amp;rsquo;).&amp;rdquo;&lt;/p></description></item><item><title>Implementing the Auto-refreshing Official Kubernetes CVE Feed</title><link>https://www.kubernetes.dev/blog/2022/09/12/k8s-cve-feed-alpha/</link><pubDate>Mon, 12 Sep 2022 00:00:00 +0000</pubDate><guid>https://www.kubernetes.dev/blog/2022/09/12/k8s-cve-feed-alpha/</guid><description>&lt;p>&lt;strong>Author&lt;/strong>: Pushkar Joglekar (VMware)&lt;/p>
&lt;p>Accompanying the release of Kubernetes v1.25, we announced
&lt;a href="https://kubernetes.io/blog/2022/09/12/k8s-cve-feed-alpha/"
 
 target="_blank" rel="noopener">availability of an official CVE feed&lt;/a>

as an &lt;code>alpha&lt;/code> feature. This blog will cover how we implemented this feature.&lt;/p>
&lt;h2 id="implementation-details">Implementation Details&lt;/h2>
&lt;p>An &lt;a href="https://kubernetes.io/docs/reference/issues-security/official-cve-feed/"
 
 target="_blank" rel="noopener">auto-refreshing CVE feed&lt;/a>

allows users and implementers to programmatically fetch the list of CVEs
announced by the Kubernetes SRC (Security Response Committee).&lt;/p>
&lt;p>To ensure freshness and minimal maintainer overhead, the feed updates
automatically by fetching the CVE related information from the CVE announcement
GitHub Issues. Creating these issues is already part of the existing Security
Response Committee (SRC) workflow.&lt;/p></description></item><item><title>Enhancements Opt-in Process Change for v1.26</title><link>https://www.kubernetes.dev/blog/2022/09/09/enhancements-opt-in/</link><pubDate>Fri, 09 Sep 2022 00:00:00 +0000</pubDate><guid>https://www.kubernetes.dev/blog/2022/09/09/enhancements-opt-in/</guid><description>&lt;p>&lt;strong>Author:&lt;/strong> Grace Nguyen&lt;/p>
&lt;h2 id="context-and-motivations">Context and Motivations&lt;/h2>
&lt;p>Since the inception of the Kubernetes release team, we have used a spreadsheet to keep track of enhancements for the release. The project has scaled massively in the past few years, with almost a hundred enhancements collected for the 1.24 release. This process has become error-prone and time consuming. A lot of manual work is required from the release team and the SIG leads to populate KEPs data in the sheet. We have received continuous feedback from our contributors to streamline the process.&lt;/p></description></item><item><title>Spotlight on SIG Storage</title><link>https://www.kubernetes.dev/blog/2022/08/22/sig-storage-spotlight-2022/</link><pubDate>Mon, 22 Aug 2022 00:00:00 +0000</pubDate><guid>https://www.kubernetes.dev/blog/2022/08/22/sig-storage-spotlight-2022/</guid><description>&lt;p>Since the very beginning of Kubernetes, the topic of persistent data and how to address the requirement of stateful applications has been an important topic. Support for stateless deployments was natural, present from the start, and garnered attention, becoming very well-known. Work on better support for stateful applications was also present from early on, with each release increasing the scope of what could be run on Kubernetes.&lt;/p>
&lt;p>Message queues, databases, clustered filesystems: these are some examples of the solutions that have different storage requirements and that are, today, increasingly deployed in Kubernetes. Dealing with ephemeral and persistent storage, local or remote, file or block, from many different vendors, while considering how to provide the needed resiliency and data consistency that users expect, all of this is under SIG Storage&amp;rsquo;s umbrella.&lt;/p></description></item><item><title>Meet Our Contributors - APAC (China region)</title><link>https://www.kubernetes.dev/blog/2022/08/15/meet-our-contributors-china-ep-03/</link><pubDate>Mon, 15 Aug 2022 00:00:00 +0000</pubDate><guid>https://www.kubernetes.dev/blog/2022/08/15/meet-our-contributors-china-ep-03/</guid><description>&lt;p>&lt;strong>Authors &amp;amp; Interviewers:&lt;/strong> &lt;a href="https://github.com/AvineshTripathi"
 
 target="_blank" rel="noopener">Avinesh Tripathi&lt;/a>
, &lt;a href="https://github.com/Debanitrkl"
 
 target="_blank" rel="noopener">Debabrata Panigrahi&lt;/a>
, &lt;a href="https://github.com/jayesh-srivastava"
 
 target="_blank" rel="noopener">Jayesh Srivastava&lt;/a>
, &lt;a href="https://github.com/Priyankasaggu11929/"
 
 target="_blank" rel="noopener">Priyanka Saggu&lt;/a>
, &lt;a href="https://github.com/PurneswarPrasad"
 
 target="_blank" rel="noopener">Purneswar Prasad&lt;/a>
, &lt;a href="https://github.com/vedant-kakde"
 
 target="_blank" rel="noopener">Vedant Kakde&lt;/a>
&lt;/p>
&lt;hr>
&lt;p>Hello, everyone 👋&lt;/p>
&lt;p>Welcome back to the third edition of the &amp;ldquo;Meet Our Contributors&amp;rdquo; blog post series for APAC.&lt;/p>
&lt;p>This post features four outstanding contributors from China, who have played diverse leadership and community roles in the upstream Kubernetes project.&lt;/p>
&lt;p>So, without further ado, let&amp;rsquo;s get straight to the article.&lt;/p>
&lt;h2 id="andy-zhang">&lt;a href="https://github.com/andyzhangx"
 
 target="_blank" rel="noopener">Andy Zhang&lt;/a>
&lt;/h2>
&lt;p>Andy Zhang currently works for Microsoft China at the Shanghai site. His main focus is on Kubernetes storage drivers. Andy started contributing to Kubernetes about 5 years ago.&lt;/p></description></item><item><title>Enhancing Kubernetes one KEP at a Time</title><link>https://www.kubernetes.dev/blog/2022/08/11/enhancing-kubernetes-one-kep-at-a-time/</link><pubDate>Thu, 11 Aug 2022 00:00:00 +0000</pubDate><guid>https://www.kubernetes.dev/blog/2022/08/11/enhancing-kubernetes-one-kep-at-a-time/</guid><description>&lt;p>&lt;strong>Author:&lt;/strong> Ryler Hockenbury (Mastercard)&lt;/p>
&lt;p>Did you know that Kubernetes v1.24 has &lt;a href="https://kubernetes.io/blog/2022/05/03/kubernetes-1-24-release-announcement/"
 
 target="_blank" rel="noopener">46 enhancements&lt;/a>
? That&amp;rsquo;s a lot of new functionality packed into a 4-month release cycle. The Kubernetes release team coordinates the logistics of the release, from remediating test flakes to publishing updated docs. It&amp;rsquo;s a ton of work, but they always deliver.&lt;/p>
&lt;p>The release team comprises around 30 people across six subteams - Bug Triage, CI Signal, Enhancements, Release Notes, Communications, and Docs.  Each of these subteams manages a component of the release. This post will focus on the role of the enhancements subteam and how you can get involved.&lt;/p></description></item><item><title>Spotlight on SIG Docs</title><link>https://www.kubernetes.dev/blog/2022/08/02/sig-docs-spotlight-2022/</link><pubDate>Tue, 02 Aug 2022 00:00:00 +0000</pubDate><guid>https://www.kubernetes.dev/blog/2022/08/02/sig-docs-spotlight-2022/</guid><description>&lt;p>&lt;strong>Author:&lt;/strong> Purneswar Prasad&lt;/p>
&lt;h2 id="introduction">Introduction&lt;/h2>
&lt;p>The official documentation is the go-to source for any open source project. For Kubernetes,
it&amp;rsquo;s an ever-evolving Special Interest Group (SIG) with people constantly putting in their efforts
to make details about the project easier to consume for new contributors and users. SIG Docs publishes
the official documentation on &lt;a href="https://kubernetes.io"
 
 target="_blank" rel="noopener">kubernetes.io&lt;/a>
 which includes,
but is not limited to, documentation of the core APIs, core architectural details, and CLI tools
shipped with the Kubernetes release.&lt;/p></description></item><item><title>Contextual Logging in Kubernetes 1.24</title><link>https://www.kubernetes.dev/blog/2022/05/25/contextual-logging/</link><pubDate>Wed, 25 May 2022 00:00:00 +0000</pubDate><guid>https://www.kubernetes.dev/blog/2022/05/25/contextual-logging/</guid><description>&lt;p>&lt;strong>Authors:&lt;/strong> Patrick Ohly (Intel)&lt;/p>
&lt;p>The &lt;a href="https://github.com/kubernetes/community/blob/main/archive/wg-structured-logging/README.md"
 
 target="_blank" rel="noopener">Structured Logging Working
Group&lt;/a>

has added new capabilities to the logging infrastructure in Kubernetes
1.24. This blog post explains how developers can take advantage of those to
make log output more useful and how they can get involved with improving Kubernetes.&lt;/p>
&lt;h2 id="structured-logging">Structured logging&lt;/h2>
&lt;p>The goal of &lt;a href="https://github.com/kubernetes/enhancements/blob/master/keps/sig-instrumentation/1602-structured-logging/README.md"
 
 target="_blank" rel="noopener">structured
logging&lt;/a>

is to replace C-style formatting and the resulting opaque log strings with log
entries that have a well-defined syntax for storing message and parameters
separately, for example as a JSON struct.&lt;/p></description></item><item><title>February 2022 Community Meeting Highlights</title><link>https://www.kubernetes.dev/blog/2022/05/05/community-meeting-februrary-2022/</link><pubDate>Thu, 05 May 2022 00:00:00 +0000</pubDate><guid>https://www.kubernetes.dev/blog/2022/05/05/community-meeting-februrary-2022/</guid><description>&lt;p>&lt;strong>Author:&lt;/strong> Nigel Brown (VMware)&lt;/p>
&lt;p>We just had our first contributor community meeting this year, and it was awesome to be back with you
in that format. These meetings will be happening on Zoom once per month, on the third Thursday of the
month - that should be available in your calendar if you’re subscribed to the k-dev mailing list.
Community meetings are an opportunity for you to meet synchronously with other members of the
Kubernetes community to talk about issues of general appeal.&lt;/p></description></item><item><title>K8s CI Bot Helper Job: automating "make update"</title><link>https://www.kubernetes.dev/blog/2022/03/15/k8s-triage-bot-helper-ci-job/</link><pubDate>Tue, 15 Mar 2022 00:00:00 +0000</pubDate><guid>https://www.kubernetes.dev/blog/2022/03/15/k8s-triage-bot-helper-ci-job/</guid><description>&lt;p>&lt;strong>Authors:&lt;/strong> &lt;a href="https://github.com/SubhasmitaSw"
 
 target="_blank" rel="noopener">Subhasmita Swain&lt;/a>
, &lt;a href="https://github.com/dims"
 
 target="_blank" rel="noopener">Davanum Srinivas&lt;/a>
&lt;/p>
&lt;hr>
&lt;p>If you are contributing to the Kubernetes project and are developing on a Windows PC, it is conceivable that you will encounter certain issues that will cause your pull request to get held up by test failures. This article describes a workaround for a similar issue I encountered when attempting to have my modifications approved and merged into the master branch.&lt;/p>
&lt;h2 id="why-is-this-needed">Why is this needed?&lt;/h2>
&lt;p>While contributing to &lt;a href="https://github.com/kubernetes/kubernetes"
 
 target="_blank" rel="noopener">kubernetes/kubernetes&lt;/a>
 for some minor documentation changes, the pushed changes needed to be updated with other verified contents of the entire documentation. So, in order for the change to take effect, a single command must be performed to ensure that all tests on the CI pipeline pass. The single command &lt;code>make update&lt;/code> runs all presubmission verification tests. For some reason on the &amp;ldquo;Windows Subsystem for Linux&amp;rdquo; environment the tests, specifically the &lt;a href="https://github.com/kubernetes/kubernetes/blob/master/hack/update-openapi-spec.sh"
 
 target="_blank" rel="noopener">update-openapi-spec.sh&lt;/a>
 script, failed (in my case, take a look at the conversation &lt;a href="https://github.com/kubernetes/kubernetes/pull/107691"
 
 target="_blank" rel="noopener">here&lt;/a>
), eventually failing the &lt;code>pull-kubernetes-verify&lt;/code> tests.&lt;/p></description></item><item><title>Meet Our Contributors - APAC (Aus-NZ region)</title><link>https://www.kubernetes.dev/blog/2022/03/14/meet-our-contributors-au-nz-ep-02/</link><pubDate>Mon, 14 Mar 2022 00:00:00 +0000</pubDate><guid>https://www.kubernetes.dev/blog/2022/03/14/meet-our-contributors-au-nz-ep-02/</guid><description>&lt;p>&lt;strong>Authors &amp;amp; Interviewers:&lt;/strong> &lt;a href="https://github.com/anubha-v-ardhan"
 
 target="_blank" rel="noopener">Anubhav Vardhan&lt;/a>
, &lt;a href="https://github.com/Atharva-Shinde"
 
 target="_blank" rel="noopener">Atharva Shinde&lt;/a>
, &lt;a href="https://github.com/AvineshTripathi"
 
 target="_blank" rel="noopener">Avinesh Tripathi&lt;/a>
, &lt;a href="https://github.com/bradmccoydev"
 
 target="_blank" rel="noopener">Brad McCoy&lt;/a>
, &lt;a href="https://github.com/Debanitrkl"
 
 target="_blank" rel="noopener">Debabrata Panigrahi&lt;/a>
, &lt;a href="https://github.com/jayesh-srivastava"
 
 target="_blank" rel="noopener">Jayesh Srivastava&lt;/a>
, &lt;a href="https://github.com/verma-kunal"
 
 target="_blank" rel="noopener">Kunal Verma&lt;/a>
, &lt;a href="https://github.com/PranshuSrivastava"
 
 target="_blank" rel="noopener">Pranshu Srivastava&lt;/a>
, &lt;a href="https://github.com/Priyankasaggu11929"
 
 target="_blank" rel="noopener">Priyanka Saggu&lt;/a>
, &lt;a href="https://github.com/PurneswarPrasad"
 
 target="_blank" rel="noopener">Purneswar Prasad&lt;/a>
, &lt;a href="https://github.com/vedant-kakde"
 
 target="_blank" rel="noopener">Vedant Kakde&lt;/a>
&lt;/p>
&lt;hr>
&lt;p>Good day, everyone 👋&lt;/p>
&lt;p>Welcome back to the second episode of the &amp;ldquo;Meet Our Contributors&amp;rdquo; blog post series for APAC.&lt;/p>
&lt;p>This post will feature four outstanding contributors from the Australia and New Zealand regions, who have played diverse leadership and community roles in the Upstream Kubernetes project.&lt;/p></description></item><item><title>SIG Node CI Subproject Celebrates Two Years of Test Improvements</title><link>https://www.kubernetes.dev/blog/2022/02/16/sig-node-ci-subproject-celebrates-two-years-of-test-improvements/</link><pubDate>Wed, 16 Feb 2022 00:00:00 +0000</pubDate><guid>https://www.kubernetes.dev/blog/2022/02/16/sig-node-ci-subproject-celebrates-two-years-of-test-improvements/</guid><description>&lt;p>&lt;strong>Authors:&lt;/strong> Sergey Kanzhelev (Google), Elana Hashman (Red Hat)&lt;/p>
&lt;p>Ensuring the reliability of SIG Node upstream code is a continuous effort
that takes a lot of behind-the-scenes effort from many contributors.
There are frequent releases of Kubernetes, base operating systems,
container runtimes, and test infrastructure that result in a complex matrix that
requires attention and steady investment to &amp;ldquo;keep the lights on.&amp;rdquo;
In May 2020, the Kubernetes node special interest group (&amp;ldquo;SIG Node&amp;rdquo;) organized a new
subproject for continuous integration (CI) for node-related code and tests. Since its
inauguration, the SIG Node CI subproject has run a weekly meeting, and even the full hour
is often not enough to complete triage of all bugs, test-related PRs and issues, and discuss all
related ongoing work within the subgroup.&lt;/p></description></item><item><title>Spotlight on SIG Multicluster</title><link>https://www.kubernetes.dev/blog/2022/02/04/sig-multicluster-spotlight-2022/</link><pubDate>Fri, 04 Feb 2022 00:00:00 +0000</pubDate><guid>https://www.kubernetes.dev/blog/2022/02/04/sig-multicluster-spotlight-2022/</guid><description>&lt;p>&lt;strong>Authors:&lt;/strong> Dewan Ahmed (Aiven) and Chris Short (AWS)&lt;/p>
&lt;h2 id="introduction">Introduction&lt;/h2>
&lt;p>&lt;a href="https://github.com/kubernetes/community/tree/main/sig-multicluster"
 
 target="_blank" rel="noopener">SIG Multicluster&lt;/a>
 is the Special Interest Group (SIG) focused on how Kubernetes concepts are expanded and used beyond the cluster boundary. Historically, Kubernetes resources only interacted within that boundary - KRU or Kubernetes Resource Universe (not an actual Kubernetes concept). Kubernetes clusters, even now, don&amp;rsquo;t really know anything about themselves or, about other clusters. Absence of cluster identifiers is a case in point. With the growing adoption of multicloud and multicluster deployments, the work SIG Multicluster doing is gaining a lot of attention.&lt;/p></description></item><item><title>Meet Our Contributors - APAC (India region)</title><link>https://www.kubernetes.dev/blog/2022/01/10/meet-our-contributors-india-ep-01/</link><pubDate>Mon, 10 Jan 2022 00:00:00 +0000</pubDate><guid>https://www.kubernetes.dev/blog/2022/01/10/meet-our-contributors-india-ep-01/</guid><description>&lt;p>&lt;strong>Authors &amp;amp; Interviewers:&lt;/strong> &lt;a href="https://github.com/anubha-v-ardhan"
 
 target="_blank" rel="noopener">Anubhav Vardhan&lt;/a>
, &lt;a href="https://github.com/Atharva-Shinde"
 
 target="_blank" rel="noopener">Atharva Shinde&lt;/a>
, &lt;a href="https://github.com/AvineshTripathi"
 
 target="_blank" rel="noopener">Avinesh Tripathi&lt;/a>
, &lt;a href="https://github.com/Debanitrkl"
 
 target="_blank" rel="noopener">Debabrata Panigrahi&lt;/a>
, &lt;a href="https://github.com/verma-kunal"
 
 target="_blank" rel="noopener">Kunal Verma&lt;/a>
, &lt;a href="https://github.com/PranshuSrivastava"
 
 target="_blank" rel="noopener">Pranshu Srivastava&lt;/a>
, &lt;a href="https://github.com/CIPHERTron"
 
 target="_blank" rel="noopener">Pritish Samal&lt;/a>
, &lt;a href="https://github.com/PurneswarPrasad"
 
 target="_blank" rel="noopener">Purneswar Prasad&lt;/a>
, &lt;a href="https://github.com/vedant-kakde"
 
 target="_blank" rel="noopener">Vedant Kakde&lt;/a>
&lt;/p>
&lt;p>&lt;strong>Editor:&lt;/strong> &lt;a href="https://psaggu.com"
 
 target="_blank" rel="noopener">Priyanka Saggu&lt;/a>
&lt;/p>
&lt;hr>
&lt;p>Good day, everyone 👋&lt;/p>
&lt;p>Welcome to the first episode of the APAC edition of the &amp;ldquo;Meet Our Contributors&amp;rdquo; blog post series.&lt;/p>
&lt;p>In this post, we&amp;rsquo;ll introduce you to five amazing folks from the India region who have been actively contributing to the upstream Kubernetes projects in a variety of ways, as well as being the leaders or maintainers of numerous community initiatives.&lt;/p></description></item><item><title>Announcing the Kubernetes Contributor Celebration 2021</title><link>https://www.kubernetes.dev/blog/2021/12/07/announcing-the-kubernetes-contributor-celebration-2021/</link><pubDate>Tue, 07 Dec 2021 00:00:00 +0000</pubDate><guid>https://www.kubernetes.dev/blog/2021/12/07/announcing-the-kubernetes-contributor-celebration-2021/</guid><description>&lt;h2 id="contributor-celebration-2021">Contributor Celebration 2021&lt;/h2>
&lt;p>It&amp;rsquo;s that time of the year again, Yayy!!&lt;/p>
&lt;p>Like last year, this year also we are back with Kubernetes Contributor Celebration, the annual end of the year celebration, to recognize our achievements and have some fun! It’s a time for us to relax, chat and do something fun with your fellow contributors!&lt;/p>
&lt;h2 id="registration">Registration&lt;/h2>
&lt;p>To register, please fill out the &lt;a href="https://docs.google.com/forms/d/e/1FAIpQLSdRIboKulEPf7jVgRH3iTVwS4PEk6k0htcOs1eSG2OBmkxEjg/viewform"
 
 target="_blank" rel="noopener">Registration Form&lt;/a>
.
More details on &lt;a href="https://www.kubernetes.dev/events/2021/kcc/how-to-join/"
 
 >how to join&lt;/a>
 the event.&lt;/p></description></item><item><title>Improve your documentation with Mermaid.js diagrams</title><link>https://www.kubernetes.dev/blog/2021/12/01/improve-your-documentation-with-mermaid.js-diagrams/</link><pubDate>Wed, 01 Dec 2021 00:00:00 +0000</pubDate><guid>https://www.kubernetes.dev/blog/2021/12/01/improve-your-documentation-with-mermaid.js-diagrams/</guid><description>&lt;p>By Chris Metz and Tim Bannister&lt;/p>
&lt;hr>
&lt;p>Topics covered in this blog.&lt;/p>

&lt;figure>
 &lt;img src="https://www.kubernetes.dev/blog/2021/improve-with-mermaid-diagrams/mermaid-blog-outline.svg"/> 
&lt;/figure>

&lt;!--- added padding to align text with diagram above --->
&lt;p style="padding-left: 200px; font-weight: bold">&lt;a href="https://mermaid-js.github.io/mermaid-live-editor/edit/#eyJjb2RlIjoiJSV7aW5pdDp7XCJ0aGVtZVwiOlwibmV1dHJhbFwifX0lJVxuZmxvd2NoYXJ0IExSXG4gICAgQltXaHkgYXJlIGRpYWdyYW1zPGJyPnVzZWZ1bCBmb3IgZG9jdW1lbnRhdGlvbj9dIC0tPiBDW1VzZSBNZXJtYWlkLmpzXVxuICAgIEMgLS0-IERbRXhhbXBsZXNdXG5cbiAgICAiLCJtZXJtYWlkIjoie1xuICBcInRoZW1lXCI6IFwiZGVmYXVsdFwiXG59IiwidXBkYXRlRWRpdG9yIjpmYWxzZSwiYXV0b1N5bmMiOnRydWUsInVwZGF0ZURpYWdyYW0iOmZhbHNlfQ">Live editor link: Topics Covered&lt;/a>&lt;/p>
&lt;hr>
&lt;h2 id="why-are-diagrams-useful-for-documentation">Why are diagrams useful for documentation?&lt;/h2>
&lt;ul>
&lt;li>
&lt;p>&lt;strong>Friendly landing spot&lt;/strong>. Greeting readers with a page full of text can be intimidating to those new to Kubernetes, software engineering and tech writing.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>&lt;strong>Faster grasp of concepts.&lt;/strong> A diagram can serve as a visual roadmap for details covered in the accompanying text.&lt;/p></description></item><item><title>How to choose a SIG as a non-code Kubernetes contributor</title><link>https://www.kubernetes.dev/blog/2021/07/09/how-to-choose-a-sig-as-a-non-code-kubernetes-contributor/</link><pubDate>Fri, 09 Jul 2021 00:00:00 +0000</pubDate><guid>https://www.kubernetes.dev/blog/2021/07/09/how-to-choose-a-sig-as-a-non-code-kubernetes-contributor/</guid><description>&lt;p>Kubernetes contributors aren&amp;rsquo;t people in capes or part of some secret society. How to start committing to the GitHub repos that make up the project &lt;a href="https://www.kubernetes.dev/docs/guide/"
 
 target="_blank" rel="noopener">is well documented&lt;/a>
, yet it remains intimidating for many.&lt;/p>
&lt;p>A few years ago, I spoke at an event and jokingly said, &amp;ldquo;Kubernetes is just a bunch of APIs and YAML&amp;hellip; I&amp;rsquo;m a contributor; you don&amp;rsquo;t believe me?&amp;rdquo; After that talk, someone pulled me aside and asked if I was the Kubernetes contributor. They wanted to get involved in the community. Then came the real question, &amp;ldquo;I don&amp;rsquo;t know which special interest group (SIG) I would work in.&amp;rdquo;&lt;/p></description></item><item><title>From Kubernetes for work to Kubernetes for play</title><link>https://www.kubernetes.dev/blog/2021/06/01/peeyush-contributor-story/</link><pubDate>Tue, 01 Jun 2021 00:00:00 +0000</pubDate><guid>https://www.kubernetes.dev/blog/2021/06/01/peeyush-contributor-story/</guid><description>&lt;div class="alert alert-primary" role="alert">


 &lt;i>
Addendum by &lt;a href="https://twitter.com/mbbroberg">Matt Broberg&lt;/a> on May 26, 2021
&lt;/i>
&lt;br>&lt;br>
It's with a heavy heart that this story of Peeyush's contribution begins by acknowledging his sudden passing.
Peeyush was a foundational member of the Upstream Marketing subproject.
I saw his friendly face every Friday for over a year,
and often chat about life before others joined the call.
He was kind, incredibly funny, and a loving father. 
He was also an incredible technologist with years of hands-on experience with Kubernetes,
but he spent his time building a space dedicated to communication and connection.
He valued making all contributors feel like this community can be their home, and he was incredibly successful at it.
&lt;br>&lt;br>
We lost a friend this week.
If you're mourning that loss,
know you're not alone.
Whatever you do to honor him,
may it be with as much kindness as he brought to others every day.
We have started to collect some of our &lt;a href="https://github.com/cncf/memorials/blob/main/peeyush-gupta.md" target="_blank" rel="noreferrer">thoughts and memories of Peeyush&lt;/a> as a memorial to him and what he brought to the community.
If you would like to share some of your own, please &lt;a href="https://github.com/cncf/memorials/blob/main/peeyush-gupta.md" target="_blank" rel="noreferrer">open a PR adding your own memories of him.&lt;/a>


&lt;/div>

&lt;p>My first encounter with Kubernetes was at my first job when a large banking customer wanted to evaluate Kubernetes on ppc64le architecture for application deployment. I was intrigued as it wasn&amp;rsquo;t every day when a bank seeks to consider something new! That was also my first interaction with Golang and I loved it instantly. I mean, who doesn&amp;rsquo;t love a cross compiled statically linked binary?! Before that, I was mostly working with Python and OpenStack, which are great as well. But Kubernetes opened a whole new world for me. Being familiar with Docker, which still was pretty new at that time, and the awesome cross-compilation capabilities of Go, I was quickly able to build a proof of concept, and my team loved it.&lt;/p></description></item><item><title>Announcing the Kubernetes Contributor Stories Series</title><link>https://www.kubernetes.dev/blog/2021/05/14/contributor-stories-series/</link><pubDate>Fri, 14 May 2021 00:00:00 +0000</pubDate><guid>https://www.kubernetes.dev/blog/2021/05/14/contributor-stories-series/</guid><description>&lt;p>The Kubernetes contributor community is vast. We have tens of thousands of members by any conservative estimate and many hundreds involved day-to-day. We are from all around the world, all kinds of backgrounds, all types of expertise, and we are all Kubernetes contributors.&lt;/p>
&lt;p>We also have this amazing new website dedicated specifically to Kubernetes contributors. With that in mind, let&amp;rsquo;s combine the two.&lt;/p>
&lt;p>We are asking any and &lt;strong>all contributors to share their unique story&lt;/strong> to highlight the many ways they show up to be part of the Kubernetes community. Here are some&lt;/p></description></item><item><title>Contributing to the Development Guide</title><link>https://www.kubernetes.dev/blog/2020/09/28/contributing-to-the-development-guide/</link><pubDate>Mon, 28 Sep 2020 00:00:00 +0000</pubDate><guid>https://www.kubernetes.dev/blog/2020/09/28/contributing-to-the-development-guide/</guid><description>&lt;p>When most people think of contributing to an open source project, I suspect they probably think of
contributing code changes, new features, and bug fixes. As a software engineer and a long-time open
source user and contributor, that&amp;rsquo;s certainly what I thought. Although I have written a good quantity
of documentation in different workflows, the massive size of the Kubernetes community was a new kind
of &amp;ldquo;client.&amp;rdquo; I just didn&amp;rsquo;t know what to expect when Google asked my compatriots and me at
&lt;a href="https://lionswaycontent.com/"
 
 target="_blank" rel="noopener">Lion&amp;rsquo;s Way&lt;/a>
 to make much-needed updates to the Kubernetes Development Guide.&lt;/p></description></item><item><title>Announcing the Contributor Website</title><link>https://www.kubernetes.dev/blog/2020/08/24/announcing-the-contributor-website/</link><pubDate>Mon, 24 Aug 2020 00:00:00 +0000</pubDate><guid>https://www.kubernetes.dev/blog/2020/08/24/announcing-the-contributor-website/</guid><description>&lt;p>Welcome to &lt;a href="https://www.kubernetes.dev"
 
 target="_blank" rel="noopener">kubernetes.dev&lt;/a>
, the Kubernetes Contributor website; built to become
the one stop shop for Kubernetes contributor content and news. It brings
important documentation scattered throughout the project into &lt;strong>one central
location&lt;/strong>.&lt;/p>
&lt;h2 id="resources-for-contributors">Resources for contributors&lt;/h2>
&lt;p>At launch, the contributor site will host a subset of our documentation. Some
highlights include (with short links in parenthesis):&lt;/p>
&lt;ul>
&lt;li>Our contributor guide (&lt;a href="https://k8s.dev/guide"
 
 target="_blank" rel="noopener">k8s.dev/guide&lt;/a>
) walks you through the first steps to
becoming a contributor&lt;/li>
&lt;li>The contributor cheatsheet (&lt;a href="https://k8s.dev/cheatsheet"
 
 target="_blank" rel="noopener">k8s.dev/cheatsheet&lt;/a>
) has common tips and tricks
for regular contribution&lt;/li>
&lt;li>The community calendar (&lt;a href="https://k8s.dev/calendar"
 
 target="_blank" rel="noopener">k8s.dev/calendar&lt;/a>
) shows all the upcoming community
group meetings&lt;/li>
&lt;li>Current release cycle information (&lt;a href="https://k8s.dev/release"
 
 target="_blank" rel="noopener">k8s.dev/release&lt;/a>
) lets you stay up-to-date
on upcoming release deadlines and milestones.&lt;/li>
&lt;/ul>
&lt;p>&lt;strong>TIP:&lt;/strong> As seen above, the &lt;a href="https://k8s.dev"
 
 target="_blank" rel="noopener">k8s.dev&lt;/a>
 domain can be substituted for
&lt;a href="https://www.kubernetes.dev"
 
 target="_blank" rel="noopener">kubernetes.dev&lt;/a>
 for easy short-linking :)&lt;/p></description></item></channel></rss>