010e6c87e4
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 Endpoints back into the cert-manager RBAC policy **What this PR does / why we need it**: Adds permission to CRUD Endpoints resources back into the cert-manager RBAC role. This is to prevent deployments using the 'master' version of the Helm chart failing when deploying a pre-0.3 (unreleased) release of cert-manager. We will remove this in 0.4. This is in order to reduce friction for new users if they forget/decide not to use a tagged release of the Helm chart. **Release note**: ```release-note NONE ``` /cc @davecheney @mikebryant |
||
|---|---|---|
| .. | ||
| 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).