Step Issuer

Step Issuer is a Kubernetes cert-manager CertificateRequest controller that uses a step-ca online certificate authority to sign internal certificates for…

  • Infrastructure
  • Security
  • Tools & Utilities
Step Issuer is a Kubernetes cert-manager CertificateRequest controller that uses a step-ca online certificate authority to sign internal certificates for ingresses and other Kubernetes resources.

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.

56/100 Fair

Maintained
88last commit 5 days ago
Popular
49269 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data
Security check
201 serious finding, 3 minor, CI, tests, OpenSSF Scorecard 6.4/10

Based on 4 of 5 factors.

Availability: platform listings confirmed today

GitHub stars
269
Open issues
14
Last commit
2026-11-16
Latest release
v0.12.0
License
Apache-2.0
Activity
rising

Checked 3 days ago - source: GitHub (smallstep/step-issuer)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Check AWS credentials and port 8083 Before starting Step Functions Local, make sure AWS credentials are available, such as the AWS_ACCESS_KEY_ID and AWS_SECRET_KEY environment variables or a saved default AWS profile. The local server starts on port 8083, so missing credentials can break AWS calls and a blocked port can stop other apps from reaching it. source
  • Before you begin Install step-ca and cert-manager v1.0.0 or higher in the Kubernetes cluster before deploying step-issuer. source

Fetched 41 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Is step-issuer compatible with cert-manager?

Yes, it is implemented as a cert-manager CertificateRequest controller.

Which CA signs the certificates it requests?

It uses the step-ca online CA to sign certificate requests.

Can it provide ingress certificates from an internal CA instead of Let's Encrypt?

Yes, it is designed to get certificates for ingresses and other Kubernetes resources from an internal CA instead of Let's Encrypt.

Where can I report problems with step-issuer?

The project has a GitHub issues page for step-issuer.

Answers sourced from github.com, github.com

Community

Collected 48 days ago - public community threads