LeaderWorkerSet: An API for deploying a group of pods as a unit of replication
C-Rank Grade: A (Welcoming) - 61/100
External PR Merge Rate: 54%
Response Time: 21h
First Timer Success: 47%
kubernetes-sigs/lws has a recorded first-timer success rate of 47.1%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in kubernetes-sigs/lws respond to incoming external pull requests in approximately 21.0 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 61.0 places kubernetes-sigs/lws in the A tier.
The external contributor pull request merge rate for kubernetes-sigs/lws is 54.5%, based on public PR activity from non-core contributors.
kubernetes-sigs/lws does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Balanced & professional review environment in kubernetes-sigs/lws. Maintains strict focus on technical quality and test standards.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/kubernetes-sigs/lws?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 07:00 UTC (07:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 15:00 to 19:00 UTC (15:00 - 19:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~14 hours (68% approval). Large PRs (>500 lines) take ~101 hours (25% approval). Keep your diff compact for rapid review.
What would you like to be added: Document the supported Kubernetes versions in the README and installation guide. Replace the outdated Kubernetes >= 1.26 requirement with >= 1.33. State that LWS supports Kubernetes 1.33 through 1.36, matching the four existing required E2E presubmit jobs. Link the corresponding TestGrid jobs. Follow the public support-policy pattern used by JobSet. A similar documentation update was made in Kueue. Why is this needed: The current installation documentation still lists Kubernetes 1.26 as the minimum requirement, while CI validates Kubernetes 1.33, 1.34, 1.35, and 1.36. Users currently have no clear public statement describing the tested and supported Kubernetes versions. Completion requirements: This enhancement requires the following artifacts: Design doc API change Docs update /help wanted
What happened: #323 removed pods/create from generated RBAC files but missed the kubebuilder marker in pod_controller.go. Therefore, #325 regenerated config/rbac/role.yaml with pods/create, leaving Helm and Kustomize inconsistent. LWS does not create Pods directly; the StatefulSet controller does. Expected fix: Remove create from the Pod RBAC marker. Keep create for Services. Regenerate and test the manifests. Verify LWS works without Pod creation permission. This should preferably follow #952, so CI keeps Helm and Kustomize RBAC synchronized.
What happened: The pull-lws-test-e2e-upgrade-main job exits before running the upgrade tests: hack/e2e-test.sh: line 136: archive: unbound variable Example failure: https://prow.k8s.io/view/gs/kubernetes-ci-logs/pr-logs/pull/kubernetes-sigs_lws/953/pull-lws-test-e2e-upgrade-main/2090340013316247552 What you expected to happen: The temporary image archive should be cleaned up and the upgrade tests should continue. How to reproduce it (as minimally and precisely as possible): Trigger pull-lws-test-e2e-upgrade-main against a revision containing the current kind_load_image implementation. Anything else we need to know?: This was introduced by #928 (78ea4be): a RETURN trap outlives the function-local archive variable, and nounset terminates the script when the trap runs again. A fix exists in the unrelated open PR #877 (ad9d95b). It would be useful to extract it into a focused PR. Environment: LWS revision: main at 3824359 Test environment: Kubernetes Prow presubmit Others: Bash with noun
What would you like to be cleaned: Avoid duplicating Kubernetes YAML manifests across Markdown pages. Add a Hugo include shortcode and render documentation snippets from canonical sample files, such as files under config/samples or site/static/examples. Suggested scope: Add an include shortcode for YAML examples. Select one canonical location for runnable samples. Migrate repeated LWS and DisaggregatedSet snippets incrementally. Make the site build fail when an included example is missing. Prior art: JobSet include shortcode JobSet documentation usage Kueue include shortcode Why is this needed: Copied YAML can drift from the CRD schema and runnable examples. Review of #989 highlighted how repeated DisaggregatedSet snippets can diverge from the required roles[].spec structure. Using a single source of truth reduces maintenance, applies fixes consistently, and allows CI to validate the same manifests shown in the documentation.
What happened: The upgrade E2E presubmit is configured with always_run: false and optional: true. API defaulting, ControllerRevision, CRD, and rollout changes can therefore pass required CI without upgrade coverage. PR #877 demonstrated this gap: a new defaulted field could make a legacy revision appear changed and trigger an unintended rollout. What you expected to happen: Automatically run and require upgrade E2E for relevant changes. Documentation-only changes can remain excluded to control CI cost. How to reproduce it (as minimally and precisely as possible): Open a PR modifying revision or API defaulting logic and observe that the upgrade lane is not required. Anything else we need to know?: Related work: #926 and #928. Environment: Kubernetes version: N/A LWS version: main Cloud provider or hardware configuration: N/A OS: N/A Kernel: N/A Install tools: N/A Others: Prow presubmit configuration
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to kubernetes-sigs/lws, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of kubernetes-sigs/lws acknowledge new external contributions in approximately 21 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 54.5% were successfully merged into the primary branch.
kubernetes-sigs/lws has a recorded first-timer success rate of 47.1%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~21 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 61.0 places kubernetes-sigs/lws in the Welcoming tier.
The external pull request merge rate is 54.5%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
kubernetes-sigs/lws does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.
All metrics displayed for kubernetes-sigs/lws are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.