Declarative node readiness for Kubernetes - gate scheduling with taints until node infrastructure (CNI, GPU, storage, custom checks) is actually ready.
C-Rank Grade: A (Welcoming) - 61/100
External PR Merge Rate: 56%
Response Time: 1d
First Timer Success: 58%
kubernetes-sigs/node-readiness-controller has a recorded first-timer success rate of 58.3%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in kubernetes-sigs/node-readiness-controller respond to incoming external pull requests in approximately 25.2 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 60.6 places kubernetes-sigs/node-readiness-controller in the A tier.
The external contributor pull request merge rate for kubernetes-sigs/node-readiness-controller is 55.8%, based on public PR activity from non-core contributors.
kubernetes-sigs/node-readiness-controller currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in kubernetes-sigs/node-readiness-controller. 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/node-readiness-controller?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 13:00 UTC (13:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 13:00 to 17:00 UTC (13:00 - 17:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (70% approval). Large PRs (>500 lines) take ~121 hours (25% approval). Keep your diff compact for rapid review.
Implement a Node Problem Detector (NPD) custom plugin that runs a probe (similar to kubelet probes) and returns exit code 0/1 to indicate readiness. This allows operators who are familiar with pod readiness/liveness probes to reuse that configuration style for node-level readiness reporting. Reuses a familiar probe model so users can express readiness checks the same way they already do for pods. Can be deployed as an NPD plugin (lightweight go-lang binary to give exit status as per NPD requirements). This can be integrated into node-readiness-controller example (#125) in the future. Proposal: Add documentation and an example NPD plugin that: Accepts probe configuration (HTTP/TCP like semantics) similar to kubelet probes. Runs on the node and exits with code 0 for healthy, 1 for unhealthy. Emits basic logs. Provide example config / NPD plugin manifest to demonstrate usage. Acceptance criteria: A new example npd plugin implementation in examples/ or cmd/ that demonstrates an HTT
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/node-readiness-controller, 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/node-readiness-controller acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 55.8% were successfully merged into the primary branch.
kubernetes-sigs/node-readiness-controller has a recorded first-timer success rate of 58.3%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 days+. 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 60.6 places kubernetes-sigs/node-readiness-controller in the Welcoming tier.
The external pull request merge rate is 55.8%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, kubernetes-sigs/node-readiness-controller currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for kubernetes-sigs/node-readiness-controller 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.