Home for Cluster API, a subproject of sig-cluster-lifecycle
C-Rank Grade: A (Welcoming) - 68/100
External PR Merge Rate: 78%
Response Time: 14h
First Timer Success: 61%
kubernetes-sigs/cluster-api has a recorded first-timer success rate of 60.6%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in kubernetes-sigs/cluster-api respond to incoming external pull requests in approximately 13.6 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 67.9 places kubernetes-sigs/cluster-api in the A tier.
The external contributor pull request merge rate for kubernetes-sigs/cluster-api is 77.7%, based on public PR activity from non-core contributors.
kubernetes-sigs/cluster-api currently has 4 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in kubernetes-sigs/cluster-api. Prompt code reviews with positive guidance for new contributors.
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/cluster-api?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 16:00 UTC (16:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 09:00 to 13:00 UTC (09:00 - 13:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~10 hours (96% approval). Large PRs (>500 lines) take ~70 hours (35% approval). Keep your diff compact for rapid review.
When generating release notes for v1.14.3 the release notes tool was generating the following errors ## FIXME: Consistency errors! PR number 14189 identified from commits, not found in the PR list I think the release notes tool picked up on PR 14189 (merged into main) because PR https://github.com/kubernetes-sigs/cluster-api/pull/14255/commits (merged into release-1.14) contained a link to 14189 in the commit message. Let's figure out why that happens and try to ignore PR links in commit messages.
Which jobs are flaking? periodic-cluster-api-test-main periodic-cluster-api-test-main periodic-cluster-api-test-mink8s-release-1-13 Which tests are flaking? sigs.k8s.io/cluster-api/core/reconcilers/topology/cluster TestReconcileControlPlane/Should_update_the_ControlPlane_without_machine_infrastructure_(control_plane_contract_v1beta1) Since when has it been flaking? Thrice since 28th September. Testgrid link https://storage.googleapis.com/k8s-triage/index.html?date=2026-09-29&job=.*cluster-api.*(test%7Ce2e)-(mink8s-)*&repo=cluster-api&xjob=.*-provider-.#1daa56280a6a7032792e Reason for failure (if possible) Failed === RUN TestReconcileControlPlane/Should_update_the_ControlPlane_without_machine_infrastructure_(control_plane_contract_v1beta1) I0928 20:12:03.148701 28800 reflector.go:507] "Caches populated" logger="controller-runtime.cache" type="controlplane.cluster.x-k8s.io/v1beta2, Kind=GenericControlPlane" reflector="pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:343" I
What would you like to be added (User Story)? As a cluster admin I would like to add files with defer set, so they are written after a disk is mounted. (And any other reasons why one would want to use defer in write_files of cloud-init) Detailed Description Basically, add a 'defer' field here: cluster-api/api/bootstrap/kubeadm/v1beta1/kubeadmconfig_types.go Line 303 in f7dd2c7 type File struct { and then copy the value of that field to the 'defer' field of write_files in the cloud-init config (here, I think? cluster-api/bootstrap/kubeadm/pkg/cloudinit/files.go Line 21 in f7dd2c7 write_files:{{ range . }} ) Anything else you would like to add? No response Label(s) to be applied /kind feature One or more /area label. See https://github.com/kubernetes-sigs/cluster-
We have encountered an issue where machines end up with a stale HealthCheckSucceeded=False condition that never gets cleared, even though the nodes have fully recovered and are running fine. This has been observed in two scenarios, both using a MachineHealthCheck with a remediationTemplate: "No heartbeat for 5 minutes": Node briefly reported Ready=Unknown, the health check fired, the node recovered on its own, but HealthCheckSucceeded=False persists. "Exceeded start-up time of 30m": Node eventually came up healthy after exceeding the configured startup timeout, but the failed condition was never removed. After a node recovers from such a transient health check failure: NodeHealthy=True NodeReady=True No active remediation objects exist HealthCheckSucceeded=False: this was not cleared Available=False: machine appears unavailable when it is not CAPI version used: v1.13.1 Label(s) to be applied /kind bug /area machinehealthcheck
What would you like to be added (User Story)? As an operator, I would like to be able to gracefully remove a Node and its underlying Machine/Infrastructure respecting any disruption configurations through a deletion of the Node object in the child cluster. Detailed Description CAPI supports a configurable and sophisticated deletion process for Machine objects that respect workload availability (PDB's, etc). At present, this is triggered through the deletion timestamp (metadata.deletionTimestamp) on the Machine object being set. In some environments, the operator of the CAPI infrastructure differs from the operator of the child-cluster and its resources - or, jumping across clusters is cumbersome. In this model, it is challenging for a child-cluster operator to trigger this same, safe, deletion process from the child-cluster directly. A potential solution is to (via feature flag) have CAPI configure metadata.finalizers on managed Nodes and have it react to the Node's metadata.deletion
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/cluster-api, 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/cluster-api acknowledge new external contributions in approximately 13 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 77.7% were successfully merged into the primary branch.
kubernetes-sigs/cluster-api has a recorded first-timer success rate of 60.6%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~13 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 67.9 places kubernetes-sigs/cluster-api in the Welcoming tier.
The external pull request merge rate is 77.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, kubernetes-sigs/cluster-api currently has 4 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for kubernetes-sigs/cluster-api 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.