Weekly GitHub Report for Kubernetes

Thank you for subscribing to our weekly newsletter! Each week, we deliver a comprehensive summary of your GitHub project's latest activity right to your inbox, including an overview of your project's issues, pull requests, contributors, and commit activity.

Table of Contents

• I. News
  • 1.1. Recent Version Releases
  • 1.2. Other Noteworthy Updates
• II. Issues
  • 2.1. Top 5 Active Issues
  • 2.2. Top 5 Stale Issues
  • 2.3. Open Issues
  • 2.4. Closed Issues
  • 2.5. Issue Discussion Insights

• III. Pull Requests
  • 3.1. Open Pull Requests
  • 3.2. Closed Pull Requests
  • 3.3. Pull Request Discussion Insights

• IV. Contributors
  • 4.1. Contributors

I. News

1.1 Recent Version Releases:

The current version of this repository is v1.32.3

1.2 Version Information:

The Kubernetes version released on March 11, 2025, introduces key updates detailed in the official CHANGELOG, with additional binary downloads available. For comprehensive information on new features and changes, users are encouraged to consult the Kubernetes announce forum and the linked CHANGELOG.

II. Issues

2.1 Top 5 Active Issues:

We consider active issues to be issues that that have been commented on most frequently within the last week. Bot comments are omitted.

1. [KIND/FAILING-TEST] [NEEDS-TRIAGE] [SIG/K8S-INFRA] [Failing Test] ci-kubernetes-e2e-capz-master-windows: This issue concerns a failing continuous integration test job for Kubernetes on Windows using the Cluster API Provider for Azure (CAPZ), caused by the retirement of AKS version 1.33.5 from standard support, which leads to a setup failure when creating the management cluster. The failure is due to an external infrastructure change rather than a Kubernetes code regression, and the fix requires updating the AKS management cluster version in the CAPZ and windows-testing repositories to a currently supported version.

   • The comments detail the triage process identifying the root cause as an AKS version deprecation, confirm no Kubernetes code changes caused the failure, and discuss the successful fix via a pull request to windows-testing that restored the CI job, though some new test failures appeared afterward, prompting further investigation and planned updates to test images and code.
   • Number of comments this week: 8

2. [KIND/BUG] [PRIORITY/BACKLOG] [SIG/NODE] [TRIAGE/ACCEPTED] Memory Manager pod scope drops hugepage requests used only by regular init containers: This issue addresses a problem in the static Memory Manager with pod-level Topology Manager scope where memory resource requests made exclusively by regular init containers, specifically hugepage requests, are dropped from the pod's aggregated resource calculation. This omission leads to inaccurate topology hints and NUMA machine state accounting, causing the system to under-reserve hugepage capacity, and the expected behavior is for all managed resources requested by any container type to be included in the pod's resource calculation.

   • The comments acknowledge the legitimacy of the issue and discuss its relation to a broader, older problem of resource release after init containers complete; they agree the fix is correct but caution that it may expose existing "lost resource" cases, recommending careful evaluation and documentation of the behavior change without rushing the fix.
   • Number of comments this week: 6

3. [SIG/NODE] [KIND/FEATURE] [TRIAGE/ACCEPTED] [WG/DEVICE-MANAGEMENT] DRA resource health: remove v1alpha1 gRPC API: This issue requests the removal of the deprecated v1alpha1 gRPC API for DRA resource health in version 1.40, following its replacement by the v1 API in an earlier release. The goal is to complete the deprecation process of this beta API as planned in the Kubernetes project roadmap.

   • The comments include initial tagging and assignment commands, followed by a request from a contributor to work on the issue, which is deferred until closer to the 1.40 release, with acknowledgment of this timeline.
   • Number of comments this week: 6

4. [SIG/SCHEDULING] [NEEDS-TRIAGE] [WG/DEVICE-MANAGEMENT] DRA: List Types for Attributes - hoist the calculations / rationale for max lengths into a more permanent doc location, add unit test exercising every field/list dimension at its max: This issue discusses consolidating the calculations and rationale for maximum lengths of list-type attributes in device resource management into a more permanent documentation location, along with adding a unit test that exercises every field and list dimension at its maximum. It aims to clarify and maintain the validation of these limits across various feature gate scenarios and ensure comprehensive test coverage for maximal size objects.

   • The comments include a detailed summary of current max-length limits and test coverage for different feature gate scenarios, a note that some prior discussions are now obsolete due to decisions to reduce device counts when advanced features are enabled, and references to ongoing pull requests that simplify and update the integration tests and documentation accordingly.
   • Number of comments this week: 5

5. [SIG/STORAGE] [SIG/NODE] [KIND/FLAKE] [NEEDS-TRIAGE] [Flaky Test] [sig-node] k8s.io/kubernetes/pkg/kubelet/volumemanager reconciler: This issue reports a flaky unit test in the Kubernetes kubelet volumemanager reconciler, where a timing-dependent race causes the test to fail waiting for a pod volume to unmount after a failed setup. The failure is due to the test issuing single reconcile calls without retrying, causing the unmount operation to be gated behind a backoff period and never retried, which is a known long-standing flake unrelated to recent code changes.

   • The comments confirm the flake is a test-harness timing race rather than a product regression, clarify the gating mechanism involves an operationPending check rather than just a backoff, and suggest a test-only fix to wait for the mount operation to complete before retrying the unmount reconcile, with agreement to re-home the issue to sig/storage and deduplicate with a prior similar flake.
   • Number of comments this week: 5

2.2 Top 5 Stale Issues:

We consider stale issues to be issues that has had no activity within the last 30 days. The team should work together to get these issues resolved and closed as soon as possible.

As of our latest update, there are no stale issues for the project this week.

2.3 Open Issues

This section lists, groups, and then summarizes issues that were created within the last week in the repository.

Issues Opened This Week: 52

Summarized Issues:

• Flaky and Timing-Dependent Tests: Several issues report flaky or timing-dependent test failures across different components, including scheduler performance tests, Windows CI tests, kubetest.Up, and kubelet volumemanager reconciler. These flakes are caused by race conditions, mutex contention, timing assumptions, or environment changes, leading to intermittent failures that complicate CI reliability and test stability.
• issues/140751, issues/140752, issues/140760, issues/140762, issues/140823, issues/140924

• Resource Allocation and Device Management Bugs: Multiple issues describe bugs in the Device Resource Allocation (DRA) system and dynamic resource allocator, including incorrect device allocation due to shared allocation flags, over-commitment of device counters, and improper overhead accounting for init containers. These bugs cause resource misaccounting, invalid states, and potential pod admission failures.
• issues/140797, issues/140799, issues/140802, issues/140812

• Pod and Container Resource Calculation Issues: Several problems affect pod resource limit calculations, including kubelet treating missing container limits as zero, Memory Manager omitting hugepage requests from init containers, and duplicate memory reservations after kubelet restarts. These issues lead to inaccurate resource configurations and potential pod admission or scheduling problems.
• issues/140810, issues/140814, issues/140906

• Health and Status Reporting Problems in DRA and Plugins: Issues report problems with device health reporting in DRA, including stale or overwritten health states during plugin upgrades and delayed PodStatus updates when device health-check deadlines expire. These cause inaccurate or missing health information and status transitions for affected pods.
• issues/140818, issues/140819

• Windows-Specific Failures and Environment Issues: Several issues describe Windows CI failures caused by environment changes such as Azure VM image updates, Windows Update errors blocking OpenSSH installation, and deprecated AKS management cluster versions causing setup failures. These environment-related problems lead to persistent test failures and blocked merges.
• issues/140777, issues/140869, issues/140900

• Scheduler and Preemption Feature Enhancements and Flakes: Issues cover feature promotion and flakiness in workload-aware preemption and vertical scaling scheduler preemption, including defining metrics, handling preemption timing, and fixing partial pod group preemption failures. These affect scheduling correctness and feature readiness.
• issues/140854, issues/140893, issues/140863

• Kubelet Performance and Configuration Validation: Problems include kubelet's serialized pod status sync bottleneck under high churn and the need to enhance CPU and Topology Manager policy validation to support Kubernetes version emulation. These issues impact kubelet scalability and configuration compatibility during upgrades.
• issues/140936, issues/140937

• API Server and Control Plane Bugs: Several issues describe API server panics due to queue management bugs, hanging requests caused by grpc-go transport recycling, and incorrect use of "not found" getters in the generic control plane. These bugs cause crashes, request delays, and control plane inconsistencies.
• issues/140884, issues/140911, issues/140857

• Job and StatefulSet Controller Bugs: Issues include duplicate pod creation caused by annotation changes in Indexed Jobs and inability to scale down StatefulSets after failed scale-up attempts due to resource quota issues. These bugs lead to improper job execution and stuck scaling operations.
• issues/140839, issues/140858

• Networking and DNS Issues: Problems include kubelet copying invalid IPv6 link-local scoped nameservers into pods causing DNS failures, and kube-proxy crashing with segmentation faults in nftables mode on EKS with Bottlerocket OS, leading to service traffic failures.
• issues/140844, issues/140898

• Feature Gate and API Deprecation Management: Issues cover the removal of deprecated v1alpha1 DRA resource health API, reintroduction of admissioninitializer interface for backward compatibility, and feature gate misconfiguration causing API server startup failures. These affect API stability and backward compatibility.
• issues/140838, issues/140915, issues/140813

• Kubectl Command Bugs and Enhancements: Issues include client-side validation bugs in kubectl create ingress causing silent TLS drops, impersonation permission checks expanding to overlapping CRDs incorrectly, and requests for improved debug output formatting in kubectl auth can-i. These affect CLI correctness and usability.
• issues/140922, issues/140961, issues/140962

• Test Suite Flakiness and Timeout Issues: Several test suites experience intermittent timeouts and flakiness due to resource exhaustion, test growth, or flaky test assumptions, affecting node conformance, CRI-O kubelet serial tests, and image pull credential tests. These reduce CI reliability and require test or infrastructure improvements.
• issues/140942, issues/140943, issues/140944

• Horizontal Pod Autoscaler Metric Calculation Bug: The HPA controller encounters an integer underflow error when scaling replicas down to zero, causing invalid metric target values and stuck status conditions. This bug disrupts autoscaling behavior.
• issues/140956

• EventSeries Metadata Annotation Missing: The EventSeries type lacks the atomic struct annotation, causing invalid field names in Elasticsearch/OpenSearch ingestion pipelines and resulting in batch rejections of event data. This breaks observability integrations.
• issues/140957

• API Server Routing Bug: The PathRecorderMux.Handle method incorrectly routes nested endpoint requests, resulting in 404 errors and requiring use of HandlePrefix to fix routing behavior.
• issues/140832

• Deprecated Badge Removal: The Go Report Card badge in the README is outdated and should be removed as the service is retired and the badge no longer links to meaningful reports.
• issues/140940

2.4 Closed Issues

This section lists, groups, and then summarizes issues that were closed within the last week in the repository. This section also links the associated pull requests if applicable.

Issues Closed This Week: 51

Summarized Issues:

• Security Context and Privilege Escalation Issues: Several issues highlight problems with Kubernetes security context validations, including incorrect checks that allow unintended privileges when allowPrivilegeEscalation: false is combined with certain capabilities, and incomplete blocking of dangerous capabilities leading to false security assurances. These issues expose containers to privilege escalation risks due to validation bugs and propose extending checks to cover all relevant capabilities properly.
• issues/119568, issues/131336

• Dynamic Resource Allocation (DRA) Reliability and Validation: Multiple issues address improving DRA driver reliability through sanity checks during device allocation, adding declarative validation for device metadata, fixing bugs causing duplicate device allocations or checkpoint growth, and promoting the DRAResourceHealth API to beta. These efforts aim to prevent race conditions, resource leaks, and improve validation to ensure consistent and correct resource management.
• issues/128981, issues/137761, issues/139475, issues/140433, issues/140441, issues/140471

• Pod Scheduling and ResourceClaim Conflicts: Issues describe race conditions and concurrency problems during pod scheduling with DRA, including duplicate ResourceClaims creation, conflicts in PreBind plugins, and unbounded goroutine growth due to event recording under throttling. These problems cause scheduling instability, timeouts, and resource inconsistencies, with mitigations involving concurrency reduction and improved event handling.
• issues/139555, issues/140217, issues/140393

• Flaky and Failing Tests in Various Components: Several issues report flaky or failing tests across Kubernetes components such as integration tests, unit tests, and end-to-end tests caused by timing issues, deadlocks, race conditions, environment misconfigurations, and non-deterministic behaviors. These failures reduce test reliability and require fixes including timeout extensions, state isolation, and improved error handling.
• issues/137207, issues/138608, issues/140815, issues/140822, issues/140870, issues/140875, [issues/140901](https://github.com/issues/140901]

• Kubelet and Pod Lifecycle Bugs: Issues include kubelet incorrectly starting multiple containers for static pods, failure to restart init containers after node reboot due to misinterpreted container states, and CSI PluginWatcher goroutine remaining idle causing driver registration failures. These bugs cause pod startup failures, stuck pod states, and driver registration issues impacting node stability and pod lifecycle management.
• issues/123087, issues/137710, issues/140754

• API Server and Logging Inconsistencies: Problems include incorrect HTTP verb logging for watch requests and missing field selectors for ResourceSlice filtering, leading to confusing logs and limited API filtering capabilities. These issues affect observability and client-side resource querying precision.
• issues/130373, issues/137413

• Scheduler Performance and Validation Issues: The scheduler suffers from performance bottlenecks due to expensive full scans on ResourceClaim events and lacks comprehensive validation in scheduler-perf operations, causing unclear errors and inefficient CPU usage. Proposed solutions include optimizing event handling and adding stricter validation to improve scheduler reliability and performance.
• issues/132679, issues/138095

• Pod Quality of Service (QOS) Classification Bug: An inconsistency in pod-level resource evaluation causes incorrect QOS class assignments by failing to distinguish between nil and empty resource specifications, potentially breaking assumptions in resource accounting and leading to misclassified pods.
• issues/135082

• ResourceSlice Validation Panic: A panic occurs due to an integer divide by zero error in ResourceSlice validation caused by mismatched Quantity methods, leading to improper arithmetic and validation failures.
• issues/140472

• Pod Resize and Container Event Notification: Issues highlight the need for container event notifications to support in-place pod resizing and report test failures due to insufficient node memory causing pod resize timeouts, indicating gaps in event handling and resource availability for resizing operations.
• issues/131112, issues/140640

• Code Generation and Tag Handling Policy: There is a need to establish a consistent policy for handling unrecognized +k8s: tags in code generators like validation-gen, balancing strictness and backward compatibility to avoid build or validation issues.
• issues/130455

• Module Management and Build Independence: Proposal to move the k8s.io/cri-api module out of staging to resolve versioning conflicts and enable independent building and management, requiring changes in publishing, tagging, ownership, and CI setup.
• issues/131539

• Localhost NodePort Support Challenges: Discussion on enabling localhost NodePorts to support local registries by exploring fallback proxying methods and networking hacks to overcome limitations in existing proxy implementations without relying on problematic techniques.
• issues/132955

• Goroutine Leaks in Core Components: Two issues describe goroutine leaks caused by blocked channel receives and select statements without selectable cases in core Kubernetes components, leading to resource leaks detectable by goleak.
• issues/134322, issues/134323

• PodGroup Scheduling and Ordering Flakiness: Non-deterministic pod ordering due to Go map iteration order causes flaky scheduling tests on Windows, leading to incorrect scheduling results and test failures.
• issues/140420

• Structured Allocator Bugs: Bugs in the structured allocator cause double-counting of shared device allocations and integer overflow in capacity rounding, resulting in false insufficient resource errors and corrupted allocation tracking.
• issues/140433, issues/140441

• PodGroupPostFilter Extension for DRA: Proposal to add a podGroupPostFilter method to maintain existing DRA behavior after introducing the PodGroupPostFilter extension point in workload-aware scheduling.
• issues/140534

• Scalability Testing Pre-submit Checks: Proposal to add pre-submit scalability tests for the kubernetes-sigs/agent-sandbox repository to catch regressions early and improve feedback by running tests under different load scenarios integrated with TestGrid.
• issues/140750

• PodCertificate Manager Deadlock: Flaky test failures caused by deadlocks in the podcertificate manager due to delayed credential returns, impacting test reliability.
• issues/140822

• Feature Gate Regression Causing Kubelet Panics: Regression where enabling the PodLevelResourcesFixDefaulting feature gate without the PodLevelResources gate causes kubelet startup panics and test failures due to configuration merge issues.
• issues/140848

• Windows CI Test Timeout Due to Resource Constraints: Flaky Windows CI test failures caused by polling deadlines exceeded on underpowered Azure VMs running multiple concurrent tests, requiring timeout extensions to improve stability.
• issues/140870

• Pod Startup Latency Regression on AWS DRA Jobs: Increased pod startup latency traced to a regression affecting pod scheduling times, fixed by reverting changes and adjusting cache sizes to restore performance.
• issues/140877

• Alpha Feature Gate Dependency Failures: Alpha containerd jobs fail due to enabling alpha feature gates dependent on a beta feature that is disabled by default, causing initialization errors and test failures.
• issues/140887

• End-to-End Test Framework Flakiness and Cleanup Issues: Multiple sources of flakiness and silent failures in the e2e test framework include error suppression hiding leaks, lack of retries on transient errors, premature readiness checks, improper goroutine shutdown, and race conditions in PVC deletion, with fixes improving reliability.
• issues/140901

• Untested API Endpoint Detection: A failing conformance test detects an untested API endpoint getLifecycleAPIGroup, identifying it as a duplicate of a previously reported issue and highlighting gaps in API test coverage.
• issues/140923

• Pod Secret File Ownership Support: Kubernetes currently lacks support for setting file ownership (UID and GID) on mounted secret files, complicating secure access by non-root users and multiple container processes. This limitation affects software that enforces strict ownership and permission checks on secret files.
• issues/81089

• Kubectl Apply Field Persistence Behavior: Documentation is needed to clarify that fields like serviceAccountName and serviceAccount may persist unexpectedly after deletion and re-application due to how kubectl apply manages resource state, causing confusion about field removal.
• issues/82525

• Disruption Controller Worker Configuration: The disruption controller's fixed number of workers causes overload and syncing delays when managing many Pod Disruption Budgets, impairing eviction handling and causing status lag, suggesting the need for configurable worker counts.
• issues/82930

2.5 Issue Discussion Insights

This section will analyze the tone and sentiment of discussions within this project's open and closed issues that occurred within the past week. It aims to identify potentially heated exchanges and to maintain a constructive project environment.

Based on our analysis, there are no instances of toxic discussions in the project's open or closed issues from the past week.

III. Pull Requests

3.1 Open Pull Requests

This section provides a summary of pull requests that were opened in the repository over the past week. The top three pull requests with the highest number of commits are highlighted as 'key' pull requests. Other pull requests are grouped based on similar characteristics for easier analysis. Up to 25 pull requests are displayed in this section, while any remaining pull requests beyond this limit are omitted for brevity.

Pull Requests Opened This Week: 102

Key Open Pull Requests

1. test: add conformance coverage for EvictionRequest: This pull request adds comprehensive end-to-end conformance test coverage for the EvictionRequest API in Kubernetes, verifying all key resource operations such as create, get, list, watch, patch, update, status updates, and deletion to ensure compliance with GA API requirements.

• URL: pull/140897

• Associated Commits: 3ce50, 6d7d6, 3d1f3, 2710e, 11d31, 9d830, 45ee7, 19d41, c3866

2. [WIP] testing scale: This pull request is focused on testing and improving the scalability of the Kubernetes watch dispatch system by adding detailed metrics, probes, and optimizations such as stage-specific fan-out cost isolation, latency measurements, stall detection, batching enhancements, and adjustments to channel sizes to better monitor and enhance watch performance.

• URL: pull/140861

• Associated Commits: 123db, 9c586, 8195c, 3be88, bf1d7, acfc5, 55154, 38ab2

3. [DRAFT][FG: InPlacePodVerticalScalingExclusiveCPUs] Preparation policy static for 5554 4 granular commits: This pull request prepares the static policy components for integrating in-place pod vertical scaling with exclusive CPU allocation by modifying only policy_static.go and policy_static_test.go files, supporting the new CPU allocation logic that handles resizing operations while preserving CPU topology and allocation locality, and is gated behind the InPlacePodVerticalScalingExclusiveCPUs feature to avoid impacting the stable pod admission path.

• URL: pull/140775

• Associated Commits: 4d6f5, d198d, b4925, b6d1a, fa585

Other Open Pull Requests

• Version and Release Updates: This topic includes updates to the hard-coded DefaultKubeBinaryVersion to 1.38 in preparation for the new minor release and fixes to the Kubernetes 1.34 release branch by addressing gomock errors and upgrading the Go version to 1.26.5. These changes ensure compatibility and stability while cleaning up obsolete test cases and deprecated API scenarios.
  [pull/140764, pull/140919]

• Logging and Error Handling Improvements: Pull requests in this topic reduce log noise by downgrading the log level for expected websocket closure errors and improve strategic merge patch error messages in kubectl by explicitly indicating missing merge key fields. These fixes enhance user experience by preventing misleading logs and providing clearer error context.
  [pull/140794, pull/140771]

• Controller and Informer API Migration: This topic covers migration of controllers in the pkg/controller package to use the typed informer API, replacing untyped handlers with generated typed interfaces to improve type safety and clarity. The migration maintains some dynamic registrations where necessary to balance safety and flexibility.
  [pull/140776]

• Pod Resource and Kubelet Bug Fixes: These pull requests fix bugs related to pod overhead in fallback resource requests, device manager allocation for zero-valued device-plugin requests, and static Memory Manager resource request calculations including init containers. The fixes ensure accurate resource accounting and prevent pod rejection due to allocation errors.
  [pull/140809, pull/140791, pull/140816]

• Device Resource Allocation and Health Management: This topic fixes the kubelet Device Resource Allocation plugin manager by ensuring only the authoritative device health stream updates the health cache during plugin upgrades, preventing stale endpoints from overwriting active health states and refreshing Pod status accordingly.
  [pull/140842]

• OOM Kill Counter Test Coverage: This pull request adds end-to-end test coverage for containers with stale, non-zero cumulative oom_kill counters that later exit normally, complementing prior fixes by validating this scenario beyond unit tests.
  [pull/140867]

• OpenAPI Endpoint Optimization: Two alpha feature gates, OpenAPIV2BytesCache and OpenAPIV2LazyBuild, optimize the /openapi/v2 endpoint by caching marshaled JSON bytes with ETags and lazily building the specification on first request, respectively. These changes reduce memory usage while maintaining byte-identical responses and backward compatibility.
  [pull/140927, pull/140939]

• Autoscaling and Scheduler Metrics Enhancements: This topic fixes an autoscaling bug by skipping per-pod metric division when replicas are zero to prevent errors and extends the Kubernetes scheduler's MetricAsyncRecorder to asynchronously record incoming queue metrics across all scheduling queue implementations. These improvements enhance stability and observability.
  [pull/140958, pull/140753]

• Scheduler Metrics Documentation: This pull request documents the profile label in all kube-scheduler metrics help text and cleans up existing metric descriptions for clarity and accuracy, improving discoverability for users.
  [pull/140800]

• IssuingManager Deadlock Fix: This pull request resolves a goroutine deadlock in the IssuingManager by adding WaitGroup tracking and context cancellation observation to ensure proper graceful shutdown and responsiveness to cancellation signals.
  [pull/140855]

• Finalizer Validation on ObjectMeta Updates: This pull request adds missing validation for finalizers during ObjectMeta updates to ensure malformed and conflicting finalizers are properly checked, maintaining consistency and enabling future cleanup of redundant validation logic.
  [pull/140891]

• Apiserver Watch Cache Optimization: This pull request improves the apiserver watch cache by replacing materialization of list results into slices with a streaming iterator over an immutable snapshot, enabling efficient pagination and filtering without extra memory overhead while preserving client-visible behavior.
  [pull/140896]

• kubectl cp Bug Fix: This pull request fixes a bug in kubectl cp by adding support for Pod references using the resource/name format, allowing users to specify remote file paths with syntax like pod/<pod-name>:<path>, enabling direct use of output from kubectl get pods -o name.
  [pull/140756]

• Test Stability Improvements: These pull requests address test instability by fixing a race condition in TestExternalJWTSigningAndAuth with additional wait calls and increasing the timeout in TestVolumeAttachLimitExceededCleanup to handle Windows CI mutex contention and disk I/O.
  [pull/140761, pull/140763]

• CPUManager Policy Update: This pull request updates the CPUManager's distribute-cpus-across-cores policy to allocate CPUs based on actual CPU topology rather than logical numbering, improving CPU distribution and affinity on systems with contiguous sibling thread IDs.
  [pull/140766]

• Kubelet CommandRunner Refactor: This pull request refactors kubelet's CommandRunner dependencies by moving the service wrapper out of the kuberuntime package and relocating instrumented_services, allowing kubelet to initialize the instrumented runtime service and improving instrumentation coverage.
  [pull/140767]

• Extensions API Comment Check: This pull request enables a check to ensure comments start with the serialized version of the field name specifically within the extensions API group.
  [pull/140779]

• HorizontalPodAutoscaler Category Addition: This pull request adds the podautoscalers category to the HorizontalPodAutoscaler resource, enabling users to list HPAs using kubectl get podautoscalers and aligning with the VerticalPodAutoscaler CRD category.
  [pull/140781]

3.2 Closed Pull Requests

This section provides a summary of pull requests that were closed in the repository over the past week. The top three pull requests with the highest number of commits are highlighted as 'key' pull requests. Other pull requests are grouped based on similar characteristics for easier analysis. Up to 25 pull requests are displayed in this section, while any remaining pull requests beyond this limit are omitted for brevity.

Pull Requests Closed This Week: 194

Key Closed Pull Requests

1. e2e_node: add CRI container metrics test for PodAndContainerStatsFromCRI: This pull request adds an end-to-end node test that validates the /metrics/cadvisor endpoint correctly reports container metrics via the CRI metrics collection path when the PodAndContainerStatsFromCRI feature gate is enabled, ensuring accurate per-container CPU, memory, filesystem, process, and pod-level network metrics, and complements the existing cadvisor-based container metrics test by exercising the alternative runtime metrics fetching method.

• URL: pull/140784

• Associated Commits: 269d3, 1bfcd, c2cee, 93ce3, c22ea, cbbba, 59734, 2beec, 35962, bdc23, c099c, 9b8bc, f6dc7, b0f77, 1d742, 4ea9d, 07595, aa7dc, 7ee50, b606c, 5d76d, 9304e, 64469, d795d, d18f3, 43f5d, 610b2, d60a7, ac14d, 7ef18, 9bca2, d595a, 77d8b, fe6a7, f5034, b6f63, 2034d, f97da, 6c1cd, 92d1d, a925c, cc084, 18545, c3515, 712de, 78f72, d3054, 39a9d, 2b198, 429a5, 19955, fc1de, 9193b, 95315, ae5e6, f0ec3, 7158c, 6bdaf, 298be, 5cce9, 60a91, 1cc68, 6cb4b, b78d6, 17223, f52d1, 412e5, 95ccf, 9c18c, a4116, 8d19a, a0352, 17296, e0316, b139c, f18c9, 354a1, b2ba4, 757cc, ecf6d, 745e2, 62d05, 1d850, 891a9, 98ecf, 07144, 3e8d4, 52947, 28dd6, cbb38, a45ce, 00083, 24471, 100bf, 4bfac, 568c8, 739e2, 5f099, 76cd4, e9d3b, 5cdb4, f0d0f, b6434, 2bd86, 29952, 3aa1c, 294c4, cc1b3, 0c872, f9b62, 493c5, b0b25, 710a5, 75693, 102c4, d2b5c, aee40, 46a0b, 314bf, 037ba, 9ebcf, 1f27b, 73359, 65cef, 91e51, 0c487, 37349, 99b75, 23888, 6c684, c106d, 0f0c7, 8eef0, 6bd05, 20cb5, 48f4d, 0a283, 872bd, 6489f, 088d4, 80901, afb3e, 59c83, 86ce9, ba803, 7949d, d52dd, 38e4e, cd90f, 06714, 92e30, 598f6, 5c2fa, d8d51, 02c02, 6a416, 24e2b, 7ffb8, 410f5, cb701, a4666, e7f8b, 1b6c4, cf6cb, bc62c, 4434f, f90cf, 3a0d1, 6426c, 0b6ec, 7e74f, 3f3f9, 8465b, fadd9, 1e3b3, 5cf0d, 96044, 0dd36, 3ab1d, e77dc, f981c, 2db44, 987c8, 28520, cf183, 3f971, ccc3b, 581e9, 7d0b0, 0225d, f69a8, 2ae0b, 67a49, e6688, 2dcc6, de6c4, c024e, 9b743, 62907, c3bf5, 118b9, 7d266, 3e4a2, 09e3a, c5315, 3a9ab, 086c8, 39695, ca79f, 908b5, 4cc89, 06c19, b812e, 130dc, 8feda, e908d, 5b5b0, e7d1f, a1faf, 98d03, 3cfad, 4e585, ea669, 66e48, babc2, bee5e, 1468e, fa75a, 4bc70, d974e, df2f0, 6e53d, 1d833, 386ae, 72f33, 0c35e, 7ceba, c4e40, 43617, d02d5, ed85b, 3a09e, 2825e, e2522, 69f9e, 78acd, 05e6a, 0f7d1, 83f3a

• Associated Commits: 269d3, 1bfcd, c2cee, 93ce3, c22ea, cbbba, 59734, 2beec, 35962, bdc23, c099c, 9b8bc, f6dc7, b0f77, 1d742, 4ea9d, 07595, aa7dc, 7ee50, b606c, 5d76d, 9304e, 64469, d795d, d18f3, 43f5d, 610b2, d60a7, ac14d, 7ef18, 9bca2, d595a, 77d8b, fe6a7, f5034, b6f63, 2034d, f97da, 6c1cd, 92d1d, a925c, cc084, 18545, c3515, 712de, 78f72, d3054, 39a9d, 2b198, 429a5, 19955, fc1de, 9193b, 95315, ae5e6, f0ec3, 7158c, 6bdaf, 298be, 5cce9, 60a91, 1cc68, 6cb4b, b78d6, 17223, f52d1, 412e5, 95ccf, 9c18c, a4116, 8d19a, a0352, 17296, e0316, b139c, f18c9, 354a1, b2ba4, 757cc, ecf6d, 745e2, 62d05, 1d850, 891a9, 98ecf, 07144, 3e8d4, 52947, 28dd6, cbb38, a45ce, 00083, 24471, 100bf, 4bfac, 568c8, 739e2, 5f099, 76cd4, e9d3b, 5cdb4, f0d0f, b6434, 2bd86, 29952, 3aa1c, 294c4, cc1b3, 0c872, f9b62, 493c5, b0b25, 710a5, 75693, 102c4, d2b5c, aee40, 46a0b, 314bf, 037ba, 9ebcf, 1f27b, 73359, 65cef, 91e51, 0c487, 37349, 99b75, 23888, 6c684, c106d, 0f0c7, 8eef0, 6bd05, 20cb5, 48f4d, 0a283, 872bd, 6489f, 088d4, 80901, afb3e, 59c83, 86ce9, ba803, 7949d, d52dd, 38e4e, cd90f, 06714, 92e30, 598f6, 5c2fa, d8d51, 02c02, 6a416, 24e2b, 7ffb8, 410f5, cb701, a4666, e7f8b, 1b6c4, cf6cb, bc62c, 4434f, f90cf, 3a0d1, 6426c, 0b6ec, 7e74f, 3f3f9, 8465b, fadd9, 1e3b3, 5cf0d, 96044, 0dd36, 3ab1d, e77dc, f981c, 2db44, 987c8, 28520, cf183, 3f971, ccc3b, 581e9, 7d0b0, 0225d, f69a8, 2ae0b, 67a49, e6688, 2dcc6, de6c4, c024e, 9b743, 62907, c3bf5, 118b9, 7d266, 3e4a2, 09e3a, c5315, 3a9ab, 086c8, 39695, ca79f, 908b5, 4cc89, 06c19, b812e, 130dc, 8feda, e908d, 5b5b0, e7d1f, a1faf, 98d03, 3cfad, 4e585, ea669, 66e48, babc2, bee5e, 1468e, fa75a, 4bc70, d974e, df2f0, 6e53d, 1d833, 386ae, 72f33, 0c35e, 7ceba, c4e40, 43617, d02d5, ed85b, 3a09e, 2825e, e2522, 69f9e, 78acd, 05e6a, 0f7d1, 83f3a

2. KEP-5936: Alpha support of atomic write volume user fields behind a feature gate AtomicWriteVolumeUserFields: This pull request implements alpha support for defining atomic write volume user fields in Kubernetes, enabling users to specify the desired file owner of atomically written volume files behind the new feature gate AtomicWriteVolumeUserFields, which is disabled by default.

• URL: pull/139764

• Associated Commits: ed4d2, 6b43e, 64b6e, 8e263, 55696, 918ac, 087c7, ba5a6, b4ae2, 2c63e, e031d, 27963, 57304, 0cba2, 5f6be, e7f5e, ec5d1, 66e0a, c4684, 64eaa, 600c9, cd22c, a944e, c9867, 18bee, 1ad21, cc560, 7d514, 8326b, 8ab47, 06eaa, d253d, c32ac, 56747

• Associated Commits: ed4d2, 6b43e, 64b6e, 8e263, 55696, 918ac, 087c7, ba5a6, b4ae2, 2c63e, e031d, 27963, 57304, 0cba2, 5f6be, e7f5e, ec5d1, 66e0a, c4684, 64eaa, 600c9, cd22c, a944e, c9867, 18bee, 1ad21, cc560, 7d514, 8326b, 8ab47, 06eaa, d253d, c32ac, 56747

3. KEP-5517: DRANodeAllocatableResources alpha 2 implementation: This pull request implements the Alpha 2 updates for KEP-5517 by enhancing the DRANodeAllocatableResources feature to support updated ResourceSlice mappings and PodStatus for direct and overhead resource allocations, integrating these allocations into kubelet’s pod and container cgroup and OOM score configurations, and enabling in-place resizing of resource requests and limits for pods using DRA claims.

• URL: pull/140009

• Associated Commits: 4228f, bccc2, 3dcdf, 577c2, c6bf6, 2515e, cedc8, 111cf, 9c773, 146ec, ec896, e13a7, e9707, 145e6, 2fcf0, 71750, 2ced5, 33df9, 873bd, 93e4d, c29a4, 349aa, 1c635, 2a165, 8be4c, eb3cb, e6b65

• Associated Commits: 4228f, bccc2, 3dcdf, 577c2, c6bf6, 2515e, cedc8, 111cf, 9c773, 146ec, ec896, e13a7, e9707, 145e6, 2fcf0, 71750, 2ced5, 33df9, 873bd, 93e4d, c29a4, 349aa, 1c635, 2a165, 8be4c, eb3cb, e6b65

Other Closed Pull Requests

3.3 Pull Request Discussion Insights

This section will analyze the tone and sentiment of discussions within this project's open and closed pull requests that occurred within the past week. It aims to identify potentially heated exchanges and to maintain a constructive project environment.

Based on our analysis, there are no instances of toxic discussions in the project's open or closed pull requests from the past week.

IV. Contributors

4.1 Contributors

Active Contributors:

We consider an active contributor in this project to be any contributor who has made at least 1 commit, opened at least 1 issue, created at least 1 pull request, or made more than 2 comments in the last month.

If there are more than 10 active contributors, the list is truncated to the top 10 based on contribution metrics for better clarity.

Access Last Week's Newsletter:

• Link