This change maintains backwards compatibility, but makes the `accessKeyID` and `secretAccessKeySecretRef` fields of the `route53` DNS provider optional. If not provided, AWS credentials will be loaded from `AWS_*` environment variables or the EC2 metadata service. This should also work for things that impersonate the EC2 metadata service, such as [kube2iam](https://github.com/jtblin/kube2iam) and [kail](https://github.com/uswitch/kiam). Signed-off-by: Matt Moyer <moyer@heptio.com> |
||
|---|---|---|
| .. | ||
| api-types | ||
| deploy | ||
| devel | ||
| examples | ||
| user-guides | ||
| high-level-overview.png | ||
| README.md | ||
cert-manager documentation
This is the extended documentation page for cert-manager, containing detailed specification of API types, user guides, and developer documentation.
It is split into these three sections for easier navigation.
API types
User guides
- Deploying cert-manager using Helm
- Migrating from kube-lego
- ingress-shim configuration and usage
- Creating a simple CA based issuer
- Creating cluster wide issuers
- Issuing an ACME certificate using HTTP validation
- Issuing an ACME certificate using DNS validation
Developer docs
Developer documentation can be found in the devel/ directory (coming soon).