cert-manager-webhook
The cert-manager webhook is a component of cert-manager that serves ACME (Automatic Certificate Management Environment) HTTP-01 domain-ownership validation…
Platform availability
Available on 0 of 10 platforms
- Unraid (not listed)
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm (not listed)
- 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.
77/100 Good
- Maintained
- 100last commit 16 days ago
- Popular
- 8314,149 GitHub stars
- Easy to install
- 250 install platforms, install notes, Docker image
- Light to run
- No data
Based on 3 of 4 factors.
- GitHub stars
- 14,149
- Open issues
- 277
- Last commit
- 2026-11-05
- Latest release
- v1.21.3
- License
- Apache-2.0
- Activity
- declining
Checked 16 days ago - source: GitHub (cert-manager/cert-manager)
Resources & Compatibility
Requirements not published yet.
Checked 23 days ago - source: Docker Hub image tags and published docs
First-install notes
- Install cert-manager with official YAML Use kubectl apply -f to install the official cert-manager.yaml, because cert-manager-webhook is only one part of the stack and needs the other components plus CRDs (Kubernetes object definitions). This gives you a standard starting setup without extra package-manager tools. source
- Use Helm OCI if you prefer packages If you already use Helm (a Kubernetes package manager), install the official chart from the OCI registry (a package repository) with --create-namespace and --set crds.enabled=true. That creates the cert-manager namespace and enables the CRDs needed by the webhook and certificate objects. source
- Legacy Helm path needs a repo add If you are following the legacy Helm instructions, add the Jetstack repository with helm repo add before running helm install. This step gives Helm the address of the chart repository, and skipping it makes the install fail. source
Fetched 53 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
Can I deploy only cert-manager-webhook?
No. cert-manager-webhook is only one part of the stack, and it needs the other cert-manager components plus the CRDs.
What causes the 'failed calling webhook webhook.cert-manager.io' error?
It is tied to installation-related causes. Check the cert-manager troubleshooting documentation for the webhook.
Why does the cert-manager webhook readiness probe fail after deleting its namespace?
Deleting the namespace can leave the webhook failing readiness when the same configuration is redeployed. The reported workaround is to delete the deployment cleanly, starting with the operator and then deleting the CRDs.
What should I check when cert-manager resources cannot be created or updated because the webhook is unreachable?
Check the compatibility of your environment and take the necessary action. This is the advice given when the webhook is unreachable.
Answers sourced from cert-manager.io, cert-manager.io, stackoverflow.com, www.reddit.com
Community
- Issues with DNS resolution of cert-manager webhook (forum)
- How can I fix 'failed calling webhook "webhook.cert-manager.io"'? (forum)
Collected 48 days ago - public community threads