Weekly GitHub Report for Kubernetes: March 10, 2025 - March 17, 2025
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:
The current version of this repository is v1.32.2
1.2 Version Information:
The version release, created on February 12, 2025, introduces key updates and changes to Kubernetes, with detailed information and additional binary downloads available in the linked changelog. Notable highlights or trends from this release can be found in the Kubernetes announcement forum and the changelog documentation.
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.
As of our latest update, there are no active issues with ongoing comments this week.
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.
- Support endpoint authentication for K8s trace configuration: This issue is about adding support for gRPC authentication in Kubernetes trace configuration, as currently only the gRPC format endpoint is supported without authentication. The lack of authentication support is seen as insufficient, and the request is to enable gRPC authentication to enhance security for trace configurations.
- Scheduler: Avoid scheduling pods to nodes where the allocatable resource is insufficient for the pod limit resource: This issue addresses the problem of scheduling pods to nodes where the allocatable resources are insufficient to meet the pod's specified limit resources, which can render the pod's limit resource settings ineffective. The proposed solutions include either preferring nodes with sufficient allocatable resources (soft solution) or outright rejecting nodes that do not meet the resource requirements (hard solution), and it also questions whether an in-tree or out-of-tree plugin would be more suitable for implementation.
- kube-proxy: Inconsistent behaviors about disabling health check server and metrics server: This issue highlights inconsistencies between the documentation and the actual behavior of the kube-proxy component in Kubernetes regarding the disabling of the health check server and metrics server using the "--healthz-bind-address" and "--metrics-bind-address" flags. The problem is that setting these flags to empty values does not disable the servers as expected, and there are inconsistencies in the validation code that allow an empty HealthzBindAddress but not an empty MetricsBindAddress, leading to potential errors and unexpected behavior in the kube-proxy. Since there were fewer than 5 open issues, all of the open issues have been listed above.
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: 0
Summarized Issues:
As of our latest update, there are no open issues for the project this week.
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: 5
Summarized Issues:
- Failing Unit and E2eNode Tests: The "TestUnsafeConversions" unit test in Kubernetes started failing due to a Golang change that introduced a panic when using
AllocsPerRunin parallel, which was resolved by removing parallel execution. Similarly, the "ImageGCNoEviction" test in the E2eNode Suite fails when executed with kubetest2, as it does not handle DiskPressure correctly, leading to a failed pod state, with a fix in progress.
- Ephemeral Storage and PersistentVolumeClaim Issues: There is confusion in Kubernetes regarding data being written to disk instead of ephemeral storage when using an emptyDir volume, despite specifying ephemeral storage resource requests and limits, prompting a need for solutions to enforce ephemeral space usage. Additionally, a bug causes pods with a PersistentVolumeClaim in a terminating state to fail in refreshing their ServiceAccount tokens, potentially disrupting service meshes like Linkerd and Istio.
- Consistent Failure of Storage Job: The "ci-kubernetes-e2e-storage-kind-alpha-beta-features" job consistently fails as tracked by Testgrid, with no specified reason for the failure. Contributors are actively discussing and investigating the issue to find a resolution, as indicated by the comments and linked resources.
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: 0
As of our latest update, there are no open pull requests for the project this week.
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: 12
Key Closed Pull Requests
1. StatefulSet: add explicit validation for .spec.serviceName and mark the field optional: This pull request addresses a bug and API change in Kubernetes by explicitly marking the .spec.serviceName field in StatefulSets as optional to align with actual usage and documentation, and by adding validation to ensure that if this field is set, it must conform to DNS 1123 label standards to prevent the controller from failing to create pods due to invalid service names.
- URL: pull/130233
- Merged: 2025-03-13T20:27:47Z
2. Fix kubelet restart unmounts volumes of running pods if the referenced PVC is being deleted by the user : This pull request addresses a bug in Kubernetes where the kubelet, upon restart, unintentionally unmounts volumes of running pods if the Persistent Volume Claim (PVC) they reference is being deleted by the user, by adding an end-to-end test to reproduce the issue and implementing a fix to handle PVCs stuck in a terminating state during the Device State Watcher (DSW) rebuild process.
- URL: pull/130335
- Merged: 2025-03-10T10:09:47Z
3. KEP-4330: add forward compatibility for compatibility mode: This pull request introduces forward compatibility for compatibility mode in Kubernetes by adding two new API server CLI flags, --emulation-forward-compatible and --runtime-config-emulation-forward-compatible, which allow for the implicit and explicit enabling of APIs introduced after the emulation version, ensuring that controllers with newly promoted APIs can still function in compatibility mode.
- URL: pull/130354
- Merged: 2025-03-14T01:55:58Z
Other Closed Pull Requests
- Failing Test Issues: This topic covers pull requests that address failing test issues in the Kubernetes project. One pull request resolves a failing test by pre-pulling images for the
ImageGCNoEvictiontest when run withkubetest2, while another removes parallel execution for tests usingAllocsPerRundue to a Golang change causing a panic.
- Test Suite Cleanup: This topic involves a pull request that streamlines the Kubernetes test suite by removing a redundant test related to the configmap volume. The functionality verified by this test is already covered by an existing conformance test, thus optimizing the test suite.
- Pod Distribution Budget Optimization: This pull request addresses unnecessary updates to the Pod Distribution Budget (PDB) in Kubernetes. By implementing the use of ResourceVersion, it prevents such updates, optimizing the system's performance and resource management.
- Runc Version Update: This pull request updates the runc version from v1.2.1 to v1.2.5 in the Kubernetes project. It addresses a regression issue related to systemd v230 affecting workloads using NVIDIA GPUs by modifying unit properties to avoid requiring a systemctl daemon-reload for transient units.
- WebSocket Client Refactor: This pull request refactors the tunneling connection implementation in Kubernetes to use the Gorilla WebSocket client directly. It replaces the previous custom RoundTripper approach, aligning better with WebSocket semantics and simplifying the codebase.
- Request Validation Alignment: This pull request aligns request validation with etcd3 store validation in Kubernetes. It moves the validation of requests that set resource version and continue from internal rejection in etcd3 to the request validation phase, eliminating the need to test this scenario in TestGetListCacheBypass.
- Consistency Checking Feature: This pull request implements a feature for consistency checking in the Kubernetes project. It was successfully merged on March 11, 2025, as indicated by its title and commit message.
- Scheduling Process Modification: This pull request introduces a feature that modifies the Kubernetes scheduling process. It calls
PreEnqueueplugins before adding a pod to the backoff queue, allowing for the possibility to skip these calls when popping from the backoff queue if the active queue is empty.
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.
| Contributor | Commits | Pull Requests | Issues | Comments |
|---|---|---|---|---|
| bart0sh | 17 | 2 | 2 | 64 |
| aojea | 20 | 2 | 1 | 23 |
| jpbetz | 32 | 0 | 1 | 4 |
| googs1025 | 10 | 3 | 1 | 23 |
| serathius | 18 | 4 | 5 | 8 |
| pohly | 19 | 2 | 1 | 11 |
| tallclair | 17 | 1 | 1 | 13 |
| omerap12 | 3 | 2 | 0 | 25 |
| zhifei92 | 17 | 6 | 0 | 7 |
| Jefftree | 22 | 1 | 1 | 4 |