Go to file
2017-10-24 13:43:59 +02:00
.github Create ISSUE_TEMPLATE.md 2017-10-23 21:15:01 +01:00
cmd Make acmesolver image configurable through CLI. Use tagged version as default. 2017-10-13 16:39:06 +01:00
contrib/charts/cert-manager Update rbac.yaml 2017-10-18 14:01:35 +01:00
docs Added comments for using hostedZoneID field with route53 provider 2017-10-24 13:43:59 +02:00
hack Refactor e2e setup into scripts. Speed up e2e tests. 2017-10-16 12:58:47 +01:00
pkg Consistent use of glog 2017-10-16 14:50:27 +01:00
test Verify TLS certificate is produced in certificate_ca tests 2017-10-16 15:43:39 +01:00
vendor Update vendor 2017-10-11 17:24:50 +01:00
.dockerignore Ignore folders for building docker image 2017-08-12 14:55:11 +01:00
.gitignore Update .gitignore 2017-08-07 21:03:17 +01:00
.gitlab-ci.yml Make acmesolver image configurable through CLI. Use tagged version as default. 2017-10-13 16:39:06 +01:00
.travis.yml Set travis go_import_path 2017-10-23 19:44:39 +01:00
CODE_OF_CONDUCT.md Create CODE_OF_CONDUCT.md 2017-10-23 00:16:10 +01:00
Dockerfile.acmesolver Enable gitlab-ci 2017-08-14 11:12:55 +01:00
Dockerfile.controller Enable gitlab-ci 2017-08-14 11:12:55 +01:00
Gopkg.lock Add Prometheus metrics server 2017-10-11 17:24:26 +01:00
Gopkg.toml Update vendor/ 2017-08-05 00:36:25 +01:00
labels.yaml Add provider labels. Clean up old labels. 2017-10-23 21:18:57 +01:00
LICENSE add apache 2.0 license 2017-07-22 12:04:24 +01:00
Makefile Add ACME certificate http01 e2e test 2017-10-16 12:58:21 +01:00
OWNERS Create OWNERS 2017-10-23 19:37:48 +01:00
README.md Wrap at 80 chars 2017-10-24 00:13:19 +01:00

cert-manager Build Status

cert-manager is a Kubernetes add-on to automate the management and issuance of TLS certificates from various issuing sources.

It will ensure certificates are valid and up to date periodically, and attempt to renew certificates at an appropriate time before expiry.

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

cert-manager high level overview diagram

Current status

This project is not yet ready to be a component in a critical production stack, however it is at a point where it offers comparable features to other projects in the space. If you have a non-critical piece of infrastructure, or are feeling brave, please do try cert-manager and report your experience here in the issue section.

NOTE: currently we provide no guarantees on our API stability. This means there may be breaking changes that will require changes to all Issuer/Certificate resources you have already created. We aim to provide a stable API after a 1.0 release.

Quickstart

Prebuilt images for cert-manager are made available on Dockerhub.

Pre-requisites

  • Kubernetes cluster with CustomResourceDefinition or ThirdPartyResource support

Deploying cert-manager

The easiest way to deploy cert-manager into your cluster is to use the Helm chart. For information on how to do this see the Deploying cert-manager using Helm user guide.

Creating your first Issuer and Certificate

An Issuer in cert-manager describes a source of X.509 certificates. A Certificate in cert-manager defines a desired X.509 certificate. Below is a list of user guides that can be used to get started with both resources:

Further documentation

For further documentation, please check the /docs directory in this repository.

Troubleshooting

If you encounter any issues whilst using cert-manager, and your issue is not documented, please file an issue.

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.

Please take a look at our issue tracker if you are unsure where to start with getting involved!

We also use the #kube-lego channel on kubernetes.slack.com for chat relating to the project.

Developer documentation should be available soon at docs/devel.

Changelog

The list of releases is the best place to look for information on changes between releases.