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`. ``` |
||
|---|---|---|
| .. | ||
| rbac | ||
| without-rbac | ||
| README.md | ||
Deployment files
This directory contains example deployment manifests for cert-manager that can be used in place of the official Helm chart.
This is useful if you are deploying cert-manager into an environment without Helm, or want to inspect a 'bare minimum' deployment.
Where do these come from?
The manifests in these subdirectories are generated from the Helm chart
automatically. The values.yaml files used to configure cert-manager can be
found in hack/deploy.
They are automatically generated by running ./hack/update-deploy-gen.sh.