mirrors/external-dns
1
0
Fork 0
mirror of https://github.com/kubernetes-sigs/external-dns.git synced 2025-08-06 09:36:58 +02:00
Code Issues Packages Projects Releases Wiki Activity

Update registry description in FAQ

Browse Source 
The current wording of the FAQ implies that the registry option is enabled by default, which can lead to users losing data. This change updates the registry description to make obvious that this is a supported configuration option, but not a default one.
This commit is contained in:
Jeff Goldschrafe 2022-02-05 14:31:40 -05:00 committed by GitHub
parent 261bcadd7c
commit 585536fbaf
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/faq.md
View File

@ -88,7 +88,7 @@ ExternalDNS will allow you to opt into any Services and Ingresses that you want
### I'm afraid you will mess up my DNS records!
ExternalDNS since v0.3 implements the concept of owning DNS records. This means that ExternalDNS will keep track of which records it has control over, and will never modify any records over which it doesn't have control. This is a fundamental requirement to operate ExternalDNS safely when there might be other actors creating DNS records in the same target space.
Since v0.3, ExternalDNS can be configured to use an ownership registry. When this option is enabled, ExternalDNS will keep track of which records it has control over, and will never modify any records over which it doesn't have control. This is a fundamental requirement to operate ExternalDNS safely when there might be other actors creating DNS records in the same target space.
For now ExternalDNS uses TXT records to label owned records, and there might be other alternatives coming in the future releases.