Releases: gardener/external-dns-management
0.7.0
no release notes available
0.6.3
[external-dns-management]
Action Required
- [OPERATOR] This release replaces the former (0.6.2) one. Please do not use (f962a08)
- version 0.6.2, but this one instead.
- 0.6.2 contains an errornous fix for changing dns classes.
- It will cause problems if two dns source controllers
- are running with different dns-classes.
0.6.2
[external-dns-management]
Most notable changes
-
[OPERATOR] On AWS the hosted zones potentially usable by a set of credentials
are now filtered by the permissions for reading their record sets.
So, even if the list permission is given for all zones, only zones
whose record sets can really be read will be added to the available
zone list. (b809fa6) -
[USER] #35 @MartinWeindel
Source controller for DNS entries has been added to forward DNS entries to a target cluster.
This allows to delegate management of the DNS backend to another cluster.
Improvements
-
[OPERATOR] #35 @MartinWeindel
New flags --target-creator-label-name, --target-creator-label-value, --target-owner-id, --target-set-ignore-owners to annotate/label multiple source clusters -
[OPERATOR] #33 @ialidzhikov
Golang version is upgraded to 1.12.7. -
[OPERATOR] (cdd25bd)
fixing duplicate dns entries by source controllers after restart -
[OPERATOR] (7121962)
schedule recheck of DNS provider if error cause is external
0.6.1
0.6.0
[external-dns-management]
Improvements
- [OPERATOR] Added caching of zone state to reduce calls to DNS provider. This is especially useful for AWS Route53 to avoid running into rate throttling. Optionally the state cache is persisted to disk to avoid API calls on startup. (#29, @MartinWeindel)
0.5.5
0.5.4
0.5.3
0.5.2
0.5.1
Crash issue in Alicloud #24