362735f8f1
Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>. Add default shortNames to certificates CRD Defaults to `[cert, certs]` and is configurable with `certificateCRDShortNames` parameter. **What this PR does / why we need it**: Simplifies manual certificate management with kubectl. Fixes #311 <div name="review-notes" /> **Special notes for your reviewer**: Instead of a boolean switch do/dont include the shortNames, the value defines the aliases. This may be handy if anybody prefers `[crt, crts]` instead. I'm not too keen on the `certificateCRDShortNames` variable name. It might be better to use `Resource` instead of `CRD` to be consistent with the `createCustomResource` var. Other CRDs are probably ok without an alias, but other people workflows may differ. Should these also be configurable? In that case, the variables could be `shortNames: {certificates: [], …}`. **Release note**: ```release-note Add Certificate CRD shortnames `cert` and `certs`. This is configurable in the Helm Chart with `certificateResourceShortNames`. ``` |
||
|---|---|---|
| .. | ||
| 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).