# Kubernetes Contributors Blog

The Kubernetes contributor blog is used by the project to communicate community reports, contributor news, and any updates that might be relevant to people contributing to Kubernetes.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## From Working Group to SIG Architecture: spotlight on AI Conformance

DevFeed: [From Working Group to SIG Architecture: spotlight on AI Conformance](<https://devfeed.tech/articles/from-working-group-to-sig-architecture-spotlight-on-ai-conformance-106317.md>)

Original publisher: [Read original article](<https://www.kubernetes.dev/blog/2026/10/29/sig-arch-ai-conformance-2026/>)

Author: The Kubernetes Authors

Published: 2026-10-29T05:00:00Z

Content type: news

Language: en

Sources: [Kubernetes Contributors Blog](<https://devfeed.tech/sources/kubernetes-contributors-blog.md>)

Topics: [AI Integration Strategies](<https://devfeed.tech/topics/ai-integration-strategies.md>), [Service fabric](<https://devfeed.tech/topics/service-fabric.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [KServe](<https://devfeed.tech/topics/kserve.md>)

Tags: [2015](<https://devfeed.tech/tags/2015.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-platform](<https://devfeed.tech/tags/ai-platform.md>), [ai-workloads](<https://devfeed.tech/tags/ai-workloads.md>), [apps](<https://devfeed.tech/tags/apps.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [argo](<https://devfeed.tech/tags/argo.md>), [cncf](<https://devfeed.tech/tags/cncf.md>), [collaboration](<https://devfeed.tech/tags/collaboration.md>), [community](<https://devfeed.tech/tags/community.md>), [controllers](<https://devfeed.tech/tags/controllers.md>), [ecosystem](<https://devfeed.tech/tags/ecosystem.md>), [google](<https://devfeed.tech/tags/google.md>), [kserve](<https://devfeed.tech/tags/kserve.md>), [kubeflow](<https://devfeed.tech/tags/kubeflow.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [spotlight](<https://devfeed.tech/tags/spotlight.md>)

### AI overview

Kubernetes AI Conformance aims to reduce fragmentation and portability problems by establishing vendor-neutral requirements for AI infrastructure. The temporary Working Group published initial requirements and launched certification, then moved the work into a permanent SIG Architecture subproject to keep standards aligned with Kubernetes conformance and API design. The program handles fast-changing AI infrastructure through a tiered model: emerging capabilities begin as recommended SHOULD requirements and can become mandatory MUST requirements as APIs stabilize and adoption grows. It focuses on infrastructure capabilities, such as accelerator support through Dynamic Resource Allocation, rather than specific AI frameworks or model servers. The excerpt reports growth from 18 to 31 certified platforms within a few months. Contributors can join meetings, review or propose requirements using the KAR template, or expand automated Go tests; vendors can find certification details in cncf/k8s-ai-conformance.

### Source excerpt

In this SIG Architecture spotlight we talked with Janet Kuo (Google) and Yuan Tang (Red Hat) about the journey of AI Conformance in Kubernetes, from the initial Working Group to the integration SIG Architecture as a subproject. Introductions Frederico Muñoz and Kirti Goyal (FK): Hi Janet, Yuan, and thank you for the opportunity to learn a bit more about AI Conformance. Can you tell us a bit about yourselves and how you got involved in Kubernetes? Janet Kuo: I'm a Senior Staff Software Engineer at Google and have been a Kubernetes maintainer since 2015, joining the community just as we were racing toward the 1.0 launch. I started my journey writing the core workload controllers that standardized how applications are orchestrated on Kubernetes. Today, I lead SIG Apps as a Co-chair & TL, and also lead the AI Conformance program. My current focus is to ensure Kubernetes remains the best platform for the next generation of workloads, such as AI. Yuan Tang: I'm a Senior Principal Software Engineer at Red Hat, where I lead the development of our AI platform and drive our upstream open source strategy. I became involved in Kubernetes early on by fostering collaborations between the Kubernetes community and projects I was leading, including Kubeflow, Argo, and KServe. I later helped found and lead WG Serving and the AI Conformance program, advancing innovation and strengthening community collaboration around running AI workloads on Kubernetes. Program, Working Group, Subproject: the many shapes of AI Conformance FK: AI Conformance started as a CNCF Program, was it then you got involved? Janet Kuo: I was actually involved from day one since I pitched the original idea. It became obvious then that everyone was starting to run AI on Kubernetes, but vendors were building their infrastructure stacks in different ways. I got worried about ecosystem fragmentation. So I wrote up the initial Kubernetes AI Conformance Proposal, took it to the CNCF leadership to get their buy-in, and s

## One Signed Answer: SLSA Verification Summaries for registry.k8s.io Images

DevFeed: [One Signed Answer: SLSA Verification Summaries for registry.k8s.io Images](<https://devfeed.tech/articles/one-signed-answer-slsa-verification-summaries-for-registry-k8s-io-images-104466.md>)

Original publisher: [Read original article](<https://www.kubernetes.dev/blog/2026/10/28/registry-k8s-io-verification-summaries/>)

Author: The Kubernetes Authors

Published: 2026-10-28T00:00:00Z

Content type: article

Language: en

Sources: [Kubernetes Contributors Blog](<https://devfeed.tech/sources/kubernetes-contributors-blog.md>)

Topics: [slsa levels](<https://devfeed.tech/topics/slsa-levels.md>), [software artifact signing](<https://devfeed.tech/topics/software-artifact-signing.md>), [container image compliance](<https://devfeed.tech/topics/container-image-compliance.md>), [container images](<https://devfeed.tech/topics/container-images.md>), [Container Image Building](<https://devfeed.tech/topics/container-image-building.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [reproducible builds](<https://devfeed.tech/topics/reproducible-builds.md>)

Tags: [build](<https://devfeed.tech/tags/build.md>), [builder](<https://devfeed.tech/tags/builder.md>), [clusters](<https://devfeed.tech/tags/clusters.md>), [container](<https://devfeed.tech/tags/container.md>), [container-images](<https://devfeed.tech/tags/container-images.md>), [identity](<https://devfeed.tech/tags/identity.md>), [image](<https://devfeed.tech/tags/image.md>), [images](<https://devfeed.tech/tags/images.md>), [k8s](<https://devfeed.tech/tags/k8s.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [manifest](<https://devfeed.tech/tags/manifest.md>), [policy](<https://devfeed.tech/tags/policy.md>), [promotion](<https://devfeed.tech/tags/promotion.md>), [provenance](<https://devfeed.tech/tags/provenance.md>), [pull-request](<https://devfeed.tech/tags/pull-request.md>), [registry](<https://devfeed.tech/tags/registry.md>), [repositories](<https://devfeed.tech/tags/repositories.md>), [repository](<https://devfeed.tech/tags/repository.md>), [slsa](<https://devfeed.tech/tags/slsa.md>), [verification](<https://devfeed.tech/tags/verification.md>)

### AI overview

The Kubernetes image promoter now evaluates staging-image provenance against each project's policy in kubernetes/k8s.io, copies accepted attestations to registry.k8s.io, and publishes a signed SLSA verification summary (VSA) for each promoted image. Consumers can check the summary signer, verifier ID, result, and required build level with cosign and jq, or download it and run slsa-verifier with crane. Pin both signer and level: PASSED alone may mean only that promotion used a reviewed manifest, and an image without a policy can receive SLSA_BUILD_LEVEL_UNEVALUATED. SPO's v1.1.1 operator images, binaries, and Helm chart reach level 3; its bundle reaches only level 1 in that release, so a level 3 check fails. Projects need signed staging provenance, a manifest policy, and a test run. Cloud Build can provide level 1; level 3 requires provenance from an isolated GitHub workflow, then verification and attachment to the matching staging digest. Roll out policies in warn mode, test with kpromo cip, verify summaries, then use require to block violations. Summaries are created once at promotion, and most images promoted before October 2026 lack them; multi-architecture platform images need,

### Source excerpt

The Kubernetes community has been signing its container images since v1.24, and the images that kpromo, the Kubernetes image promoter (rewritten earlier this year), copies to registry.k8s.io get a signature. A signature answers one question: did this image go through the official promotion process? It does not answer the more interesting one: how was this image built, and from which source? Projects can attach signed SLSA provenance to their images to answer that. But to check it yourself, you have to know who builds each image, which identity signs its provenance, which builder it claims and which repository it comes from, for every project you pull from. That is a lot to ask, and in practice few people do it. Since October 2026, the image promoter does this work for you, once, at promotion time, and publishes the answer as a signed SLSA verification summary (VSA) for every image it promotes. In this blog post, I'd like to explain how it works, how you can verify it, and how your project can get its images verified at SLSA build level 1 or 3. How does it work? A project declares a provenance policy in its promoter manifest in kubernetes/k8s.io: who may sign its build attestations, which builders it trusts and at which level, and which source repositories its images come from. When a reviewed pull request promotes an image, the promoter evaluates the attestations of the staging image against that policy with the SLSA verifier, copies the accepted attestations to registry.k8s.io and writes the summary: flowchart LR build["Project build"] staging[("Staging registry")] policy["Provenance policy
in kubernetes/k8s.io"] promoter["Image promoter"] prod[("registry.k8s.io")] users["Users and clusters"] build -- "image and
signed provenance" --> staging staging --> promoter policy --> promoter promoter -- "image, attestations,
verification summary" --> prod prod -- "verify one summary" --> users The summaries are signed by a dedicated identity, promoter-summaries@

## Announcing the Workload Conformance Working Group

DevFeed: [Announcing the Workload Conformance Working Group](<https://devfeed.tech/articles/announcing-the-workload-conformance-working-group-102165.md>)

Original publisher: [Read original article](<https://www.kubernetes.dev/blog/2026/10/27/announcing-workload-conformance-wg/>)

Author: The Kubernetes Authors

Published: 2026-10-27T04:30:00Z

Content type: news

Language: en

Sources: [Kubernetes Contributors Blog](<https://devfeed.tech/sources/kubernetes-contributors-blog.md>)

Topics: [Resilience](<https://devfeed.tech/topics/resilience.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>), [observability](<https://devfeed.tech/topics/observability.md>)

Tags: [announce](<https://devfeed.tech/tags/announce.md>), [api](<https://devfeed.tech/tags/api.md>), [assessment](<https://devfeed.tech/tags/assessment.md>), [behavior](<https://devfeed.tech/tags/behavior.md>), [community](<https://devfeed.tech/tags/community.md>), [disruption](<https://devfeed.tech/tags/disruption.md>), [input](<https://devfeed.tech/tags/input.md>), [networking](<https://devfeed.tech/tags/networking.md>), [observability](<https://devfeed.tech/tags/observability.md>), [security](<https://devfeed.tech/tags/security.md>), [specification](<https://devfeed.tech/tags/specification.md>), [standard](<https://devfeed.tech/tags/standard.md>), [storage](<https://devfeed.tech/tags/storage.md>), [testing](<https://devfeed.tech/tags/testing.md>), [tests](<https://devfeed.tech/tags/tests.md>), [upgrade](<https://devfeed.tech/tags/upgrade.md>)

### AI overview

The Kubernetes Workload Conformance Working Group aims to give cluster operators and application maintainers a shared, repeatable baseline for checking how workloads behave at runtime. Its charter calls for a specification for each Kubernetes minor version, a method to test each requirement against a running workload, and upstream tooling to run those tests. Requirements must have objective tests executable by a test binary. The proposed scope spans security, disruption resilience, resource use, networking, storage, API usage, and observability; specific requirements and tests are still undecided. The work covers how workloads run, not application logic, and the tooling will not retest Certified Kubernetes coverage or require a packaging format or vendor tool. The group seeks real-world examples, reviewers, test and tooling contributors, early testers, SIG input, and long-term maintainers. It targets a stable first specification and working tests within two to three Kubernetes release cycles.

### Source excerpt

We are excited to announce that the Kubernetes community now has a Workload Conformance Working Group. The working group is writing a shared standard for how workloads behave at runtime on Kubernetes. To get it right, we need input from the people who build those workloads and from the people who run the clusters they're deployed on. Why workloads need a shared standard Certified Kubernetes tests the cluster, and Kubernetes AI Conformance tests whether a cluster can run AI and ML workloads. Nothing comparable exists for the workloads themselves, so cluster operators still check each application by hand before routine maintenance or a Kubernetes upgrade. The problems they find are familiar. A routine node drain is often how you discover that an application can't tolerate disruption. An upgrade can break an application that still depends on a removed API version. Others show up in day-to-day operation: workloads that ask for privileges they don't need, or reserve resources they never use. Kubernetes already documents much of this, including security and handling disruptions. Even so, every cluster operator ends up repeating the same assessment, and application maintainers get the same questions from each environment they support. A common specification with repeatable tests would give both groups the same baseline to start from. What the working group will deliver The charter sets out three deliverables: A specification of workload behavior for each Kubernetes minor version. A method for testing each requirement against a running workload. Upstream conformance tooling that implements those tests. The first step is deciding which workloads and behaviors the specification covers. The scope includes security, resilience during disruptions, resource use, networking, storage, API usage, and observability, but the group hasn't yet agreed on specific requirements or on how to test them. However, one rule is already set: every requirement needs an objective test that a test b

## Announcing the 2026 Steering Committee Election Results

DevFeed: [Announcing the 2026 Steering Committee Election Results](<https://devfeed.tech/articles/announcing-the-2026-steering-committee-election-results-88846.md>)

Original publisher: [Read original article](<https://www.kubernetes.dev/blog/2026/10/16/steering-committee-results-2026/>)

Author: The Kubernetes Authors

Published: 2026-10-16T15:00:00Z

Content type: news

Language: en

Sources: [Kubernetes Contributors Blog](<https://devfeed.tech/sources/kubernetes-contributors-blog.md>)

Topics: [Linux](<https://devfeed.tech/topics/linux.md>), [Fedora Project Community](<https://devfeed.tech/topics/fedora-project-community.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [community](<https://devfeed.tech/tags/community.md>), [complete](<https://devfeed.tech/tags/complete.md>), [coreweave](<https://devfeed.tech/tags/coreweave.md>), [defense](<https://devfeed.tech/tags/defense.md>), [get-involved](<https://devfeed.tech/tags/get-involved.md>), [github](<https://devfeed.tech/tags/github.md>), [governance](<https://devfeed.tech/tags/governance.md>), [health](<https://devfeed.tech/tags/health.md>), [io](<https://devfeed.tech/tags/io.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [meeting-notes](<https://devfeed.tech/tags/meeting-notes.md>), [members](<https://devfeed.tech/tags/members.md>), [notes](<https://devfeed.tech/tags/notes.md>), [pr](<https://devfeed.tech/tags/pr.md>), [project](<https://devfeed.tech/tags/project.md>), [public](<https://devfeed.tech/tags/public.md>), [red-hat](<https://devfeed.tech/tags/red-hat.md>), [steering](<https://devfeed.tech/tags/steering.md>), [suse](<https://devfeed.tech/tags/suse.md>)

### AI overview

The Kubernetes Steering Committee election is complete, with three of seven seats filled for two-year terms. Michael McCune, Janet Kuo, and Priyanka Saggu were elected; they join four continuing members. The committee governs the Kubernetes project and invites community participation through meetings, issues, pull requests, and its mailing list.

### Source excerpt

The 2026 Steering Committee Election is now complete. The Kubernetes Steering Committee consists of 7 seats, 3 of which were up for election in 2026. Incoming committee members serve a term of 2 years, and all members are elected by the Kubernetes Community. 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 its charter. Thank you to everyone who voted in the election; your participation helps support the community's continued health and success. Results Congratulations to the elected committee members whose two-year terms begin immediately (listed in alphabetical order by GitHub handle): Michael McCune (@elmiko), Red Hat Janet Kuo (@janetkuo), Google Priyanka Saggu (@priyankasaggu11929), SUSE They join continuing members: Kat Cosgrove (@katcosgrove), VillageSQL Paco Xu 徐俊杰 (@pacoxu), DaoCloud Rita Zhang (@ritazh), CoreWeave Maciej Szulik (@soltysh), Defense Unicorns Big thanks! Thank you and congratulations on a successful election to this round's election officers: Nina Polshakova Sreeram Venkitesh Rey Lejano Thanks to the Emeritus Steering Committee Members. Your service is appreciated by the community: Antonio Ojea (@aojea), Google Benjamin Elder (@BenTheElder), Google Sascha Grunert (@saschagrunert), Red Hat And thank you to all the candidates who came forward to run for election. Get involved with the Steering Committee This governing body, like all of Kubernetes, is open to all. You can follow along with Steering Committee meeting notes and weigh in by filing an issue or creating a PR against their repo. They have an open meeting on the first Wednesday at 8am PT of every month. They can also be contacted at their public mailing list steering@kubernetes.io. You can see what the Steering Committee meetings are all about by watching past meetings on the YouTube Playlist.

## KCD Around the World: Nigeria

DevFeed: [KCD Around the World: Nigeria](<https://devfeed.tech/articles/kcd-around-the-world-nigeria-88138.md>)

Original publisher: [Read original article](<https://www.kubernetes.dev/blog/2026/10/15/kcd-around-the-world-nigeria/>)

Author: The Kubernetes Authors

Published: 2026-10-15T07:00:00Z

Content type: article

Language: en

Sources: [Kubernetes Contributors Blog](<https://devfeed.tech/sources/kubernetes-contributors-blog.md>)

Topics: [Developer Events](<https://devfeed.tech/topics/developer-events.md>), [coding-community](<https://devfeed.tech/topics/coding-community.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [Hacktoberfest](<https://devfeed.tech/topics/hacktoberfest.md>)

Tags: [certifications](<https://devfeed.tech/tags/certifications.md>), [cloud-native](<https://devfeed.tech/tags/cloud-native.md>), [community](<https://devfeed.tech/tags/community.md>), [contributors](<https://devfeed.tech/tags/contributors.md>), [days](<https://devfeed.tech/tags/days.md>), [developers](<https://devfeed.tech/tags/developers.md>), [open-source](<https://devfeed.tech/tags/open-source.md>)

### AI overview

Organizers of KCD Nigeria describe the growth of the country's Kubernetes community, the role of local chapters and events in connecting developers, and plans for the 2026 gathering. They discuss opportunities for African practitioners to learn about cloud native technologies, contribute to open source, and share how local organizations use Kubernetes.

### Source excerpt

Welcome back to KCD Around the World, a series where we explore Kubernetes Community Days from every corner of the globe. 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 share what makes it unique. This stop: Nigeria. KCD Nigeria started back in 2021 as KCD Africa, the first Kubernetes Community Days on the continent. On October 24, 2026, the community comes together at Zone Tech Park in Gbagada, Lagos, for its fourth edition, themed "Telling the African Cloud Native Story". We spoke with organizers Divine Odazie, Ileriayo Adebiyi, Somtochi Onyekwere, and Uchechukwu Obasi about how the Nigerian cloud native community has grown and where it is headed. Meet the community Destiny Erhabor (DE): Could you each introduce yourselves and tell us how you got involved in Kubernetes? Divine Odazie (DO): I'm a CNCF Ambassador, founder of EverythingDevOps, and a program committee member for Platform Engineering Day North America 2026. As a developer advocate, I help cloud native vendors build better end-user tools and infrastructure. I've contributed to Kubernetes, Cilium, and other projects, and I've given talks and workshops at KubeCon North America, Open Source Summit Europe, Kubernetes Community Days, and Ansible Contributor Summit. My journey in Kubernetes started in 2021, after working with Docker and Docker Compose at an e-commerce startup. I heard about Kubernetes at an open source conference where Chris Aniszczyk spoke. He shared a Kubernetes and Cloud Native Associate (KCNA) voucher, which I used to take and pass the exam. Five years later, I hold four certifications, I'm a CNCF Ambassador, I've organized a KCD, attended several KubeCons, and worked on Data on Kubernetes, platform engineering, and much more. Ileriayo Adebiyi (IA): I used to work as an IT engineer. I handled everything the developers couldn't, from managing servers to helping get the

## SIG Instrumentation Welcomes kubernetes-mixin

DevFeed: [SIG Instrumentation Welcomes kubernetes-mixin](<https://devfeed.tech/articles/sig-instrumentation-welcomes-kubernetes-mixin-85161.md>)

Original publisher: [Read original article](<https://www.kubernetes.dev/blog/2026/10/12/sig-instrumentation-welcomes-kubernetes-mixin/>)

Author: The Kubernetes Authors

Published: 2026-10-12T00:00:00Z

Content type: news

Language: en

Sources: [Kubernetes Contributors Blog](<https://devfeed.tech/sources/kubernetes-contributors-blog.md>)

Topics: [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [infrastructure monitoring](<https://devfeed.tech/topics/infrastructure-monitoring.md>), [Grafana](<https://devfeed.tech/topics/grafana.md>), [Prometheus alert rules](<https://devfeed.tech/topics/prometheus-alert-rules.md>)

Tags: [grafana](<https://devfeed.tech/tags/grafana.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [infrastructure-monitoring](<https://devfeed.tech/tags/infrastructure-monitoring.md>), [instrumentation](<https://devfeed.tech/tags/instrumentation.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [prometheus](<https://devfeed.tech/tags/prometheus.md>)

### AI overview

SIG Instrumentation has adopted kubernetes-mixin, a Kubernetes and Prometheus monitoring project that provides recording rules, alert rules, and Grafana dashboards. The repository transfer keeps existing Git remote and runbook URLs working, while maintenance continues alongside Kubernetes releases.

### Source excerpt

The kubernetes-mixin project, with over eight years of commit history, has been adopted by SIG Instrumentation. What is kubernetes-mixin? Kubernetes and Prometheus go hand in hand when it comes to monitoring clusters; a lot of data is already provided by many components and through related projects such as kube-state-metrics, cAdvisor, and node_exporter. However, knowing which metrics to look at, how to keep PromQL queries performant in large fleets, and what constitutes an error condition can be a tricky subject. This is where kubernetes-mixin comes in; it provides recording rules (such as namespace_workload_pod:kube_pod_owner:relabel) to speed up and simplify queries, alert rules (like KubePodCrashLooping) to identify info/warning/critical conditions, and Grafana dashboards to visualize the metrics. These assets work together to provide an infrastructure monitoring setup available to install directly or via downstream projects such as kube-prometheus-stack. Adoption by SIG Instrumentation Following a #sig-instrumentation Slack discussion, a website issue to provide documentation on instrumentation best practices was created. It seemed many of the alerts provided by kubernetes-mixin were recognized as commonly deployed but were not part of an official Kubernetes project or subproject, making it difficult to reference in official Kubernetes documentation. Consensus was reached among the original maintainers and KEP-5905 was created to track the move of the kubernetes-mixin repo into the Kubernetes SIGs organization. The transfer was confirmed to be completed on Tuesday, September 8, 2026. Ongoing maintenance and compatibility Transferring the repo, rather than forking, allows existing Git remote and runbook URLs to continue working as before. Regular maintenance continues (see below to get involved!) and kubernetes-mixin continues to follow the Kubernetes release cycle, tracking new metrics and deprecations based on real-world usage. Getting involved Whether it's a

## KCD Around the World: Sofia

DevFeed: [KCD Around the World: Sofia](<https://devfeed.tech/articles/kcd-around-the-world-sofia-60756.md>)

Original publisher: [Read original article](<https://www.kubernetes.dev/blog/2026/09/28/kcd-around-the-world-sofia/>)

Author: The Kubernetes Authors

Published: 2026-09-28T00:00:00Z

Content type: article

Language: en

Sources: [Kubernetes Contributors Blog](<https://devfeed.tech/sources/kubernetes-contributors-blog.md>)

Topics: [developer-relations](<https://devfeed.tech/topics/developer-relations.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [engineering-leadership](<https://devfeed.tech/topics/engineering-leadership.md>), [Plover](<https://devfeed.tech/topics/plover.md>)

Tags: [ambassador](<https://devfeed.tech/tags/ambassador.md>), [cloud-native](<https://devfeed.tech/tags/cloud-native.md>), [cncf](<https://devfeed.tech/tags/cncf.md>), [collaboration](<https://devfeed.tech/tags/collaboration.md>), [communities](<https://devfeed.tech/tags/communities.md>), [community](<https://devfeed.tech/tags/community.md>), [contributors](<https://devfeed.tech/tags/contributors.md>), [event](<https://devfeed.tech/tags/event.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [open-source-collaboration](<https://devfeed.tech/tags/open-source-collaboration.md>), [people](<https://devfeed.tech/tags/people.md>)

### AI overview

KCD Around the World interviews the organizers of the second Kubernetes Community Days in Sofia about their roles, community-building work, and the event's purpose as a meeting place for Bulgaria's cloud native community.

### Source excerpt

Welcome back to KCD Around the World, a series where we explore Kubernetes Community Days from every corner of the globe. 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 share what makes it unique. This stop: Sofia, Bulgaria. On Tuesday, September 29, 2026, the second KCD Sofia takes place at Sofia Event Center. We spoke with three of its organizers, Yoana, Spas, and Orlin, about building a meeting point for Bulgaria's cloud native community and what goes into running it for a second year. Meet the community Kashish Verma (KV): Could you each introduce yourselves and tell us how you got involved in Kubernetes? Yoana: Hi, I'm Yoana, one of the KCD Sofia organizers. My background isn't purely technical. Most of my work has been about building technology communities and bringing companies, engineers, and people who care about the ecosystem together. At KCD Sofia, I look after partnerships, sponsors, communication, logistics, and coordination, basically everything that has to fall into place before the doors can open. What pulled me into the Kubernetes world was the community. You realize pretty quickly that it's not just about the technology, it's about people sharing what they know and building things together. Spas: Hi, I'm Spas! I've worked with cloud native technologies for years, both in my day job and in the community, and I'm a CNCF Ambassador. For me, Kubernetes has always been about more than what it can do technically. It's the ecosystem around it that keeps me hooked: open source, collaboration, and people sharing knowledge. At KCD Sofia, I help shape the agenda and review talk topics, and I also work on the event concept and some of the visual and organizational details. Orlin: Hey, I'm Orlin. I've been on the KCD Sofia team since the very first edition in 2025, and I end up doing a bit of everything, from planning and coordination to co

## What I learned from joining the Blog team

DevFeed: [What I learned from joining the Blog team](<https://devfeed.tech/articles/what-i-learned-from-joining-the-blog-team-58862.md>)

Original publisher: [Read original article](<https://www.kubernetes.dev/blog/2026/09/23/what-i-learned-from-joining-the-blog-team/>)

Author: Is the author listed correctly

Published: 2026-09-23T18:00:00Z

Content type: tutorial

Language: en

Sources: [Kubernetes Contributors Blog](<https://devfeed.tech/sources/kubernetes-contributors-blog.md>)

Topics: [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [Documentation](<https://devfeed.tech/topics/documentation.md>), [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [Hugo](<https://devfeed.tech/topics/hugo.md>)

Tags: [article](<https://devfeed.tech/tags/article.md>), [blog](<https://devfeed.tech/tags/blog.md>), [contributor](<https://devfeed.tech/tags/contributor.md>), [formatting](<https://devfeed.tech/tags/formatting.md>), [github](<https://devfeed.tech/tags/github.md>), [hugo](<https://devfeed.tech/tags/hugo.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [review](<https://devfeed.tech/tags/review.md>), [style-guide](<https://devfeed.tech/tags/style-guide.md>), [team](<https://devfeed.tech/tags/team.md>)

### AI overview

A practical guide to joining and reviewing the Kubernetes blog team. It explains where to find blog pull requests, how to apply blog and style guidelines, and how draft and publication workflows work.

### Source excerpt

When I joined the Kubernetes blog team, I did not know quite what to expect. Here is everything I picked up along the way from finding your first PR to getting an article published. Everyone starts somewhere and I am glad you are starting here. Before I get into it, let me answer the question I had when I first joined. Am I actually qualified to do this? Yes. Genuinely. You do not need years of Kubernetes experience to do this well. Curiosity and being keen will take you further than you think. The more you review, the more natural it feels. Everyone on this team had a first review. It went fine. Yours will too. Where to find blogs to review? Blog PRs are spread across two repositories depending on where they will be published. Here is where to find them: Open blog PRs on k/website Open PRs on k/contributor-site Yay, just pick one and go for it! What we do not publish? Before you invest real time in a review, please spend two minutes here: What we do not publish Not everything that comes in is a fit, so it is worth a quick check before you go deep. And if you are ever not sure, just ask the team (it is OK to ask)! How do I know what a good blog looks like? The standards are already set. There are proper guidelines for this, please read them before you start reviewing: Blog guidelines Style guide Blogs use the same style guide as docs but blogs are not docs, so there are some exceptions. Have a look at them as well: Blog-specific exceptions I know it's a lot to take in at once, and that's okay. Start with one thing, maybe punctuation or formatting, and go from there. You will naturally get faster over time. The details that are easy to miss This is the part I really want you to slow down on. These are the small things that quietly delay publication. Every blog goes through two stages. First it gets merged as a draft. Then, in a separate PR, it gets published. So, these are the few things I want you to treat as a pre-merge checklist. (Trust me it really helped me, and

## Spotlight on SIG Apps

DevFeed: [Spotlight on SIG Apps](<https://devfeed.tech/articles/spotlight-on-sig-apps-58165.md>)

Original publisher: [Read original article](<https://www.kubernetes.dev/blog/2026/09/22/sig-apps-spotlight/>)

Author: The Kubernetes Authors

Published: 2026-09-22T18:00:00Z

Content type: article

Language: en

Sources: [Kubernetes Contributors Blog](<https://devfeed.tech/sources/kubernetes-contributors-blog.md>)

Topics: [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [Deployment](<https://devfeed.tech/topics/deployment.md>), [Resilience](<https://devfeed.tech/topics/resilience.md>), [Software](<https://devfeed.tech/topics/software.md>), [Cloud Native Ecosystem](<https://devfeed.tech/topics/cloud-native-ecosystem.md>)

Tags: [deployment](<https://devfeed.tech/tags/deployment.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [resilience](<https://devfeed.tech/tags/resilience.md>), [scaling](<https://devfeed.tech/tags/scaling.md>), [software](<https://devfeed.tech/tags/software.md>), [stateful](<https://devfeed.tech/tags/stateful.md>), [stateless](<https://devfeed.tech/tags/stateless.md>)

### AI overview

This Kubernetes SIG Apps spotlight discusses workload management, application lifecycle management, resilience during failures and upgrades, and the evolution of Kubernetes controllers. It includes perspectives from SIG Apps chairs on the Workloads API, controller reliability, and support for AI workloads.

### Source excerpt

Spotlight on SIG Apps As Kubernetes adoption has grown, the conversation has shifted beyond running containers to managing increasingly complex application lifecycles. Modern platforms support stateless web services, stateful databases, batch processing, AI workloads, and platform services. At the same time, they must remain reliable during upgrades, scaling events, and infrastructure failures. Every Kubernetes user relies on SIG Apps, whether they realize it or not. Deployments, StatefulSets, DaemonSets, Jobs, and CronJobs form the foundation of how applications are deployed, updated, scaled, and operated across the Kubernetes ecosystem. SIG Apps is focused on improving workload resilience, refining application lifecycle management, and addressing the operational challenges that emerge when applications encounter node failures, rollout disruptions, and increasingly complex infrastructure environments. In this spotlight, we sit down with two of the three SIG Apps chairs Janet Kuo and Maciej Szulik to discuss the evolution of Kubernetes workload management, the challenges of balancing application reliability with operational simplicity, and the future of application lifecycle management within one of Kubernetes' most influential Special Interest Groups. Introducing SIG Apps Natalie Fisher: Can you introduce yourself, your role, and how you got involved in SIG Apps? Janet Kuo: I'm a Senior Staff Software Engineer at Google and have been a Kubernetes maintainer since 2015, joining the community just as we were racing toward the 1.0 launch. In those early days, my focus was on building the core Workloads API, specifically developing controllers like Deployment, ReplicaSet, StatefulSet, and DaemonSet, defining their rollout behaviors, and bringing them from initial designs to GA. That hands-on work was my entry point into SIG Apps. Since then, I've stayed deeply involved in both the technical and community sides of Kubernetes. I have led SIG Apps as Co-Chair and Tech Lea

## Publishing a Kubernetes SIG's Images to registry.k8s.io

DevFeed: [Publishing a Kubernetes SIG's Images to registry.k8s.io](<https://devfeed.tech/articles/publishing-a-kubernetes-sig-s-images-to-registry-k8s-io-31455.md>)

Original publisher: [Read original article](<https://www.kubernetes.dev/blog/2026/09/16/publishing-images-to-registry-k8s-io/>)

Author: The Kubernetes Authors

Published: 2026-09-16T18:00:00Z

Content type: tutorial

Language: en

Sources: [Kubernetes Contributors Blog](<https://devfeed.tech/sources/kubernetes-contributors-blog.md>)

Topics: [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [container images](<https://devfeed.tech/topics/container-images.md>), [GitHub Actions](<https://devfeed.tech/topics/github-actions.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Google Cloud Platform (GCP)](<https://devfeed.tech/topics/google-cloud.md>)

Tags: [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [container-image](<https://devfeed.tech/tags/container-image.md>), [container-image-registry](<https://devfeed.tech/tags/container-image-registry.md>), [container-images](<https://devfeed.tech/tags/container-images.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [github-actions](<https://devfeed.tech/tags/github-actions.md>), [google-cloud](<https://devfeed.tech/tags/google-cloud.md>), [guide](<https://devfeed.tech/tags/guide.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>)

### AI overview

A guide to publishing official Kubernetes SIG container images through registry.k8s.io. It explains why GHCR is unsuitable for public distribution and describes the ordered workflow involving Prow, Google Cloud Build, staging registries, and image promotion.

### Source excerpt

If you're publishing container images for a Kubernetes SIG project, you might expect the same publishing workflow used by other container registries to work. That was my assumption too. My workflow successfully published the images, but they weren't publicly available. Instead, official Kubernetes project images are distributed through registry.k8s.io , the Kubernetes project's official container image registry. No single step was hard, but the steps were spread across multiple repositories and had to happen in a particular order, something I mostly learned by tripping over them. This post is the guide I wish I had at the start. It walks through that workflow end to end using Cluster Inventory API from SIG Multicluster as an example. The same process applies to eligible Kubernetes subprojects that publish official container images. My first attempt: GHCR I first tried a common GitHub release pattern: using GitHub Actions to publish images to ghcr.io on a tag push (cluster-inventory-api#40 ). The workflow succeeded, but Kubernetes GitHub organizations keep GHCR packages private, so GHCR cannot be used for public distribution. As described in the registry.k8s.io documentation , official images take a different route: Prow (the Kubernetes project's CI/CD system) picks up a tag push and runs Google Cloud Build on Kubernetes-owned infrastructure to push the image to a staging registry, and the image promoter then copies it to registry.k8s.io. The first-time setup, step by step Besides the image-owning repository, this touches three infrastructure repositories: kubernetes/k8s.io , kubernetes/test-infra , and kubernetes/org . The pieces depend on each other like this: Before you start: decide your project details Before setting up the publishing workflow, decide a few project-specific details. These values will be reused throughout the setup when creating the staging registry, configuring image builds, and setting up image promotion: <project>, which determines the staging

## Kubernetes v1.37: Declarative Validation Drives Record-Breaking API Reviews

DevFeed: [Kubernetes v1.37: Declarative Validation Drives Record-Breaking API Reviews](<https://devfeed.tech/articles/kubernetes-v1-37-declarative-validation-drives-record-breaking-api-reviews-17604.md>)

Original publisher: [Read original article](<https://www.kubernetes.dev/blog/2026/08/27/kubernetes-v1-37-declarative-validation/>)

Author: The Kubernetes Authors

Published: 2026-08-27T00:00:00Z

Content type: release

Language: en

Sources: [Kubernetes Contributors Blog](<https://devfeed.tech/sources/kubernetes-contributors-blog.md>)

Topics: [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [Developer Tools](<https://devfeed.tech/topics/developer-tools.md>), [Code](<https://devfeed.tech/topics/code.md>), [releases](<https://devfeed.tech/topics/releases.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [declarative](<https://devfeed.tech/tags/declarative.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [release](<https://devfeed.tech/tags/release.md>), [tooling](<https://devfeed.tech/tags/tooling.md>), [validation](<https://devfeed.tech/tags/validation.md>)

### AI overview

This article reports that Kubernetes v1.37 processed a project-record 118 API review pull requests, up from 88 in v1.36, while reviewers maintained pace. It identifies expanded declarative validation, which reached general availability in v1.36, as a primary efficiency driver; roughly 75% of new validations used declarative validation.

### Source excerpt

Kubernetes v1.37 saw the most API reviews in the project's history. API reviewers reviewed an all-time high of 118 PRs , up from 88 in the v1.36 release. Despite this massive surge, the API reviewers were able to keep pace. A primary driver of this efficiency was the significant expansion of declarative validation (DV), which reached General Availability (GA) in v1.36 and experienced its largest growth to date in v1.37. Declarative validation (DV) allows Kubernetes developers to declare validation rules using Interface Definition Language (IDL) tags (like +k8s:optional or +k8s:minimum=0) directly in the types.go files that define the native API types. These tags are then used by the code generator, validation-gen, to automatically generate the required validation functions, replacing the need for complex, handwritten imperative validation logic. Roughly 75% of new validations were written in DV, significantly saving reviewers' time. Because the tooling handles the complexity, reviewers provided minimal guidance on the validation logic compared to previous releases. Additionally, linters and other correctness checks were a major factor in maintaining this velocity. Pre-reviews conducted by Joel Speed (@joelspeed ), Patrick Ohly (@pohly ), Maciej Szulik (@soltysh ), Tim Allclair (@tallclair ), Joe Betz (@jpbetz ), and Mo Khan (@enj ) saved a lot of time for our core API reviewers like Jordan (@liggitt ) and Tim (@thockin ). (A special congratulations to Joe, who was promoted to API approver this release!) "The guardrail work that made use of declarative validation tags automatically require covering test cases made a big difference in 1.37. Validation expressed as declarative tags shrank the complexity of implementations and reviews, and is feeding a virtuous cycle where reviewers and authors prefer declarative validation once they get used to it. There were a few PRs this cycle that had almost no validation.go changes at all (🎉), and a lot where all the straightforwa

## KCD Around the World: San Francisco Bay Area

DevFeed: [KCD Around the World: San Francisco Bay Area](<https://devfeed.tech/articles/kcd-around-the-world-san-francisco-bay-area-17603.md>)

Original publisher: [Read original article](<https://www.kubernetes.dev/blog/2026/08/19/kcd-around-the-world-san-francisco/>)

Author: The Kubernetes Authors

Published: 2026-08-19T00:00:00Z

Content type: article

Language: en

Sources: [Kubernetes Contributors Blog](<https://devfeed.tech/sources/kubernetes-contributors-blog.md>)

Topics: [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [Cloud Native Ecosystem](<https://devfeed.tech/topics/cloud-native-ecosystem.md>), [Google](<https://devfeed.tech/topics/google.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [cloud-native](<https://devfeed.tech/tags/cloud-native.md>), [cncf](<https://devfeed.tech/tags/cncf.md>), [community](<https://devfeed.tech/tags/community.md>), [contributors](<https://devfeed.tech/tags/contributors.md>), [developer-relations](<https://devfeed.tech/tags/developer-relations.md>), [google-cloud](<https://devfeed.tech/tags/google-cloud.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [open-source](<https://devfeed.tech/tags/open-source.md>)

### AI overview

An interview with organizers of the second KCD San Francisco Bay Area, scheduled for September 1, 2026, explores the event's origins, the local Kubernetes community, and the organizers' backgrounds in Kubernetes and cloud-native technology.

### Source excerpt

Welcome back to KCD Around the World, a series where we explore Kubernetes Community Days from every corner of the globe. 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 share what makes it unique. This stop: San Francisco Bay Area. Coming up on September 1, 2026 is the second KCD San Francisco Bay Area, held at the Computer History Museum in Mountain View. We spoke with three of its organizers, Rey Lejano, Lisa-Marie Namphy, and Jason (Jay) Smith, about what makes the Bay Area community tick. Meet the community Kashish Verma (KV): Could you each introduce yourselves and tell us how you got involved in Kubernetes? Rey Lejano (RL): I'm one of the KCD San Francisco Bay Area organizers, a Kubernetes SIG Docs co-chair and SIG Security subproject lead, and I work at Red Hat. I've served on seven Release Teams, including as the v1.23 Release Lead. A conversation with a Kubernetes contributor at the 2019 KubeCon in San Diego is what pulled me into contributing to the project. Lisa-Marie Namphy (LN): Hi! I'm Lisa-Marie Namphy (Lisa), I've been a CNCF Ambassador since the early days of the program and have run one of the largest Kubernetes/Cloud Native user groups for over 10 years, now called Cloud Native Silicon Valley. I also run the Developer Relations and Tech Learning team at Intuit, where open source is core to how we build: our flagship products like TurboTax and QuickBooks run on Kubernetes and other CNCF technologies, including Argo, which Intuit originally created and donated. Jason "Jay" Smith (JS): I'm a Staff Customer Engineer on the Application Ecosystem team at Google Cloud, though I like to call myself the "Cloud Alchemist," since I help customers move from legacy monolithic architectures to microservices. On the community side, I'm a co-lead for the Cloud Native San Francisco Community, an organizer for the 2025 and 2026 KCD San Francisc

## KCD Around the World: New York

DevFeed: [KCD Around the World: New York](<https://devfeed.tech/articles/kcd-around-the-world-new-york-17602.md>)

Original publisher: [Read original article](<https://www.kubernetes.dev/blog/2026/07/28/kcd-around-the-world-new-york/>)

Author: The Kubernetes Authors

Published: 2026-07-28T18:00:00Z

Content type: article

Language: en

Sources: [Kubernetes Contributors Blog](<https://devfeed.tech/sources/kubernetes-contributors-blog.md>)

Topics: [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [Cloud](<https://devfeed.tech/topics/cloud.md>)

Tags: [community](<https://devfeed.tech/tags/community.md>), [interview](<https://devfeed.tech/tags/interview.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>)

### AI overview

An interview with Christopher Tineo, an organizer of KCD NY 2026, about his path from volunteering to organizing and the New York Kubernetes community.

### Source excerpt

Welcome to KCD Around the World, a new series where we explore Kubernetes Community Days 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'll share what makes it unique. Our first stop: New York City. To learn what made this year's event special, we interview Christopher Tineo, one of the organizers for KCD NY 2026. Meet the community Kashish Verma (KV): Hello Christopher, and welcome. Could you start by introducing yourself and telling us how you got involved with Kubernetes and the cloud native community? Christopher Tineo (CT): I'm Christopher Tineo. This year I organized KCD NY 2026, where my main focus was building out the event agenda and our event website . Going back a bit, I first got involved through a meetup organized in Santo Domingo by Victor Recio around February 2024, right after I got my CKAD certification . I had the chance to connect with a few engineers who eventually became organizers for our CNCF chapter , Ayesha Yege and Enmanuel Medina. As I dived deeper into the CNCF community, I knew I wanted to be a part of it. After watching Julia Morgado's inspiring talk at KubeCon 2023 , I was driven to take action. Despite living in the Dominican Republic, I booked a flight to KCD NY 2024 and applied to volunteer. Luckily, I got a spot on the team, and it turned out to be an incredible firsthand experience with the community. KV: What motivated you to volunteer or organize KCD New York? CT: NYC has been the start of all the great things that came after that first KCD NY in 2024, so I wanted to be that person that could motivate more engineers from my country to improve their careers and learn more from the Cloud Native community, which wasn't as developed back then. Attending as a volunteer in 2024 is what motivated me to c

## Human-Centered Automation for Kubernetes Localization in the AI Era

DevFeed: [Human-Centered Automation for Kubernetes Localization in the AI Era](<https://devfeed.tech/articles/human-centered-automation-for-kubernetes-localization-in-the-ai-era-17600.md>)

Original publisher: [Read original article](<https://www.kubernetes.dev/blog/2026/06/26/human-centered-automation-kubernetes-localization-ai-era/>)

Author: The Kubernetes Authors

Published: 2026-06-26T22:00:00Z

Content type: article

Language: en

Sources: [Kubernetes Contributors Blog](<https://devfeed.tech/sources/kubernetes-contributors-blog.md>)

Topics: [Localization (l10n)](<https://devfeed.tech/topics/localization.md>), [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [Documentation](<https://devfeed.tech/topics/documentation.md>), [Maintainers](<https://devfeed.tech/topics/maintainers.md>)

Tags: [automation](<https://devfeed.tech/tags/automation.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [maintainers](<https://devfeed.tech/tags/maintainers.md>), [translation](<https://devfeed.tech/tags/translation.md>)

### AI overview

This article describes a Kubernetes localization mentorship project focused on human-centered automation. Its goal is to help maintainers prioritize review work by improving visibility and reducing repetitive triage, rather than automating translation. The approach addresses ongoing maintenance of localized documentation as English source content changes.

### Source excerpt

This year, the Kubernetes localization subproject participated in LFX Mentorship for the first time through the project "CNCF - Kubernetes: SIG Docs Localization: AI-era localization automation" . The work was also tracked in kubernetes/website#54075 . As the mentee on this project, I worked with Kubernetes SIG Docs localization mentors on a practical maintenance question: In an era of rapidly improving AI translation tools, what kind of automation actually helps localization maintainers? 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. For this mentorship project, the focus was human-centered automation: tools that improve visibility, reduce repetitive triage, and protect human reviewer attention. The goal was not to automate translation. The goal was to make localization review work easier to prioritize. The maintenance problem behind localization Kubernetes documentation changes continuously. Concepts are clarified, examples are updated, feature states move forward, commands are corrected, and API-related wording changes. When English documentation changes, localized pages may also need updates. For active localization teams, this creates ongoing maintenance work. Reviewers need to understand both the source content and the target language, and they need enough Kubernetes context to decide whether a change affects technical accuracy. Existing signals can help detect possible drift. Some localization teams compare Git history to see whether the English source changed after a localized page was last updated, and Kubernetes website pages may also show lastmod warnings when localized content appears older than the English source. These signals are useful, but they do not always explain what kind of review is n

## Open source maintainership in the age of AI

DevFeed: [Open source maintainership in the age of AI](<https://devfeed.tech/articles/open-source-maintainership-in-the-age-of-ai-17601.md>)

Original publisher: [Read original article](<https://www.kubernetes.dev/blog/2026/06/26/open-source-maintainership-in-the-age-of-ai/>)

Author: CLA enforcement

Published: 2026-06-26T18:00:00Z

Content type: article

Language: en

Sources: [Kubernetes Contributors Blog](<https://devfeed.tech/sources/kubernetes-contributors-blog.md>)

Topics: [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [Code quality](<https://devfeed.tech/topics/code-quality.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-assisted-coding](<https://devfeed.tech/tags/ai-assisted-coding.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [policy](<https://devfeed.tech/tags/policy.md>), [pull-request](<https://devfeed.tech/tags/pull-request.md>), [quality](<https://devfeed.tech/tags/quality.md>)

### AI overview

This article explains how the Kubernetes community is adapting its maintainership practices to AI-assisted coding. It describes an AI policy requiring contributors to disclose AI assistance, remain responsible for changes, avoid attributing commits to AI, satisfy contributor license agreement checks, and personally respond to review comments.

### Source excerpt

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. The first step of this journey was to develop an AI policy. This seems mundane and bureaucratic but there were many PRs that derailed into discussions around AI usage. The AI policy helps steer the conversation around the project's stance on AI and provides a clear signal to contributors on how to use these tools responsibly. Kubernetes AI policy The Kubernetes project has established clear guidelines for AI-assisted contributions that balance innovation with accountability. These policies are designed to maintain code quality and ensure human oversight while acknowledging that AI tools can be valuable aids in the development process. Transparency first Contributors must disclose when AI tools have been used to assist with a pull request. A simple statement in the PR description such as "This PR was written in part with the assistance of generative AI" is sufficient. This transparency helps reviewers understand the context and apply appropriate scrutiny. Human accountability While AI tools can assist, the human contributor remains fully responsible for every change. The policy explicitly prohibits: Listing AI as a co-author on commits Using AI co-signing on commits Adding trailers like "assisted-by" or "co-developed" that attribute work to AI This isn't about diminishing AI's role as a tool--it's about maintaining clear accountability. If something breaks, there needs to be a human who understands why and can fix it. CLA enforcement for co-authors The CNCF provides a tool for verifying the

## Spotlight on WG Device Management

DevFeed: [Spotlight on WG Device Management](<https://devfeed.tech/articles/spotlight-on-wg-device-management-17599.md>)

Original publisher: [Read original article](<https://www.kubernetes.dev/blog/2026/06/24/wg-device-management-spotlight-2026/>)

Author: The Kubernetes Authors

Published: 2026-06-24T18:00:00Z

Content type: article

Language: en

Sources: [Kubernetes Contributors Blog](<https://devfeed.tech/sources/kubernetes-contributors-blog.md>)

Topics: [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [Hardware](<https://devfeed.tech/topics/hardware.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [hardware](<https://devfeed.tech/tags/hardware.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [spotlight](<https://devfeed.tech/tags/spotlight.md>)

### AI overview

This Kubernetes spotlight examines the Device Management Working Group and its work on Dynamic Resource Allocation (DRA), which recently graduated to general availability. The article discusses hardware management requirements for GPUs, TPUs, network interfaces, and other specialized resources, along with limitations of the legacy device model and scheduling challenges.

### Source excerpt

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. Efficiently managing this specialized hardware is the mission of the Device Management Working Group . Their cornerstone project, Dynamic Resource Allocation (DRA) , recently graduated to GA, marking a fundamental shift in how the project handles hardware-intensive workloads at scale. In this spotlight, we sit down with working group chairs Kevin Klues , Patrick Ohly , and John Belamaric to discuss the limitations of the legacy device model, the NP-hard challenges of scheduling, and how they're building a more programmable, hardware-aware future for Kubernetes. Introducing Device Management Natalie Fisher: Can you introduce yourself, your role, and how you got involved in the Device Management Working Group? Kevin Klues: My name is Kevin Klues. I am a Distinguished Engineer at NVIDIA. I have been a co-chair of the device management working group since its inception at Kubecon EU 2024. I have also been involved with DRA (the working group's primary deliverable) since its inception in 2019 / 2020. I have also been a kubelet maintainer since 2019, with a focus on its device manager, CPU manager, and topology manager subcomponents. The challenges we saw with using these components for workloads that relied on external accelerators (e.g., GPUs) are what triggered us to start working on DRA in the first place. Patrick Ohly: I am a Principal Engineer at Intel. In Kubernetes, I am a Tech Lead for SIG Testing and SIG Instrumentation and co-chair of the Device Management WG. I was co-chair of the WG Structured Logging and a member of the Steering Committee. Some of my early contributions to Kubernetes include ephemeral CSI volumes

## Spotlight on SIG Storage

DevFeed: [Spotlight on SIG Storage](<https://devfeed.tech/articles/spotlight-on-sig-storage-17598.md>)

Original publisher: [Read original article](<https://www.kubernetes.dev/blog/2026/06/15/sig-storage-spotlight-2026/>)

Author: The Kubernetes Authors

Published: 2026-06-15T00:00:00Z

Content type: article

Language: en

Sources: [Kubernetes Contributors Blog](<https://devfeed.tech/sources/kubernetes-contributors-blog.md>)

Topics: [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [systems](<https://devfeed.tech/topics/systems.md>), [data](<https://devfeed.tech/topics/data.md>)

Tags: [backups](<https://devfeed.tech/tags/backups.md>), [containers](<https://devfeed.tech/tags/containers.md>), [distributed-system](<https://devfeed.tech/tags/distributed-system.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [storage](<https://devfeed.tech/tags/storage.md>), [volumes](<https://devfeed.tech/tags/volumes.md>)

### AI overview

An interview with Xing Yang, co-chair of Kubernetes SIG Storage, covering the group's role in persistent data and volume management, Kubernetes CSI maintenance, recent storage features, and data protection work such as Volume Group Snapshot and Changed Block Tracking.

### Source excerpt

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 SIG Storage , the group responsible for persistent data, volume management, and the interfaces that connect Kubernetes workloads to the storage systems beneath them. We spoke with Xing Yang , Co-Chair of SIG Storage and Software Engineer at VMware by Broadcom, about the SIG's history, the features shipping in recent Kubernetes releases, and where storage in Kubernetes is headed as AI workloads become the norm. Introductions Could you introduce yourself and share your role(s) within SIG Storage? My name is Xing Yang , a software engineer at VMware by Broadcom. I'm a co-chair in SIG Storage, alongside another co-chair Saad Ali from Google. There are also two Tech Leads in SIG Storage: Michelle Au from Google and Jan Šafránek from Red Hat. What first drew you to storage in Kubernetes, and how did you start contributing? I have always been working in the storage domain, so SIG Storage was a natural place for me to get started when I began to learn Kubernetes. I started attending SIG Storage meetings , trying to figure out what I could do to help. This was before the first Container Storage Interface (CSI) release -- lots of things were still evolving. It was a very exciting time. What subprojects or areas do you actively maintain or review today? I'm a maintainer in Kubernetes CSI. There are multiple CSI sidecars -- such as csi-provisioner, csi-attacher, csi-resizer, and csi-snapshotter -- that we need to release following every Kubernetes release. I'm also a co-chair for a Data Protection Working Group co-sponsored by SIG Storage and SIG Apps . Several features have come out of that WG aimed at filling gaps in data protection support within Kubernetes. One is Volume Group Snapshot , which provides crash-consistent group snapshots for multiple volumes used by an application. Changed Block Tracking (CBT) is another critical feature

## Eliminating Kubernetes Image Signature Replication

DevFeed: [Eliminating Kubernetes Image Signature Replication](<https://devfeed.tech/articles/eliminating-kubernetes-image-signature-replication-17597.md>)

Original publisher: [Read original article](<https://www.kubernetes.dev/blog/2026/06/05/image-signature-routing/>)

Author: The Kubernetes Authors

Published: 2026-06-05T00:00:00Z

Content type: article

Language: en

Sources: [Kubernetes Contributors Blog](<https://devfeed.tech/sources/kubernetes-contributors-blog.md>)

Topics: [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [Replication](<https://devfeed.tech/topics/replication.md>), [container images](<https://devfeed.tech/topics/container-images.md>), [Routing (disambiguation)](<https://devfeed.tech/topics/routing.md>), [Latency](<https://devfeed.tech/topics/latency.md>), [Google](<https://devfeed.tech/topics/google.md>)

Tags: [cloud](<https://devfeed.tech/tags/cloud.md>), [container-images](<https://devfeed.tech/tags/container-images.md>), [cosign](<https://devfeed.tech/tags/cosign.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [latency](<https://devfeed.tech/tags/latency.md>), [manifest](<https://devfeed.tech/tags/manifest.md>), [oidc](<https://devfeed.tech/tags/oidc.md>), [registry](<https://devfeed.tech/tags/registry.md>), [replication](<https://devfeed.tech/tags/replication.md>), [route](<https://devfeed.tech/tags/route.md>), [routing](<https://devfeed.tech/tags/routing.md>), [sha256](<https://devfeed.tech/tags/sha256.md>), [signing](<https://devfeed.tech/tags/signing.md>), [verify](<https://devfeed.tech/tags/verify.md>)

### AI overview

This article explains how Kubernetes eliminated replication of image signatures across 22 regional registries. Because signatures are small and regional latency is negligible, archeio now routes signature requests to a canonical registry while image layers continue using geo-routing.

### Source excerpt

The image promoter rewrite 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. The problem After promoting container images to registry.k8s.io, the promoter signs them using cosign with keyless (OIDC) signatures. These signatures are stored as OCI artifacts alongside the images, tagged with the convention sha256-<digest>.sig and sha256-<digest>.att. The registry.k8s.io domain is backed by archeio , a thin redirector that routes container image requests to the nearest regional Google Artifact Registry backend. When a user in Europe pulls an image, archeio redirects them to europe-west2-docker.pkg.dev; a user in Asia gets redirected to asia-east1-docker.pkg.dev, and so on across 22 regional backends. This geo-routing is great for image layers, where download locality matters for performance. But it created a problem for signatures: if the promoter only wrote a signature to one region, cosign verify would fail for users redirected to any other region. The solution was a dedicated replication pipeline that copied every .sig and .att tag to all 22 regional backends. This pipeline ran as a periodic Prow job every 2 hours on weekdays, performing thousands of API calls per run: listing tags across all repositories, diffing what existed where, and copying the missing signatures. The insight Signatures and attestations are small metadata artifacts, typically a few kilobytes each. Unlike image layers where geo-locality provides meaningful download performance improvements, fetching a signature from a non-local region adds negligible latency. The entire replication pipeline existed to optimize for a latency difference that users would never notice. The solution Instead of replicating signatures everywhere, archeio was taught to route signature req

## Announcing the AI Gateway Working Group

DevFeed: [Announcing the AI Gateway Working Group](<https://devfeed.tech/articles/announcing-the-ai-gateway-working-group-17596.md>)

Original publisher: [Read original article](<https://www.kubernetes.dev/blog/2026/03/09/announcing-ai-gateway-wg/>)

Author: The Kubernetes Authors

Published: 2026-03-09T00:00:00Z

Content type: release

Language: en

Sources: [Kubernetes Contributors Blog](<https://devfeed.tech/sources/kubernetes-contributors-blog.md>)

Topics: [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [Network](<https://devfeed.tech/topics/network.md>), [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [API](<https://devfeed.tech/topics/api.md>)

Tags: [ai-gateway](<https://devfeed.tech/tags/ai-gateway.md>), [ai-infrastructure](<https://devfeed.tech/tags/ai-infrastructure.md>), [anomaly-detection](<https://devfeed.tech/tags/anomaly-detection.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [caching](<https://devfeed.tech/tags/caching.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [networking](<https://devfeed.tech/tags/networking.md>), [payload](<https://devfeed.tech/tags/payload.md>), [prompt-injection](<https://devfeed.tech/tags/prompt-injection.md>), [rag](<https://devfeed.tech/tags/rag.md>), [rate-limiting](<https://devfeed.tech/tags/rate-limiting.md>), [routing](<https://devfeed.tech/tags/routing.md>)

### AI overview

The Kubernetes community has formed the AI Gateway Working Group to develop standards, declarative APIs, and best practices for networking infrastructure that supports AI workloads. The group's proposals address policy enforcement, payload processing, routing, caching, guardrails, and RAG integration.

### Source excerpt

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're excited to announce the formation of the AI Gateway Working Group , a new initiative focused on developing standards and best practices for networking infrastructure that supports AI workloads in Kubernetes environments. What is an AI Gateway? In a Kubernetes context, an AI Gateway refers to network gateway infrastructure (including proxy servers, load-balancers, etc.) that generally implements the Gateway API 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: Token-based rate limiting for AI APIs. Fine-grained access controls for inference APIs. Payload inspection enabling intelligent routing, caching, and guardrails. Support for AI-specific protocols and routing patterns. Working group charter and mission The AI Gateway Working Group operates under a clear charter with the mission to develop proposals for Kubernetes Special Interest Groups (SIGs) and their sub-projects. Its primary goals include: Standards Development: Create declarative APIs, standards, and guidance for AI workload networking in Kubernetes. Community Collaboration: Foster discussions and build consensus around best practices for AI infrastructure. Extensible Architecture: Ensure composability, pluggability, and ordered processing for AI-specific gateway extensions. Standards-Based Approach: Build on established networking foundations, layering AI-specific capabilities on top of proven standards. Active proposals WG AI Gateway currently has several active proposals that address key challenges in AI workload networking: Payload Processing The payload processing proposal addresses the critical need for AI workloads to inspect and transform full HTTP request a

## Spotlight on SIG Architecture: API Governance

DevFeed: [Spotlight on SIG Architecture: API Governance](<https://devfeed.tech/articles/spotlight-on-sig-architecture-api-governance-17595.md>)

Original publisher: [Read original article](<https://www.kubernetes.dev/blog/2026/02/12/sig-architecture-api/>)

Author: The Kubernetes Authors

Published: 2026-02-12T00:00:00Z

Content type: article

Language: en

Sources: [Kubernetes Contributors Blog](<https://devfeed.tech/sources/kubernetes-contributors-blog.md>)

Topics: [API Governance](<https://devfeed.tech/topics/api-governance.md>), [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [API](<https://devfeed.tech/topics/api.md>), [Authentication](<https://devfeed.tech/topics/authentication.md>), [Authorization](<https://devfeed.tech/topics/authorization.md>), [OAuth](<https://devfeed.tech/topics/oauth.md>)

Tags: [api-governance](<https://devfeed.tech/tags/api-governance.md>), [apis](<https://devfeed.tech/tags/apis.md>), [auth](<https://devfeed.tech/tags/auth.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [interview](<https://devfeed.tech/tags/interview.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [spotlight](<https://devfeed.tech/tags/spotlight.md>)

### AI overview

An interview with Jordan Liggitt, lead of Kubernetes SIG Architecture's API Governance sub-project, discusses his work on Kubernetes authentication and authorization and the sub-project's scope. It explains that Kubernetes APIs include REST APIs as well as command-line flags, configuration files, binary execution, backend communication, and data persistence, with goals of stability and continued innovation.

### Source excerpt

This is the fifth interview of a SIG Architecture Spotlight series that covers the different subprojects, and we will be covering SIG Architecture: API Governance . In this SIG Architecture spotlight we talked with Jordan Liggitt , lead of the API Governance sub-project. Introduction FM: Hello Jordan, thank you for your availability. Tell us a bit about yourself, your role and how you got involved in Kubernetes. JL: My name is Jordan Liggitt. I'm a Christian, husband, father of four, software engineer at Google by day, and amateur musician by stealth. I was born in Texas (and still like to claim it as my point of origin), but I've lived in North Carolina for most of my life. I've been working on Kubernetes since 2014. At that time, I was working on authentication and authorization at Red Hat, and my very first pull request to Kubernetes attempted to add an OAuth server to the Kubernetes API server. It never exited work-in-progress status. I ended up going with a different approach that layered on top of the core Kubernetes API server in a different project (spoiler alert: this is foreshadowing), and I closed it without merging six months later. Undeterred by that start, I stayed involved, helped build Kubernetes authentication and authorization capabilities, and got involved in the definition and evolution of the core Kubernetes APIs from early beta APIs, like v1beta3 to v1. I got tagged as an API reviewer in 2016 based on those contributions, and was added as an API approver in 2017. Today, I help lead the API Governance and code organization subprojects for SIG Architecture, and I am a tech lead for SIG Auth. FM: And when did you get specifically involved in the API Governance project? JL: Around 2019. Goals and scope of API Governance FM: How would you describe the main goals and areas of intervention of the subproject? The surface area includes all the various APIs Kubernetes has, and there are APIs that people do not always realize are APIs: command-line flags,

## Announcing the Checkpoint/Restore Working Group

DevFeed: [Announcing the Checkpoint/Restore Working Group](<https://devfeed.tech/articles/announcing-the-checkpoint-restore-working-group-17594.md>)

Original publisher: [Read original article](<https://www.kubernetes.dev/blog/2026/01/21/introducing-checkpoint-restore-wg/>)

Author: The Kubernetes Authors

Published: 2026-01-21T00:00:00Z

Content type: release

Language: en

Sources: [Kubernetes Contributors Blog](<https://devfeed.tech/sources/kubernetes-contributors-blog.md>)

Topics: [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [container](<https://devfeed.tech/topics/container.md>), [migration](<https://devfeed.tech/topics/migration.md>), [distributed-systems](<https://devfeed.tech/topics/distributed-systems.md>), [Security](<https://devfeed.tech/topics/security.md>)

Tags: [announce](<https://devfeed.tech/tags/announce.md>), [container](<https://devfeed.tech/tags/container.md>), [distributed](<https://devfeed.tech/tags/distributed.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [migration](<https://devfeed.tech/tags/migration.md>), [security](<https://devfeed.tech/tags/security.md>)

### AI overview

Kubernetes announces a new Checkpoint/Restore Working Group focused on integrating checkpoint and restore functionality into Kubernetes. The article outlines potential uses including resource optimization, faster application startup, fault tolerance, interruption-aware scheduling, pod migration, and forensic analysis, and describes related CRIU projects and ways to participate.

### Source excerpt

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 Kubernetes Checkpoint Restore WG focusing on the integration of Checkpoint/Restore functionality into Kubernetes. Motivation and use cases There are several high-level scenarios discussed in the working group: Optimizing resource utilization for interactive workloads, such as Jupyter notebooks and AI chatbots Accelerating startup of applications with long initialization times, including Java applications and LLM inference services Using periodic checkpointing to enable fault-tolerance for long-running workloads, such as distributed model training Providing interruption-aware scheduling with transparent checkpoint/restore, allowing lower-priority Pods to be preempted while preserving the runtime state of applications Facilitating Pod migration across nodes for load balancing and maintenance, without disrupting workloads. Enabling forensic checkpointing to investigate and analyze security incidents such as cyberattacks, data breaches, and unauthorized access. 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: CRIU - A tool for checkpointing and restoring running applications and containers checkpointctl - A tool for in-depth analysis of container checkpoints criu-coordinator - A tool for coordinated checkpoint/restore of distributed applications with CRIU checkpoint-restore-operator - A Kubernetes operator for managing checkpoints More information about the checkpoint/restore integration with Kubernetes is also available here . Related events Following our presentation about transparent checkpointing at KubeCon EU 2025, we are excited to w

## Ingress NGINX Retirement: What You Need to Know

DevFeed: [Ingress NGINX Retirement: What You Need to Know](<https://devfeed.tech/articles/ingress-nginx-retirement-what-you-need-to-know-17593.md>)

Original publisher: [Read original article](<https://www.kubernetes.dev/blog/2025/11/12/ingress-nginx-retirement/>)

Author: The Kubernetes Authors

Published: 2025-11-12T17:00:00Z

Content type: release

Language: en

Sources: [Kubernetes Contributors Blog](<https://devfeed.tech/sources/kubernetes-contributors-blog.md>)

Topics: [ingress-nginx](<https://devfeed.tech/topics/ingress-nginx.md>), [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [Security](<https://devfeed.tech/topics/security.md>), [Vulnerabilities](<https://devfeed.tech/topics/vulnerabilities.md>), [Network](<https://devfeed.tech/topics/network.md>)

Tags: [alternatives](<https://devfeed.tech/tags/alternatives.md>), [gateway](<https://devfeed.tech/tags/gateway.md>), [ingress-nginx](<https://devfeed.tech/tags/ingress-nginx.md>), [ingress-nginx-retirement](<https://devfeed.tech/tags/ingress-nginx-retirement.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [releases](<https://devfeed.tech/tags/releases.md>), [security](<https://devfeed.tech/tags/security.md>), [security-vulnerabilities](<https://devfeed.tech/tags/security-vulnerabilities.md>)

### AI overview

Kubernetes SIG Network and the Security Response Committee announce the upcoming retirement of Ingress NGINX. Best-effort maintenance will continue until March 2026; afterward, the project will receive no further releases, bug fixes, or security updates. Existing deployments and installation artifacts will remain available, and users are encouraged to migrate to alternatives such as Gateway API.

### Source excerpt

To prioritize the safety and security of the ecosystem, Kubernetes SIG Network and the Security Response Committee are announcing the upcoming retirement of Ingress NGINX . 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. Existing deployments of Ingress NGINX will continue to function and installation artifacts will remain available. We recommend migrating to one of the many alternatives. Consider migrating to Gateway API , the modern replacement for Ingress. If you must continue using Ingress, many alternative Ingress controllers are listed in the Kubernetes documentation . Continue reading for further information about the history and current state of Ingress NGINX, as well as next steps. About Ingress NGINX Ingress is the original user-friendly way to direct network traffic to workloads running on Kubernetes. (Gateway API is a newer way to achieve many of the same goals.) In order for an Ingress to work in your cluster, there must be an Ingress controller running. There are many Ingress controller choices available, which serve the needs of different users and use cases. Some are cloud-provider specific, while others have more general applicability. Ingress NGINX was an Ingress controller, developed early in the history of the Kubernetes project as an example implementation of the API. It became very popular due to its tremendous flexibility, breadth of features, and independence from any particular cloud or infrastructure provider. Since those days, many other Ingress controllers have been created within the Kubernetes project by community groups, and by cloud native vendors. Ingress NGINX has continued to be one of the most popular, deployed as part of many hosted Kubernetes platforms and within innumerable independent users' clusters. History and Challenges The breadth and flexibility of Ingress NGINX has caused maint

## Announcing the 2025 Steering Committee Election Results

DevFeed: [Announcing the 2025 Steering Committee Election Results](<https://devfeed.tech/articles/announcing-the-2025-steering-committee-election-results-17592.md>)

Original publisher: [Read original article](<https://www.kubernetes.dev/blog/2025/11/09/steering-committee-results-2025/>)

Author: The Kubernetes Authors

Published: 2025-11-09T20:10:00Z

Content type: news

Language: en

Sources: [Kubernetes Contributors Blog](<https://devfeed.tech/sources/kubernetes-contributors-blog.md>)

Topics: [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>)

Tags: [2025](<https://devfeed.tech/tags/2025.md>), [github](<https://devfeed.tech/tags/github.md>), [governance](<https://devfeed.tech/tags/governance.md>), [issue](<https://devfeed.tech/tags/issue.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [project](<https://devfeed.tech/tags/project.md>)

### AI overview

Kubernetes announces the results of its 2025 Steering Committee election. Four new members were elected to two-year terms, joining three continuing members on the seven-seat committee that oversees Kubernetes project governance.

### Source excerpt

The 2025 Steering Committee Election 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. 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 charter . Thank you to everyone who voted in the election; your participation helps support the community's continued health and success. Results Congratulations to the elected committee members whose two year terms begin immediately (listed in alphabetical order by GitHub handle): Kat Cosgrove (@katcosgrove ), Minimus Paco Xu (@pacoxu ), DaoCloud Rita Zhang (@ritazh ), Microsoft Maciej Szulik (@soltysh ), Defense Unicorns They join continuing members: Antonio Ojea (@aojea ), Google Benjamin Elder (@BenTheElder ), Google Sascha Grunert (@saschagrunert ), Red Hat Maciej Szulik and Paco Xu are returning Steering Committee Members. Big thanks! Thank you and congratulations on a successful election to this round's election officers: Christoph Blecker (@cblecker ) Nina Polshakova (@npolshakova ) Sreeram Venkitesh (@sreeram-venkitesh ) Thanks to the Emeritus Steering Committee Members. Your service is appreciated by the community: Stephen Augustus (@justaugustus ), Bloomberg Patrick Ohly (@pohly ), Intel And thank you to all the candidates who came forward to run for election. Get involved with the Steering Committee This governing body, like all of Kubernetes, is open to all. You can follow along with Steering Committee meeting notes and weigh in by filing an issue or creating a PR against their repo . They have an open meeting on the first Wednesday at 8am PT of every month . They can also be contacted at their public mailing list steering@kubernetes.io . You can see what the Steering Committee meetings are all about by watc

## Spotlight on Policy Working Group

DevFeed: [Spotlight on Policy Working Group](<https://devfeed.tech/articles/spotlight-on-policy-working-group-17591.md>)

Original publisher: [Read original article](<https://www.kubernetes.dev/blog/2025/10/18/wg-policy-spotlight-2025/>)

Author: The Kubernetes Authors

Published: 2025-10-18T00:00:00Z

Content type: article

Language: en

Sources: [Kubernetes Contributors Blog](<https://devfeed.tech/sources/kubernetes-contributors-blog.md>)

Topics: [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [Security](<https://devfeed.tech/topics/security.md>), [software-architecture](<https://devfeed.tech/topics/software-architecture.md>), [Kyverno](<https://devfeed.tech/topics/kyverno.md>), [JSON Schema](<https://devfeed.tech/topics/json-schema.md>)

Tags: [architecture](<https://devfeed.tech/tags/architecture.md>), [article](<https://devfeed.tech/tags/article.md>), [blog-post](<https://devfeed.tech/tags/blog-post.md>), [json-schema](<https://devfeed.tech/tags/json-schema.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [kyverno](<https://devfeed.tech/tags/kyverno.md>), [security](<https://devfeed.tech/tags/security.md>)

### AI overview

This retrospective examines the completed Kubernetes Policy Working Group, its goal of developing an overall architecture for current and future policy implementations, and insights from former co-chairs about policy management in the Kubernetes ecosystem.

### Source excerpt

(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.) 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's take a look back at the work of the Policy Working Group. The Policy Working Group was dedicated to a critical mission: providing an overall architecture that encompasses both current policy-related implementations and future policy proposals in Kubernetes. Their goal was both ambitious and essential: to develop a universal policy architecture that benefits developers and end-users alike. Through collaborative methods, this working group strove to bring clarity and consistency to the often complex world of Kubernetes policies. By focusing on both existing implementations and future proposals, they ensured that the policy landscape in Kubernetes remains coherent and accessible as the technology evolves. This blog post dives deeper into the work of the Policy Working Group, guided by insights from its former co-chairs: Jim Bugwadia Poonam Lamba Andy Suderman Interviewed by Arujjwal Negi . These co-chairs explained what the Policy Working Group was all about. Introduction 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? Jim Bugwadia: My name is Jim Bugwadia, and I am a co-founder and the CEO at Nirmata which provides solutions that automate security and compliance for cloud-native workloads. At Nirmata, we have been working with Kubernetes since it started in 2014. We initially built a Kubernetes policy engine in our commercial platform and later donated it to CNCF as the Kyverno project. I joined the CNCF Kubernetes Policy Working Group to h

[Next page](<https://devfeed.tech/sources/kubernetes-contributors-blog.md?cursor=WyIyMDI1LTEwLTE4VDAwOjAwOjAwKzAwOjAwIiwgIjI1MjY2MzBiLTZjYTEtNDllYS04ODE0LWQxNTM2MzdiYmI4NiJd>)