Support delegated domains for DNS01 challenges #101
Merged
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.
What this PR does / why we need it:
If it is not desired to provide write access to the hosted zone of the certificate domain, the DNS record for DNS01 challenge cannot be written. With help of an existing CNAME DNS record the DNS challenge can be forwarded to another, accessible domain.
Example:
A certificate is requested for the domain
example.domain.com
. If by some external means a CNAME DNS record has been created for_acme-challenge.example.domain.com
with target_acme-challenge.another.domain.org
, the TXT record for the DNS01 challenge has to be written to_acme-challenge.another.domain.org
.The cert controller manager only checks for following a CNAME record, if the field
spec.followCNAME
of the certificate object is set totrue
.This feature is expected to be used only in special cases, as the CNAME record must be managed externally and individually for every domain.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note: