Kubelet CSR Approver

A Kubernetes controller that automatically approves kubelet-serving Certificate Signing Requests (CSRs) after validating them against configurable,…

  • Infrastructure
  • Tools & Utilities
A Kubernetes controller that automatically approves kubelet-serving Certificate Signing Requests (CSRs) after validating them against configurable, provider-specific rules to prevent certificate forgery on cluster nodes.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

69/100 Good

Maintained
88last commit 19 days ago
Popular
49281 GitHub stars
Easy to install
251 install platform, install notes
Light to run
No data
Security check
100no serious findings, CI, tests

Based on 4 of 5 factors.

Availability: platform listings confirmed today

GitHub stars
281
Open issues
6
Last commit
2026-11-02
Latest release
v1.2.15
License
MIT
Activity
steady

Checked 14 days ago - source: GitHub (postfinance/kubelet-csr-approver)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Install it with Helm first Add the project's Helm (a Kubernetes package installer) repository and run the install command for the kubelet-csr-approver chart, using kube-system as the namespace. This is the supported way to place the controller in your cluster and start it. source
  • Set the allowed node rules Fill in providerRegex (the pattern for allowed node names) and providerIpPrefixes (the allowed node IP ranges) before relying on it. If these are wrong, nodes may fail to get certificates, or the approver may approve certificates for hosts you didn't intend. source
  • Set a safe certificate lifetime Set maxExpirationSeconds (the longest certificate lifetime) to a value you actually want. Also keep bypassDnsResolution set to what you intend, because it controls whether name lookups are skipped and wrong values can create less-checked certificates. source

Fetched 40 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Does kubelet-csr-approver auto-approve kubelet CSRs without validation?

No. It only auto-approves kubelet-serving CSRs that comply with configurable, provider-specific checks and verifications.

Why can a kubelet CSR be denied after a kubelet restart?

The approver can deny it when regex or IP checks fail. In the reported case, a SAN IP address was not contained in the resolved IP address set.

What existing project is kubelet-csr-approver described as being inspired by?

It is described as being inspired by existing projects such as kubelet-rubber-stamp.

What Go module name is associated with the project?

It is documented as the kubelet-csr-approver Go module from the postfinance organization.

Answers sourced from github.com, pkg.go.dev, postfinance.github.io, stackoverflow.com

Community

Collected 48 days ago - public community threads