sig-node
Node
139 KEPs31 open findings
SIG Node is responsible for the components that support the controlled interactions between pods and host resources.
Leads
Subprojects
- ci-testing(opens GitHub in a new tab)
- cri-api(opens GitHub in a new tab)
- cri-client(opens GitHub in a new tab)
- cri-streaming(opens GitHub in a new tab)
- cri-tools(opens GitHub in a new tab)
- dra-driver-google-tpu(opens GitHub in a new tab)
- dra-driver-nvidia-gpu(opens GitHub in a new tab)
- kernel-module-management(opens GitHub in a new tab)
- kubelet(opens GitHub in a new tab)
- node-api(opens GitHub in a new tab)
- node-feature-discovery(opens GitHub in a new tab)
- node-problem-detector(opens GitHub in a new tab)
- node-readiness-controller(opens GitHub in a new tab)
- resource-management(opens GitHub in a new tab)
- security profiles merger(opens GitHub in a new tab)
- security-profiles-operator(opens GitHub in a new tab)
- streaming(opens GitHub in a new tab)
KEPs by status
- provisional
- 2
- implementable
- 82
- implemented
- 53
- withdrawn
- 2
Open findings
| KEP | Kind | Disagreement | Detected | Audit |
|---|---|---|---|---|
| KEP-1867 Disable AcceleratorUsage Metrics | active_status_closed_issuekep.yaml says provisional or implementable while the tracking issue is closed. Usually the feature shipped and status was never set to implemented; when a lifecycle bot closed the issue, the status may be right. | kep.yaml status implementable issue #1867 state closed (completed) on 2022-07-29 | 2026-10-18 | both sides |
| KEP-1898 Hardening exec endpoints against SSRF | active_status_closed_issuekep.yaml says provisional or implementable while the tracking issue is closed. Usually the feature shipped and status was never set to implemented; when a lifecycle bot closed the issue, the status may be right. | kep.yaml status implementable issue #1898 state closed (reason not recorded) on 2021-10-08 | 2026-10-18 | both sides |
| KEP-2040 Kubelet CRI support | active_status_closed_issuekep.yaml says provisional or implementable while the tracking issue is closed. Usually the feature shipped and status was never set to implemented; when a lifecycle bot closed the issue, the status may be right. | kep.yaml status implementable issue #2040 state closed (not_planned) on 2024-03-20 | 2026-10-18 | both sides |
| KEP-2053 Downward API HugePages | active_status_closed_issuekep.yaml says provisional or implementable while the tracking issue is closed. Usually the feature shipped and status was never set to implemented; when a lifecycle bot closed the issue, the status may be right. | kep.yaml status implementable issue #2053 state closed (completed) on 2023-04-25 | 2026-10-18 | both sides |
| KEP-2238 Liveness Probe Grace Period | active_status_closed_issuekep.yaml says provisional or implementable while the tracking issue is closed. Usually the feature shipped and status was never set to implemented; when a lifecycle bot closed the issue, the status may be right. | kep.yaml status implementable issue #2238 state closed (not_planned) on 2024-06-15 | 2026-10-18 | both sides |
| KEP-2254 cgroups v2 | active_status_closed_issuekep.yaml says provisional or implementable while the tracking issue is closed. Usually the feature shipped and status was never set to implemented; when a lifecycle bot closed the issue, the status may be right. | kep.yaml status implementable issue #2254 state closed (completed) on 2022-09-12 | 2026-10-18 | both sides |
| KEP-2403 Extend kubelet pod resource assignment endpoint to return allocatable resources | active_status_closed_issuekep.yaml says provisional or implementable while the tracking issue is closed. Usually the feature shipped and status was never set to implemented; when a lifecycle bot closed the issue, the status may be right. | kep.yaml status implementable issue #2403 state closed (completed) on 2023-08-28 | 2026-10-18 | both sides |
| KEP-2413 Seccomp by default | active_status_closed_issuekep.yaml says provisional or implementable while the tracking issue is closed. Usually the feature shipped and status was never set to implemented; when a lifecycle bot closed the issue, the status may be right. | kep.yaml status implementable issue #2413 state closed (completed) on 2023-04-25 | 2026-10-18 | both sides |
| KEP-2902 CPUManager Policy Option to Distribute CPUs Across NUMA Nodes Instead of Packing Them | active_status_closed_issuekep.yaml says provisional or implementable while the tracking issue is closed. Usually the feature shipped and status was never set to implemented; when a lifecycle bot closed the issue, the status may be right. | kep.yaml status implementable issue #2902 state closed (not_planned) on 2025-10-13 | 2026-10-18 | both sides |
| KEP-3288 Split Stdout and Stderr Log Stream of Container | active_status_closed_issuekep.yaml says provisional or implementable while the tracking issue is closed. Usually the feature shipped and status was never set to implemented; when a lifecycle bot closed the issue, the status may be right. | kep.yaml status implementable issue #3288 state closed (not_planned) on 2026-03-05 | 2026-10-18 | both sides |
| KEP-3327 CPUManager policy option to align CPUs by Socket instead of by NUMA node | active_status_closed_issuekep.yaml says provisional or implementable while the tracking issue is closed. Usually the feature shipped and status was never set to implemented; when a lifecycle bot closed the issue, the status may be right. | kep.yaml status implementable issue #3327 state closed (not_planned) on 2024-12-20 | 2026-10-18 | both sides |
| KEP-4176 New CPUManager Static Policy which spread hyperthreads across physical CPUs to better utilize CPU Cache | active_status_closed_issuekep.yaml says provisional or implementable while the tracking issue is closed. Usually the feature shipped and status was never set to implemented; when a lifecycle bot closed the issue, the status may be right. | kep.yaml status implementable issue #4176 state closed (not_planned) on 2025-12-13 | 2026-10-18 | both sides |
| KEP-4191 Split Image Filesystem | active_status_closed_issuekep.yaml says provisional or implementable while the tracking issue is closed. Usually the feature shipped and status was never set to implemented; when a lifecycle bot closed the issue, the status may be right. | kep.yaml status implementable issue #4191 state closed (not_planned) on 2026-10-17 | 2026-10-18 | both sides |
| KEP-4580 Deprecate & remove Kubelet RunOnce mode | active_status_closed_issuekep.yaml says provisional or implementable while the tracking issue is closed. Usually the feature shipped and status was never set to implemented; when a lifecycle bot closed the issue, the status may be right. | kep.yaml status provisional issue #4580 state closed (completed) on 2024-07-24 | 2026-10-18 | both sides |
| KEP-4800 Split UnCoreCache Toplogy Awareness in CPU Manager | active_status_closed_issuekep.yaml says provisional or implementable while the tracking issue is closed. Usually the feature shipped and status was never set to implemented; when a lifecycle bot closed the issue, the status may be right. | kep.yaml status implementable issue #4800 state closed (completed) on 2025-01-31 | 2026-10-18 | both sides |
| KEP-5328 Node Declared Features | active_status_closed_issuekep.yaml says provisional or implementable while the tracking issue is closed. Usually the feature shipped and status was never set to implemented; when a lifecycle bot closed the issue, the status may be right. | kep.yaml status implementable issue #5328 state closed (completed) on 2026-10-12 | 2026-10-18 | both sides |
| KEP-5593 Configure the max CrashLoopBackOff delay | active_status_closed_issuekep.yaml says provisional or implementable while the tracking issue is closed. Usually the feature shipped and status was never set to implemented; when a lifecycle bot closed the issue, the status may be right. | kep.yaml status implementable issue #5593 state closed (not_planned) on 2026-06-20 | 2026-10-18 | both sides |
| KEP-606 Kubelet endpoint for device assignment observation details | active_status_closed_issuekep.yaml says provisional or implementable while the tracking issue is closed. Usually the feature shipped and status was never set to implemented; when a lifecycle bot closed the issue, the status may be right. | kep.yaml status implementable issue #606 state closed (completed) on 2023-08-28 | 2026-10-18 | both sides |
| KEP-6072 DRA: Standard numaNode Device Attribute | active_status_closed_issuekep.yaml says provisional or implementable while the tracking issue is closed. Usually the feature shipped and status was never set to implemented; when a lifecycle bot closed the issue, the status may be right. | kep.yaml status implementable issue #6072 state closed (completed) on 2026-08-18 | 2026-10-18 | both sides |
| KEP-793 Promote Node Operating System & Architecture labels to GA | active_status_closed_issuekep.yaml says provisional or implementable while the tracking issue is closed. Usually the feature shipped and status was never set to implemented; when a lifecycle bot closed the issue, the status may be right. | kep.yaml status implementable issue #793 state closed (reason not recorded) on 2019-04-11 | 2026-10-18 | both sides |
| KEP-1797 Configure FQDN as Hostname for Pods | milestone_mismatchThe latest milestone in kep.yaml differs from the milestone of the tracking issue. | kep.yaml latest-milestone v1.22 issue #1797 milestone v1.25 (issue closed) | 2026-10-18 | both sides |
| KEP-2727 Add gRPC probe to Pod.Spec.Container.{Liveness,Readiness,Startup}Probe | milestone_mismatchThe latest milestone in kep.yaml differs from the milestone of the tracking issue. | kep.yaml latest-milestone v1.27 issue #2727 milestone v1.29 (issue closed) | 2026-10-18 | both sides |
| KEP-4033 Discover cgroup driver from CRI | milestone_mismatchThe latest milestone in kep.yaml differs from the milestone of the tracking issue. | kep.yaml latest-milestone v1.37 issue #4033 milestone v1.34 (issue closed) | 2026-10-18 | both sides |
| KEP-4438 Restarting sidecar containers during Pod termination | milestone_mismatchThe latest milestone in kep.yaml differs from the milestone of the tracking issue. | kep.yaml latest-milestone v1.37 issue #4438 milestone v1.38 (issue open) | 2026-10-18 | both sides |
| KEP-6063 Per-Pod PID Limit | milestone_mismatchThe latest milestone in kep.yaml differs from the milestone of the tracking issue. | kep.yaml latest-milestone v1.37 issue #6063 milestone v1.38 (issue open) | 2026-10-18 | both sides |
| KEP-2040 Kubelet CRI support | stage_mismatchThe stage in kep.yaml is not among the stage labels of the closed tracking issue. | kep.yaml stage beta issue #2040 stage label (closed) stage/alpha | 2026-10-18 | both sides |
| KEP-3085 Pod networking ready condition | stage_mismatchThe stage in kep.yaml is not among the stage labels of the closed tracking issue. | kep.yaml stage stable issue #3085 stage label (closed) stage/beta | 2026-10-18 | both sides |
| KEP-4800 Split UnCoreCache Toplogy Awareness in CPU Manager | stage_mismatchThe stage in kep.yaml is not among the stage labels of the closed tracking issue. | kep.yaml stage stable issue #4800 stage label (closed) stage/beta | 2026-10-18 | both sides |
| KEP-5067 Pod Generation | stage_mismatchThe stage in kep.yaml is not among the stage labels of the closed tracking issue. | kep.yaml stage stable issue #5067 stage label (closed) stage/beta | 2026-10-18 | both sides |
| KEP-793 Promote Node Operating System & Architecture labels to GA | stage_mismatchThe stage in kep.yaml is not among the stage labels of the closed tracking issue. | kep.yaml stage alpha issue #793 stage label (closed) stage/stable | 2026-10-18 | both sides |
| KEP-5978 DRA: ClusterResourceClaimTemplate | terminal_status_future_targetskep.yaml says withdrawn, rejected, deferred or replaced, but the KEP still targets a future release or is still tracked for one. | kep.yaml status withdrawn kep.yaml future targets milestone.beta = v1.38; milestone.stable = v1.40 | 2026-10-18 | both sides |
KEPs
139 KEPs owned by sig-node; click a header to sort.Showing 1–10 of 139
| KEP-24 | Add AppArmor Support | implementable | stable | v1.34 | 0 |
| KEP-34 | Protomote sysctl annotations to fields | implemented | stable | v1.21 | 0 |
| KEP-127 | Support User Namespaces | implemented | stable | v1.36 | 0 |
| KEP-135 | Seccomp to GA | implemented | stable | none | 0 |
| KEP-166 | Promote Taint Based Evictions to GA | implemented | stable | none | 0 |
| KEP-213 | RunAsGroup support in PodSpec and PodSecurityPolicy | implemented | stable | v1.21 | 0 |
| KEP-277 | Ephemeral Containers | implemented | stable | v1.25 | 0 |
| KEP-281 | Dynamic Kubelet Configuration | implemented | removed | v1.26 | 0 |
| KEP-495 | Shared PID Namespace | implemented | stable | none | 0 |
| KEP-585 | Runtime Class | implemented | stable | v1.20 | 0 |
People
242 people with a role on this SIG or its KEPs, most roles first.Showing 1–10 of 242
| Person | Roles |
|---|---|
| @mrunalp | chairtech_leadauthorreviewerapprover |
| @derekwaynecarr | tech_leadauthorreviewerapprover |
| @haircommander | chairauthorreviewerapprover |
| @sergeykanzhelev | chairauthorreviewerapprover |
| @dashpole | authorreviewerapprover |
| @dchen1107 | tech_leadreviewerapprover |
| @ehashman | authorreviewerprr_approver |
| @ffromani | authorreviewerapprover |
| @harche | authorreviewerapprover |
| @johnbelamaric | reviewerapproverprr_approver |