cert-manager Review (2026): Pricing, Features & Honest Verdict

Reviewed by MakerStack · Published · 4 min read

TLDR

cert-manager automates TLS certificate management for Kubernetes clusters, handling issuance and renewal from providers like Let’s Encrypt and Venafi. Best for: DevOps teams running production K8s workloads. Price: Free (open source). Rating: 7.9/10

What is cert-manager?

cert-manager is a CNCF project that adds certificate management capabilities to Kubernetes. It creates TLS certificates, handles renewals automatically, and integrates with issuers like Let’s Encrypt, HashiCorp Vault, and Venafi. With over 12,000 GitHub stars, it has become the de facto standard for TLS automation in the Kubernetes ecosystem.

The project uses Kubernetes-native Custom Resource Definitions (CRDs) to define certificate requirements declaratively. You specify what certificates you need through YAML manifests, and cert-manager handles the entire ACME challenge flow, private key generation, and certificate rotation behind the scenes.

Key Features

ACME Protocol Support

Full implementation of the ACME protocol for automated certificate issuance. Supports both HTTP-01 and DNS-01 challenge types, letting you validate domain ownership through either web server responses or DNS records. The DNS-01 solver works with dozens of DNS providers out of the box.

Multiple Issuer Types

Beyond Let’s Encrypt, cert-manager supports CA issuers (your own certificate authority), self-signed certificates, Vault PKI, Venafi, and external issuers through a plugin interface. You can run different issuers for different namespaces or environments.

Certificate Lifecycle Management

Automatic renewal kicks in before certificates expire (configurable threshold, defaults to 2/3 of the certificate lifetime). Failed renewals trigger Kubernetes events and can integrate with alerting systems. The Certificate resource tracks the full history of issuance attempts.

Ingress Integration

Annotate your Ingress resources and cert-manager automatically provisions matching certificates. Works with nginx-ingress, Traefik, Istio, and other ingress controllers. One annotation on an Ingress object, and TLS is handled.

Trust Manager

A companion project (trust-manager) distributes trust bundles across your cluster. Useful when you run internal CAs and need all workloads to trust your root certificates without baking them into container images.

Pricing

cert-manager is completely free and open source under the Apache 2.0 license. There are no paid tiers, no enterprise editions, and no usage limits. The CNCF backing means the project has sustainable funding without needing to monetize users directly.

Pros

  • Fully automated certificate lifecycle from issuance through renewal
  • Native Kubernetes integration through CRDs feels right at home in K8s workflows
  • Massive community adoption means excellent documentation and Stack Overflow coverage
  • CNCF graduated project with long-term maintenance guarantees
  • Supports practically every certificate authority and DNS provider

Cons

  • Initial setup complexity can overwhelm teams new to Kubernetes operators
  • Debugging failed ACME challenges requires understanding of DNS propagation and HTTP routing
  • Resource overhead adds 3-4 pods to your cluster for the controller, webhook, and cainjector
  • DNS-01 challenge configuration varies wildly across providers with inconsistent documentation
PlanPricePlan FeaturesBest For
Open SourceFreeUnlimited certificates, all issuer types, full ACME support, community supportEveryone

Who Should Use cert-manager?

Any team running Kubernetes in production that needs TLS certificates. If you are manually managing certificates or using init containers to fetch them, cert-manager replaces all of that with a declarative, automated approach. It is particularly valuable for teams managing multiple clusters or namespaces where certificate management would otherwise become a full-time job.

Solo developers running a single-node K8s cluster might find the setup overhead disproportionate. For simpler setups, Traefik’s built-in ACME support or Caddy’s automatic HTTPS could be a better fit.

Alternatives

Traefik

Traefik includes built-in ACME certificate management as part of its ingress controller. If you are already using Traefik, you get Let’s Encrypt certificates without installing anything extra. The trade-off is less flexibility with non-ACME issuers and no certificate CRD abstraction.

Caddy

Caddy automatically provisions and renews TLS certificates for any domain it serves. It is simpler than cert-manager but operates at the web server level rather than the Kubernetes level. Good for smaller deployments where you do not need cluster-wide certificate management.

AWS ACM

AWS Certificate Manager provides free TLS certificates for AWS resources. If your Kubernetes cluster runs on EKS with AWS load balancers, ACM handles certificates at the load balancer level. It locks you into AWS but eliminates the need for in-cluster certificate management entirely.

FAQ

Does cert-manager work with non-Kubernetes environments?

No. cert-manager is built specifically for Kubernetes and requires a running cluster. For non-K8s environments, look at tools like certbot, acme.sh, or Caddy.

How does cert-manager handle rate limits from Let’s Encrypt?

cert-manager respects Let’s Encrypt rate limits and will back off automatically when limits are hit. For testing, you can configure a staging issuer that uses Let’s Encrypt’s staging environment, which has much higher rate limits.

Can I use cert-manager with wildcard certificates?

Yes, but wildcard certificates require DNS-01 challenges. You will need to configure a DNS provider that cert-manager supports and set up the appropriate credentials for DNS record management.

cert-manager Pros & Cons

What We Like

  • Fully automated certificate lifecycle from issuance through renewal
  • Native Kubernetes integration through CRDs
  • Massive community with excellent documentation
  • CNCF graduated project with long-term maintenance
  • Supports practically every CA and DNS provider

What Could Be Better

  • Initial setup complexity for teams new to K8s operators
  • Debugging failed ACME challenges requires deep knowledge
  • Adds 3-4 pods of resource overhead to your cluster
  • DNS-01 config varies wildly across providers

cert-manager FAQ

Does cert-manager work with non-Kubernetes environments?

No. cert-manager is built specifically for Kubernetes. For non-K8s environments, use certbot, acme.sh, or Caddy.

How does cert-manager handle Let's Encrypt rate limits?

cert-manager respects rate limits and backs off automatically. Use a staging issuer for testing, which has much higher limits.

Can I use cert-manager with wildcard certificates?

Yes, but wildcard certificates require DNS-01 challenges with a supported DNS provider configured.

What is cert-manager?

Automated TLS certificate management for Kubernetes. Handles issuance, renewal, and rotation from providers like Let's Encrypt, Venafi, and custom CAs through Kubernetes-native CRDs.

How much does cert-manager cost?

cert-manager pricing starts at Free (open source). A free plan is available.

Is cert-manager worth it?

cert-manager is the Kubernetes standard for TLS certificate automation. Setup takes effort, but once running it eliminates certificate management as a concern entirely. Essential for any serious K8s deployment. We rate it 7.9/10.

Disclosure: MakerStack is funded by featured placement fees, sponsor slots and a small number of affiliate links. Nobody paid for this review. Where any of those does apply to a review, we say so on the page. The scoring criteria are the same in every case. See our editorial policy.

This review describes cert-manager as we tested it on March 20, 2026. Pricing, plans and features may have changed since. We don't update reviews on request; see our update policy.