Go to file
Tim Ramlot d866ee5025
refactor Acme.Setup: get rid of confusing defer logic
Signed-off-by: Tim Ramlot <42113979+inteon@users.noreply.github.com>
2025-07-12 12:26:26 +02:00
.github BOT: run 'make upgrade-klone' and 'make generate' 2025-05-14 00:27:56 +00:00
cmd refactor ACME registry (part 1) 2025-07-09 00:21:39 +02:00
deploy Revert "More fine-grained control over powerful RBAC permission granted via Helm chart" 2025-07-02 12:01:02 +02:00
design spelling: e.g. 2025-05-07 22:05:43 -04:00
docs Remove docs/ directory and replace with basic README 2020-01-20 14:53:02 +00:00
gcb Use a better supported machine type 2024-09-26 11:44:32 +01:00
hack BOT: run 'make upgrade-klone' and 'make generate' 2025-04-10 10:33:27 +00:00
internal Merge pull request #7844 from erikgb/cleanup-sign 2025-07-09 19:33:28 +00:00
logo Delete mask 2022-05-05 12:05:27 -04:00
make Merge pull request #7857 from SgtCoDFish/run-third-party-tests 2025-07-14 15:05:34 +00:00
pkg refactor Acme.Setup: get rid of confusing defer logic 2025-07-12 12:26:26 +02:00
test Merge pull request #7851 from inteon/ginkgo_context 2025-07-11 11:29:30 +00:00
third_party Switch to the cert-manager/crypto fork which contains @sigmavirus24's ACME profiles patch 2025-06-04 15:20:59 +01:00
tools remove tools/cobra script 2023-03-06 14:21:31 +00:00
.clomonitor.yml add document that links clo monitor to the LICENSES file 2023-09-27 13:45:54 +02:00
.gitignore remove deprecated files and functions 2024-02-08 10:45:06 +01:00
.golangci.yaml make upgrade-klone generate-golangci-lint 2025-06-03 20:21:20 +01:00
.trivyignore ignore CVE-2020-8559 in trivy scans 2024-04-25 09:58:47 +01:00
CODE_OF_CONDUCT.md replace governance documents with links to the cert-manager community documents 2023-09-27 13:45:14 +02:00
CONTRIBUTING.md Simplify the CONTRIBUTING.md document 2022-03-10 10:57:59 +00:00
go.mod use sigs.k8s.io/randfill instead of github.com/google/gofuzz 2025-06-06 16:11:48 +02:00
go.sum upgrade go dependencies 2025-06-06 16:11:48 +02:00
GOVERNANCE.md replace governance documents with links to the cert-manager community documents 2023-09-27 13:45:14 +02:00
klone.yaml BOT: run 'make upgrade-klone' and 'make generate' 2025-07-12 00:27:57 +00:00
LICENSE move to Makefile modules 2024-04-10 18:53:40 +02:00
LICENSES use licenses makefile module to generate LICENSES files 2025-07-04 15:38:36 +02:00
Makefile BOT: run 'make upgrade-klone' and 'make generate' 2024-08-30 00:22:20 +00:00
OWNERS Add Ali as a reviewer 2025-05-30 11:36:05 +01:00
OWNERS_ALIASES BOT: run 'make upgrade-klone' and 'make generate' 2024-11-26 01:37:56 +00:00
README.md link: cert-manager-dev Google Group 2025-02-18 13:20:13 -05:00
RELEASE.md Fix typos 2024-09-20 09:27:03 +10:00
ROADMAP.md move roadmap to community repo 2024-05-09 17:47:12 +01:00
SECURITY_CONTACTS.md replace governance documents with links to the cert-manager community documents 2023-09-27 13:45:14 +02:00
SECURITY.md replace governance documents with links to the cert-manager community documents 2023-09-27 13:45:14 +02:00
USERS.md replace governance documents with links to the cert-manager community documents 2023-09-27 13:45:14 +02:00

cert-manager project logo

Build Status Go Report Card
Artifact Hub Scorecard score CLOMonitor

cert-manager

cert-manager adds certificates and certificate issuers as resource types in Kubernetes clusters, and simplifies the process of obtaining, renewing and using those certificates.

It supports issuing certificates from a variety of sources, including Let's Encrypt (ACME), HashiCorp Vault, and Venafi TPP / TLS Protect Cloud, as well as local in-cluster issuance.

cert-manager also ensures certificates remain valid and up to date, attempting to renew certificates at an appropriate time before expiry to reduce the risk of outages and remove toil.

cert-manager high level overview diagram

Documentation

Documentation for cert-manager can be found at cert-manager.io.

For the common use-case of automatically issuing TLS certificates for Ingress resources, see the cert-manager nginx-ingress quick start guide.

For a more comprehensive guide to issuing your first certificate, see our getting started guide.

Installation

Installation is documented on the website, with a variety of supported methods.

Developing cert-manager

We actively welcome contributions and we support both Linux and macOS environments for development.

Different platforms have different requirements; we document everything on our Building cert-manager website page.

Note in particular that macOS has several extra requirements, to ensure that modern tools are installed and available. Read the page before getting started!

Troubleshooting

If you encounter any issues whilst using cert-manager, we have a number of ways to get help:

If you believe you've found a bug and cannot find an existing issue, feel free to open a new issue! Be sure to include as much information as you can about your environment.

Community

The cert-manager-dev Google Group is used for project wide announcements and development coordination. Anybody with a Google account can join the group by visiting the group and clicking "Join Group".

Meetings

We have several public meetings which any member of our Google Group is more than welcome to join!

Check out the details on our website. Feel free to drop in and ask questions, chat with us or just to say hi!

Contributing

We welcome pull requests with open arms! There's a lot of work to do here, and we're especially concerned with ensuring the longevity and reliability of the project. The contributing guide will help you get started.

Coding Conventions

Code style guidelines are documented on the coding conventions page of the cert-manager website. Please try to follow those guidelines if you're submitting a pull request for cert-manager.

Importing cert-manager as a Module

⚠️ Please note that cert-manager does not currently provide a Go module compatibility guarantee. That means that most code under pkg/ is subject to change in a breaking way, even between minor or patch releases and even if the code is currently publicly exported.

The lack of a Go module compatibility guarantee does not affect API version guarantees under the Kubernetes Deprecation Policy.

For more details see Importing cert-manager in Go on the cert-manager website.

The import path for cert-manager versions 1.8 and later is github.com/cert-manager/cert-manager.

For all versions of cert-manager before 1.8, including minor and patch releases, the import path is github.com/jetstack/cert-manager.

Security Reporting

Security is the number one priority for cert-manager. If you think you've found a security vulnerability, we'd love to hear from you.

Follow the instructions in SECURITY.md to make a report.

Changelog

Every release on GitHub has a changelog, and we also publish release notes on the website.

History

cert-manager is loosely based upon the work of kube-lego and has borrowed some wisdom from other similar projects such as kube-cert-manager.

Logo design by Zoe Paterson