Weekly GitHub Report for Kubernetes: April 21, 2025 - April 28, 2025 (12:01:25)
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.3
1.2 Version Information:
The version release on March 11, 2025, introduces key updates and changes to Kubernetes, as detailed in the linked changelog, with additional binary downloads available for users. Notable highlights or trends from this release can be found in the Kubernetes announcement forum and the comprehensive 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.
-
dns query timeout on 1.31: This issue describes a problem with DNS query timeouts occurring after upgrading Kubernetes from version 1.29 to 1.31, affecting all pods and not limited to specific ones. The user reports that DNS queries, which previously worked in version 1.29, now result in timeouts and communication errors in version 1.31, despite the CoreDNS pods running without apparent issues.
- The comments discuss potential causes and solutions, including checking known DNS issues, CoreDNS version differences, and configuration problems. Suggestions include debugging the service, verifying CoreDNS configurations, and considering kube-proxy misconfigurations. Despite attempts to downgrade CoreDNS and follow debugging documentation, the issue persists, leading the user to revert to Kubernetes version 1.29, which resolves the problem.
- Number of comments this week: 10
-
Busybox image fails to build for windows: This issue involves a failure in building the Busybox image for Windows due to a certificate verification error when attempting to download a specific version of curl. The error indicates that the certificate is signed by an unknown authority, which suggests a problem with the TLS certificate verification process during the build.
- The comments discuss potential causes and solutions for the build failure, including the possibility of using a different source for the curl download or modifying the build process to bypass certificate verification. Contributors suggest that the issue might not be with the build environment but rather with the certificate itself, and there is a discussion about whether the current source for curl is appropriate. There is also a mention of using the official curl downloads for Windows and a reference to a Slack conversation explaining the rationale behind the current setup.
- Number of comments this week: 9
-
please provide a procedure to shutdown the cluster: This issue highlights the lack of a standardized procedure within Kubernetes for shutting down an entire cluster, which is necessary for tasks such as moving hardware or performing maintenance. The user emphasizes the importance of features like stopping workloads, unmounting volumes, and ensuring the synchronization of etcd databases before shutdown.
- The comments discuss that while Kubernetes provides tools like
kubectl drainfor managing workloads, a comprehensive shutdown procedure is typically handled by external cluster management tools like kOps or Rancher. It is noted that the core Kubernetes project does not cover machine management, and the request for a coordinated shutdown feature is considered out of scope for core Kubernetes, suggesting it as a feature request for higher-level tools. - Number of comments this week: 7
- The comments discuss that while Kubernetes provides tools like
-
Importing CustomResourceDefinition shouldn't require importing server implementation: This issue addresses the need to import server implementation components when creating a typed client with CustomResourceDefinition, which is currently required due to dependencies on the apiextensions-apiserver package. The proposal suggests moving the type to a new package, such as k8s.io/api or k8s.io/apiextensions, and using type aliasing to maintain backward compatibility, allowing for a gradual migration without breaking existing implementations.
- The comments reflect a consensus on moving the type to
k8s.io/apiextensionsto avoid server dependencies, with some humor about package naming. There is agreement on the separation from server bits, and a preference for not grouping it withk8s.io/apito maintain logical separation and tooling benefits. The issue is accepted for triage and marked for cleanup. - Number of comments this week: 7
- The comments reflect a consensus on moving the type to
-
ConfigMap exists in namespace even after namespace is deleted: This issue describes a problem where a ConfigMap continues to exist in a Kubernetes cluster even after the namespace it belonged to has been deleted, due to a race condition between the namespace garbage collector and a server-side apply (SSA) patch issued by a controller. The user is puzzled as to why the API server allows object creation via SSA even after the namespace has a
deletionTimestampset, and they are unable to reproduce the issue consistently, suggesting it might be a rare occurrence.- A script is shared to demonstrate the issue, showing that SSA operations can succeed temporarily after a namespace is deleted. Audit logs are provided, showing a successful SSA patch after namespace deletion. A discussion ensues about potential causes, including race conditions between requests sent to different masters in a cluster. The issue is acknowledged, and additional logs are requested, but the user indicates limitations in log availability due to the managed nature of the cluster.
- Number of comments this week: 6
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.
- Zone-aware down scaling behavior: This issue addresses a problem with zone-aware downscaling behavior in Kubernetes, where during scale-in operations, there is an imbalance in pod distribution across zones despite using a topology spread constraint with
maxSkew: 1. The user reports that during nighttime scale-ins, the system sometimes leaves only one pod in a zone while others are distributed across two zones, leading to high CPU usage for the lone pod, which contradicts the expected behavior of maintaining a balanced distribution with at most a+/- 1pod difference per zone. 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: 20
Summarized Issues:
- DNS Query Timeout in Kubernetes 1.31: This issue describes a problem where DNS queries are timing out in Kubernetes version 1.31 after an upgrade from version 1.29, affecting all pods and resulting in communication errors with the DNS server. Despite the CoreDNS pods running without errors, attempts to downgrade the CoreDNS version do not resolve the issue.
- OpenAPI JSON Parsing Error: A failure to parse an OpenAPI JSON file using Prance is caused by a recursion depth limit error due to a self-referencing definition within the "allOf" and "oneOf" properties of the JSONSchemaProps. The issue seeks suggestions for successful parsing.
- Kubelet Container Cleanup Failure: In a Kubernetes cluster with many CronJobs, the kubelet fails to clean up exited containers, leading to IP address management congestion and eventual failure due to exceeding gRPC message size limits. Attempts to mitigate the issue through CronJob configuration adjustments have been unsuccessful.
- Volume Detachment Failure: The Kubernetes kubelet fails to properly detach a volume from a pod, resulting in the volume being stuck in a "VolumesInUse" state on a node even after the pod has been evicted. This prevents the pod from being reinitialized on a new node due to a "Multi-Attach error," exacerbated by an upgrade to Karpenter.
- Cluster Shutdown Procedure Request: There is a request for Kubernetes to provide a standardized procedure for shutting down an entire cluster, including stopping workloads, unmounting volumes, and ensuring etcd databases are synchronized. This is to facilitate tasks such as hardware relocation or maintenance, which is currently not addressed by core Kubernetes features.
- High Memory Consumption with ValidatingAdmissionPolicy: High memory consumption is observed in Kubernetes when using
ValidatingAdmissionPolicyandValidatingAdmissionPolicyBindings, with memory usage increasing significantly with the number of policies and complexity of expressions. The issue seeks optimization strategies such as reusing existing expressions to mitigate this problem.
- Unexpected NodeExpandVolume Invocation: The unexpected invocation of the NodeExpandVolume function for a Persistent Volume Claim (PVC) using NFS occurs despite the ControllerExpandVolume indicating that node expansion is not required. This leads to a VolumeResizeFailed warning on application pods even though the PVC and Persistent Volume (PV) have been successfully resized by the controller.
- ConfigMap Persistence After Namespace Deletion: A ConfigMap persists in a Kubernetes cluster even after its associated namespace has been deleted, likely due to a rare race condition involving concurrent operations by the namespace garbage collector and a server-side apply (SSA) patch. This allows object creation despite the namespace having a
deletionTimestampset.
- Busybox Image Build Failure on Windows: A failure in building the Busybox image for Windows is due to a TLS certificate verification error when attempting to download a curl package from an unofficial source. The issue suggests a need to either update the certificate authority in the build environment or switch to a more reliable source for the curl binary.
- Typed Client Creation Refactor: There is a need to refactor the Kubernetes codebase so that creating a typed client with
CustomResourceDefinitiondoes not require importing server implementation modules. The suggestion is to relocate type definitions to a new or existing package likek8s.io/apiextensionsto facilitate this change without breaking existing functionality.
- NFS MountOptions Not Respected: The
spec.mountOptionsspecified in a Persistent Volume (PV) configuration for mounting an NFS share are not being respected, as evidenced by the actual mount command output showing different options than those specified. The issue includes a suggestion for a test case to reproduce the problem.
- Volume Expansion Test Enhancement: Enhancing the existing
testsuites/volume_expand.goin the Kubernetes project to include recovery features related to volume expansion is proposed. This aims to make the tests more robust and applicable across various CSI drivers.
- Fine-Grained Access Control Implementation: There is a need for implementing fine-grained access control to resources in Kubernetes, specifically allowing only certain Pods within specified namespaces to access particular ResourceSlices. This is to enhance workload-level permissions without relying on external systems like Gatekeeper.
- Windows KubeProxy LoadBalancer Update Failure: The Windows KubeProxy's invocation of the ModifyLoadBalancer API fails to update the endpoints in the Host Network Service (HNS) LoadBalancer on Windows Server 2022. Despite using HNS version 15.4, the endpoints do not reflect the expected changes after scaling up pods in an AKS cluster running Kubernetes version 1.31+.
- Pod Stuck in Pending State Due to Anti-Affinity Rules: A pod in a Kubernetes cluster is stuck in a pending state due to pod anti-affinity rules, despite there being no apparent conflicting labels on the nodes. It is suspected that outdated cache data in the informer might be causing the scheduling failure.
- TestGetCacheBypass Failing Test Case: The "TestGetCacheBypass" test case in the Kubernetes project fails to retrieve data from the cache with a resource version of 0 due to a "dummy error." It has been identified as both a failing test and a flake under the API machinery SIG.
- Gocritic Linter Warnings Fix: Addressing and fixing the remaining gocritic linter warnings in the Kubernetes project involves creating individual pull requests for each affected Special Interest Group (SIG). These issues are considered legitimate, and their resolution will allow the removal of specific configurations in the project's golangci-lint setup.
- Server Side Applies Field Manager Conflict: Using multiple field managers with Server Side Applies in Kubernetes, particularly when transitioning from CLI to ArgoCD, leads to inconsistent behavior in deployment resource management. Changes to affinity rules are not reflected due to conflicting field ownership and difficulties in resetting the resource state without replacement.
- Secure Filepath Traversal Replacement: Replacing custom code for secure filepath traversal-resistant operations in the Kubernetes project with the newly introduced
os.Rootlibrary from Go version 1.24 is proposed. This addresses past vulnerabilities related to filepath traversal time-of-check-to-time-of-use (TOCTOU) issues.
- NoExecute Taint Not Removed After Disruption: Nodes tainted with NoExecute for eviction purposes before entering a PartialZonalDisruption are not being untainted afterward. This prevents the restoration of workloads as expected.
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: 15
Summarized Issues:
- Kubernetes Upgrade Issues: Upgrading Kubernetes from version v1.31.6 to v1.31.7 led to a 404 error when executing the
kubectl execcommand on a pod. This suggests a misconfiguration or an unexpected nginx proxy in front of the Kubernetes API server, rather than an issue with kube-proxy.
- Architecture-Specific Test Failures: A failing test on the ppc64le architecture within Kubernetes is not reporting container metrics as expected. Discrepancies were noted in the
container_spec_memory_limit_bytesvalues, with a fix being addressed in a related pull request.
- Node Readiness Conditions: A proposal for custom, extensible readiness conditions for Kubernetes Nodes aims to improve upon current workarounds using taints. This addresses issues such as missing observability data, insecure pod states, and pod failures due to incomplete runtime configurations.
- Jenkins Pipeline Failures on AKS: Jenkins pipelines are failing randomly when executing multiple stages on a Windows node pool in an Azure Kubernetes Service (AKS) environment. This is potentially due to differences in the file system of the Windows pods after updating Jenkins and AKS versions.
- Kubernetes Scheduler Preemption Process: The unnecessary clearing of the
nominatedNodeNamein the Kubernetes scheduler's preemption process when no candidates are found is being addressed. Its removal is suggested to avoid redundant operations and potentially improve performance by reducing API calls.
- Kubectl Drain Command Issues: In Kubernetes 1.32, the
kubectl draincommand fails to complete successfully when using node credentials due to the default activation of the AuthorizeNodeWithSelectors feature gate. This restricts nodes to only query pods associated with them, leading to permission errors after pods are evicted or terminated.
- NamespaceName JSON Tags: Adding JSON tags to the
types.NamespaceNamein Kubernetes is proposed to facilitate its use in custom resource definitions. The absence of these tags necessitates redundant type definitions across various projects.
- CVE-2025-22871 Vulnerability Impact: The Kubernetes project is assessing whether it might be impacted by the CVE-2025-22871 vulnerability. This involves determining if an update to the Go version is necessary based on the potential impact.
- Go Vet Panic Issue: A panic occurs when running
go veton thek8s.io/dynamic-resource-allocation/resourceslice/trackerpackage, suspected to be related to the improper use of internal packages. It was resolved by cleaning the build cache and ensuringgo vetis run on the entire module or subpackage rather than individual files.
- Persistent Volume Claim Resize Issues: An unexpected invocation of the NodeExpandVolume function after a PVC resize operation on AWS EBS results in a warning due to a race condition. This causes confusion as the error persists even after the PVC is successfully resized.
- NodeResizePending Status Issue: The "NodeResizePending" status is not removed from a PVC after a successful NodeExpandVolume operation, particularly when there is a version mismatch between the cluster and node. This leads to complications with the external-resizer's recovery feature and requires manual intervention to clear the status.
- K8s StatefulSet Topic: This issue pertains to a topic related to "K8s StatefulSet" in the Kubernetes project, as indicated by its title and body. It has been documented on GitHub without any additional comments.
- Flaking Test in Etcd3 Storage Package: A flaking test in the Kubernetes project, specifically the "TestWatchErrResultNotBlockAfterCancel" in the etcd3 storage package, is experiencing data race conditions and panic errors. This affects the stability of certain CI jobs.
- HorizontalPodAutoscaler Watch Requests: The HorizontalPodAutoscaler in Kubernetes is making failed
watchrequests for pod metrics due to a missingresourceVersionparameter. This results in 422 error codes and unnecessary load, although it does not immediately impact functionality as it falls back to successfullistcalls.
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: 43
Key Open Pull Requests
1. WIP: Test RestartContainerDuringTermination feature gate: This pull request is focused on testing the "RestartContainerDuringTermination" feature gate in Kubernetes by adding end-to-end tests, managing container termination in a non-blocking manner, and implementing logic to restart containers if liveness or startup probes fail, while also ensuring that the probe manager removes pods after all containers have stopped.
- URL: pull/131461
- Merged: No
2. Validate kubelet serving cert CN via host rewrite and DialTLSContext: This pull request introduces a new feature to the Kubernetes project that validates the kubelet serving certificate's Common Name (CN) through host rewriting and the use of DialTLSContext, as part of the v1.34 milestone under the SIG Auth group, with multiple commits refining the implementation.
- URL: pull/131450
- Merged: No
3. Fixes for bad handling of pointers and aliases in validation: This pull request addresses the inconsistent handling of pointers and aliases in validation by adding missing test cases, fixing implementations, and redefining how Context.Type is defined for typedefs to ensure consistency across validators, requiring them to explicitly manage aliases and pointers.
- URL: pull/131399
- Merged: No
Other Open Pull Requests
- Golangci-lint v2 Update and Code Fixes: This pull request updates Kubernetes to use the new golangci-lint v2, revisits check suppressions to fix broken code, and completes the migration started in a previous pull request by reorganizing suppression rules and addressing inefficiencies and bugs identified by the linter.
- NodeExpansion Feature Finalization: These pull requests are automated cherry-picks of a previous change to various release branches, involving checking for newer resize fields to determine the status of the expansion recovery feature in kubelet, and include modifications such as removing the feature gate check to finalize the status of NodeExpansion.
- Windows Proxy Regression Fix: These pull requests are automated cherry-picks of a previous fix intended to resolve a regression in the Windows Proxy introduced in version 1.31, where the creation of Host Network Service (HNS) endpoints fails if remote HNS endpoints with the same IP address have already been created, by ensuring that the local endpoint is not mistakenly deleted instead of the remote endpoint.
- Kubernetes Documentation Enhancements: These pull requests aim to enhance the documentation by detailing the implications of using the hostNetwork feature with ports, correcting a typo in the word "immediately," and updating the API documentation for the
ResizePolicyfield to clarify its application scope, thereby improving clarity and understanding for users.
- Codebase Cleanup and Refactoring: These pull requests focus on cleaning up the Kubernetes codebase by removing deprecated versions, relocating code to appropriate locations, and replacing loop-based condition checks with more efficient functions, thereby reducing code complexity and improving maintainability.
- Security and Bug Fixes: These pull requests address various security vulnerabilities and bugs, including fixing the OpenID Connect (OIDC) discovery document publishing process, introducing a validation check to prevent privilege escalation risks, and setting appropriate groups in the SubjectAccessReview (SAR) to accurately simulate the service account’s identity.
- Test and Metrics Improvements: These pull requests introduce a new
ResetMetricsoption to theTestServer, a new unit test for Precedences in LoadingRules, and address a time rounding issue by increasing the delay in the kuberuntime termination order test, thereby improving test reliability and coverage.
- Dependency and Client Enhancements: These pull requests update dependencies to address security advisories and enhance the client-go library by adding emulation version information to its user-agent string, which can help in identifying the version of the client being used for better debugging and compatibility checks.
- Scheduler and Control Plane Improvements: These pull requests introduce a feature to enhance the verbosity of scheduler logs, refactor the default service CIDR controller logic, and promote aojea as an approver for the control plane, thereby improving debugging capabilities and project management.
- API Rule and Validation Enhancements: These pull requests address an issue with the sample-apiserver by updating the code generation process to resolve API rule violations and enhance the error message generated by the
validate.EachSliceVal()function to improve clarity and usability for developers.
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: 76
Key Closed Pull Requests
1. roseteromeo56/kubernetes: This pull request involves multiple commits by Romeo Rosete, primarily adding various JavaScript and CSS files, as well as SVG logos, to the Kubernetes project, but it was ultimately not merged.
- URL: pull/131398
- Merged: No
- Associated Commits: 87086, ddfdf, 5e6f5, a45f6, 15323, 13aae, fa0f7, 586eb, 2146e, a83ea, b79ac, 27388, 45ca8, bc369, 4727f, b856e, b590b, 4b5a2, 5ac07, 58d55, 87c2b, 5afce, b39eb, 56a28, f62bc, 6eff1, 7e49e, 099c5, 733e0, 3559a, dc668, 4fe56, 01c48, 7c072, e5bdc, ff0a3, 6c10b, 2f241, 5f171, 1c95e, 7548b, 3ccf5, 4ded5, 9f55c, e68ed, 95243, f8753, c8438, 10da5, 822a9, 67baf, d1f01, 006bb, 77c11, affd1, 8c419, 41b99, 5c778, 9b10a, 4e536, 4d84a
2. Fixes for bad handling of pointers and aliases in validation: This pull request addresses the inconsistent handling and testing of pointer and typedef fields in validation by adding missing test cases, fixing implementations, and redefining how Context.Type is defined for typedefs to ensure consistency, requiring validators to unalias and unpointer types.
- URL: pull/131390
- Merged: No
- Associated Commits: c76b0, 36b79, a15b1, 3178c, 77b1d, a21b4, 8ed64, 48949, f157c, 81257, 414a2, ebdbb, 89774, 03aa9, d78db, df7ac, c50d4, 7d04a, e3470, 82ce7, 70b2f, 51f6e, fd999
3. Update README.md: This pull request involves multiple updates to the README.md and LICENSE files in the Kubernetes project, as evidenced by several commits, but it was ultimately not merged.
- URL: pull/131470
- Merged: No
Other Closed Pull Requests
- Test Refactoring and Sorting Behavior: This topic involves refactoring tests for sorting keys in
kubectl describe secretby converting them to parameterized tests. The pull request also adds new test cases to explicitly describe expected sorting behavior, including cases for sorting with casing and keys containing numbers.
- Kubelet and PVC Status Updates: This topic addresses the issue of checking for newer resize fields to determine the expansion recovery feature status in Kubernetes' kubelet. The pull request ensures that the PersistentVolumeClaim (PVC) status accurately reflects changes in storage requests and conditions without relying on feature gate checks.
- Code Generation and Dependency Management: This topic focuses on simplifying the setup process for the
hack/update-codegen.shscript by automatically ensuring the installation ofgoimportsandprotoc. The pull request eliminates the need for users to manually install these dependencies and ensures the correct versions are managed.
- Build Process and Go Version Management: This topic addresses a cleanup task by modifying the build process to read the Go version from a single source, the
.go-versionfile. The pull request reduces redundancy and potential errors in the Kubernetes project.
- Networking e2e Test Improvements: This topic addresses a flaky test in the Kubernetes networking e2e test suite by adding an explicit wait condition for endpoint updates after pod deletion. The pull request improves error logging for better debugging and enhances status reporting during the test.
- API Test Data Maintenance: This topic involves a cleanup task where the v1.33.0 API test data is added and the v1.31.0 API test data is removed. The pull request is part of maintaining up-to-date test data for each release.
- Kube Proxy Controller Cleanup: This topic aims to clean up the kube proxy controller by removing the unused burst feature and introducing a new bounded frequency runner based on the workqueue. The pull request remains unmerged due to a dependency issue in client-go.
- Kubectl Command Timeout Adjustment: This topic increases the timeout value of the
kubectl cpcommand from 10 seconds to 30 seconds. The pull request provides more time for pods experiencing insufficient resources as part of a cleanup effort.
- Error Handling and Flake Resolution: This topic addresses a cleanup and flake issue by ensuring that the original error is retained when the
ExecCommandInContainerWithFullOutput()function fails. The pull request aims to deflake issue #131067 in the Kubernetes project.
- Golangci-lint Tool Update: This topic involves updating the golangci-lint tool to version 2 and adjusting the associated configuration and implementation within the project's tooling. The pull request is part of a cleanup effort categorized under backlog priority and testing significance, although it was not merged.
- SIG Autoscaling Maintainers Update: This topic updates the SIG Autoscaling maintainers list by adding @towca, @raywainman, and the author, while removing @MaciekPytel. The pull request is part of a cleanup effort to ensure the list reflects the current maintainers.
- Windows HNS Endpoint Bug Fix: This topic addresses a bug in the Kubernetes project where the local Host Network Service (HNS) endpoint on Windows nodes was being mistakenly deleted instead of the remote endpoint. The pull request ensures that the remote endpoint always takes precedence in the queriedEndpoints map used for endpoint deletion.
- Kubelet Authz Test Framework Update: This topic updates the
kubelet_authzcomponent of the Kubernetes project to a new test framework. The pull request addresses a bug and ensures compatibility with the latest testing standards.
- Goroutine Leak Detection Cleanup: This topic addresses the cleanup of unnecessary exceptions to goroutine leak detection in the client-go cache unit tests of the Kubernetes project. The pull request ensures more robust and efficient testing by eliminating leaked goroutines.
- Scheduler Performance Tool Enhancement: This topic introduces a new feature to the Kubernetes project by adding an option to the scheduler-perf tool. The pull request allows users to initialize the target API server before the scheduler performance tests begin, enhancing the flexibility and utility of the testing process.
- CoreDNS Component Update: This topic updates the CoreDNS component to version 1.12.1 in the Kubernetes project. The pull request is part of a cleanup effort and includes a commit signed by yashsingh74.
- Etcd3 Watcher Simplification: This topic simplifies the etcd3 watcher as a follow-up to a previous task (#131020). The pull request is categorized as a cleanup and was successfully merged into the Kubernetes project.
- PodSecurityLevel Test Update: This topic updates the PodSecurityLevel used during Service CIDRs tests to address a bug and failing tests identified while updating Kubernetes in OpenShift. The pull request ensures that the tests correctly set the enforcement labels.
- PVC Status Field Name Correction: This topic addresses a bug by correcting the field name mismatch from "allocatedResourceStatus" to "AllocatedResourceStatuses" in the PersistentVolumeClaimStatus class. The pull request ensures consistency with the documentation and proper PVC status validation.
- FlowSchema Objects Cleanup: This topic removes outdated FlowSchema objects related to leader election that used unsupported lock types since Kubernetes 1.28. The pull request prevents potential saturation of the
leader-electionPriority Level and ensures correct management of leases-based leader election API calls.
- Directory Name Length Bug Fix: This topic addresses a bug by shortening long directory names for end-to-end (e2e) Pod logs to 255 characters. The pull request resolves failures due to directory names approaching the 256-character limit, affecting the creation of directories for storing logs during e2e tests.
- Volume Access Test Bug Fix: This topic addresses a bug in the Kubernetes project by ensuring that tests designed to verify multi-node access to a volume correctly create
ReadWriteManyvolumes. The pull request aligns the test's functionality with its intended purpose.
- Memory Leak Resolution in Busybox Test: This topic addresses a memory leak issue in the Kubernetes project by updating the busybox test image from version 1.36.1 to 1.37.0. The pull request resolves Out Of Memory (OOM) failures observed during Container Lifecycle tests, particularly improving the stability of a flaking test on the ppc64le architecture.
- Mockery and Go Compatibility Fix: This topic addresses a compatibility issue between mockery v2.40.3 and Go 1.24.0, which caused a panic during the mocking process. The pull request upgrades the mockery version to v2.53.3 to resolve the problem.
- Image Records Lock Bug Fix: This topic addresses a bug in the Kubernetes project by acquiring the
imageRecordsLockwhen removing an image. The pull request fixes a potential race condition between the kubelet Garbage Collector and the Eviction Manager, preventing a "fatal error: concurrent map writes."
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 |
|---|---|---|---|---|
| BenTheElder | 16 | 8 | 2 | 70 |
| pohly | 17 | 6 | 7 | 37 |
| roseteromeo56 | 61 | 2 | 0 | 0 |
| aojea | 10 | 5 | 6 | 28 |
| liggitt | 4 | 3 | 0 | 35 |
| carlory | 11 | 8 | 0 | 22 |
| bart0sh | 1 | 1 | 1 | 31 |
| gnufied | 14 | 6 | 1 | 12 |
| haosdent | 3 | 3 | 0 | 22 |
| sanposhiho | 0 | 0 | 1 | 25 |