This repository has been archived by the owner on Aug 26, 2021. It is now read-only.
add support for running multiple instance of kube-lego in the cluster #105
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… watching their own annotation and getting certificate from their corresponding LE provider
gurvindersingh
changed the title
simonswine
approved these changes
Mar 13, 2017
|
Thanks, that should work. |
Closed
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This enables kube-lego to watch its configured annotation and getting certificate from corresponding LE provider.
For running with staging LE, the annotation can be the default one or
kubernetes.io/tls-acme-stagingand for productionkubernetes.io/tls-acme-production. This will avoid people running into unnecessary LE rate limit by avoiding asking for certs from production until they really need it.This will close #50