Add acme-agent to clients list - #2302
Open
tmhal5l13 wants to merge 1 commit into
Open
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Adding acme-agent to the client list.
A centralized ACME renewal hub for organizations not running Kubernetes: DNS provider credentials stay on one hub, each spoke generates its own key locally and drives its own ACME order via DNS-01, relayed through the hub. Private keys never leave the spoke that generated them.
Since this PR was opened: added config hot-reload (
SIGHUP, no restart needed to add a spoke or rotate DNS provider credentials) and a low-friction spoke enrollment flow (acme-hub --generate-token/acme-spoke --load-token) that removes manual file-copying from spoke setup entirely.