CertAutoPilot vs cert-manager
cert-manager is the open-source Kubernetes controller that obtains certificates and keeps them in Kubernetes Secrets. It is excellent at that job. CertAutoPilot is a central platform for certificates across the whole infrastructure, Kubernetes included. Many organisations will run both.
| CertAutoPilot | cert-manager | |
|---|---|---|
| Where it runs | A central service (Linux, Docker, Kubernetes or an appliance) | Inside each Kubernetes cluster |
| Where certificates go | 21 targets: Kubernetes Secrets, IIS, Windows, Exchange, F5 BIG-IP, NetScaler, A10 Thunder, PAN-OS, FortiWeb, FortiGate, Vault, Azure Key Vault, AWS ACM, Cloudflare, SSH hosts and more | Kubernetes Secrets (consumed by Ingress, Gateway API and pods) |
| Certificate authorities | ACME (public and private CAs), Microsoft AD CS | ACME, Vault, Venafi, CA and self-signed issuers; other CAs through external issuer projects |
| Discovering existing certificates | Network, DNS zone, cloud DNS and Certificate Transparency discovery | Not in scope |
| Interface | Web UI, REST API, approvals, role-based access, audit log | Kubernetes resources (kubectl, GitOps) |
| Multi-cluster view | One inventory across clusters and non-Kubernetes systems | Per cluster |
| Licence | Free tier with every feature; Enterprise by certificate count | Open source (Apache 2.0), CNCF project |
When cert-manager is the right choice
If your certificates live only in Kubernetes and your team already manages everything as Kubernetes resources through GitOps, cert-manager does the job with no extra service to run.
When CertAutoPilot fits better
- Certificates also have to reach systems outside Kubernetes: Windows servers, load balancers, firewalls, CDNs or key vaults.
- Certificates come from Microsoft AD CS as well as ACME.
- You need one inventory, with discovery of certificates nobody registered, across clusters and data centres.
- Security or audit teams need approvals, per-resource access control and a tamper-evident audit trail outside the cluster.
Using both
CertAutoPilot's Kubernetes target writes TLS Secrets and can restart the workloads that mount them, so it can own certificates that also have to exist elsewhere, such as a wildcard certificate shared by an Ingress and an F5 virtual server. It can also find Secrets that already hold a certificate by its names, while leaving Secrets that cert-manager owns alone. cert-manager can keep issuing the cluster-only certificates.
Questions
Does CertAutoPilot replace cert-manager?
Not necessarily. cert-manager is a good fit for certificates that only live inside one Kubernetes cluster. CertAutoPilot is for certificates that must reach systems outside Kubernetes, come from AD CS, or need a central inventory, approvals and audit.
Will CertAutoPilot overwrite Secrets that cert-manager manages?
Not by default. When it finds Secrets by certificate name it skips Secrets that another controller owns (cert-manager, Helm or an owner reference) unless you explicitly include them.
Does CertAutoPilot need an agent in the cluster?
No. It talks to the Kubernetes API with a kubeconfig credential, or uses the in-cluster service account when CertAutoPilot itself runs in that cluster.
Run it on your own infrastructure. The free tier includes every feature.
Talk to us →