cert-manager/cmd/ingress-shim
jetstack-ci-bot 721a4042cd
Merge pull request #327 from ocadotechnology/wip-293
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>.

fix: Use ConfigMaps for leaderelection

**What this PR does / why we need it**:
Use ConfigMaps for leader election. Improves scalability by not modifying Endpoints, which are watched by kube-proxy.

**Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes #293

**Special notes for your reviewer**:

**Release note**:

```release-note
action required: Before upgrading, scale the cert-manager Deployment to 0, to avoid two controllers attempting to operate on the same resources
```
2018-02-21 18:22:27 +00:00
..
controller Add test cases for falsey tls-acme annotation values 2018-02-21 11:00:21 -06:00
options Add ingress-shim controller to create Certificates based on annotations on ingress resources 2017-11-30 22:53:54 +00:00
app.go fix: Use ConfigMaps for leaderelection 2018-02-21 17:48:13 +00:00
main.go Add ingress-shim controller to create Certificates based on annotations on ingress resources 2017-11-30 22:53:54 +00:00
README.md Add ingress-shim controller to create Certificates based on annotations on ingress resources 2017-11-30 22:53:54 +00:00
start.go Add ingress-shim controller to create Certificates based on annotations on ingress resources 2017-11-30 22:53:54 +00:00

ingress-shim

This is a small binary that can be run alongside any cert-manager deployment in order to automatically create Certificate resources for Ingresses when a particular annotation is found on an ingress resource.

This allows users to consume certificates from cert-manager without having to manually create Certificate resources, i.e. in a similar fashion to kube-lego.

It has been developed outside of the core of cert-manager as it is an experiment to assess the best way to implement this sort of functionality.

Project status

This project is experimental, and thus should not be relied upon in a production environment. This tool may change in backwards incompatible ways.

In the future, the functionality of this tool may be merged into cert-manager itself to provide a more seamless experience for users.