c44a7552ea
With async challenge Check, it is often happens, that solver.Check() fails on first run after solver.Present() Cert-manager then tries again, but starts with solver.Present(), which not being idempotent right now fails on certain DNS providers. This change swaps order of solver.Check() and solver.Present(). Check is not returning error if propagation not happened, it then allows Present() to run. In the current form, Present() will be spamming with errors, but this doesn't stop Check from happening on every attempt, so eventually Challenge can be verified and accepted. In the future, Present() should be made idempotent. |
||
|---|---|---|
| .github | ||
| cmd | ||
| contrib/charts | ||
| docs | ||
| hack | ||
| pkg | ||
| test | ||
| third_party/crypto/acme | ||
| vendor | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| CODE_OF_CONDUCT.md | ||
| Gopkg.lock | ||
| Gopkg.toml | ||
| labels.yaml | ||
| LICENSE | ||
| Makefile | ||
| OWNERS | ||
| README.md | ||
cert-manager
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.
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
CustomResourceDefinitionorThirdPartyResourcesupport
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:
- Creating a simple CA based Issuer
- Creating cluster wide Issuers
- Issuing an ACME certificate using HTTP validation
- Issuing an ACME certificate using DNS validation
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.