sig-node

+1 from me: it already has approval. cc'ing new SIG release email On Wednesday, March 18, 2026,

Hi all, We are announcing the release of Node Readiness Controller v0.3.0. This release focuses on

+1 from sig-node. On Thu, Mar 19, 2026 at 12:03 PM 'Jose Valdes' via sig-node <sig-node@

+1 from sig-node. On Thu, Mar 19, 2026 at 12:43 AM Narang Dixita Sohanlal <ndi...@gmail.com>

Hi, I am reaching out to request for an exception for the following: Enhancement name: Allow

Hi, I am requesting a code freeze exception to allow for the following feature enhancements. Details

+1 this is really helpful for troubleshooting and understanding resource availability and has most of

+1 from sig-node. On Wed, Mar 18, 2026 at 11:24 AM Patrick Ohly <patric...@intel.com> wrote:

+1 here from sig-arch, also added to the issue On Fri, Mar 6, 2026 at 6:54 AM Davanum Srinivas <

Hi all, We are pleased to announce the release of Node Readiness Controller v0.2.0. This release

+1 (non-binding). This project brings the upstream Kubernetes to the next level of enabling AI

Hi, Welcome! Here is how to add items to agenda: https://docs.google.com/document/d/1fb-

As discussed in the Slack thread[0], the PR did not make for the extended deadline of end of day

Hi all, Unfortunately, the release team is REJECTING this exception request. As mentioned in the

Thank you for the great work! This WG achieved very impressive results, kudos to all contributors and

Hi all, The release team is APPROVING this exception request for KEP-4563 based on the discussion in

Hi, Thanks for the great question. This touches on one of the core design goals of the project. To

We typically do not update old blog posts unless the information there is misleading or harmful. And

Hi SIG Node contributors, Just a quick reminder that the volunteer sign-up form for SIG Node v1.36

The Declarative Node Maintenance KEP (https://github.com/kubernetes/enhancements/pull/4213) aimed to

Hey folks! It's that time of the release when we're searching for volunteers to be KEP

One more update: per community guidelines, we've added a password, so the new link with password

Thanks for bringing this up. sig-storage is actively working to find best way to move forward with

---------- Forwarded message --------- From: Drew Hagen <drewha...@gmail.com> Date: Tuesday,

Thank you all for participating in the summit on Monday. I found it really useful and hope others did

---------- Forwarded message --------- From: drew.a...@gmail.com <drew.a...@gmail.com> Date:

---------- Forwarded message --------- From: Drew Hagen <drewha...@gmail.com> Date: Monday,

---------- Forwarded message --------- From: drew.a...@gmail.com <drew.a...@gmail.com> Date:

---------- Forwarded message --------- From: drew.a...@gmail.com <drew.a...@gmail.com> Date:

---------- Forwarded message --------- From: drew.a...@gmail.com <drew.a...@gmail.com> Date: