The External DNS Operator deploys and manages ExternalDNS to provide name resolution for services and routes from the external DNS provider to OKD.
|
The External DNS Operator is only supported on the |
These release notes track the development of the External DNS Operator in OKD.
The following advisory is available for the External DNS Operator version 1.3.0:
This update includes a rebase to the 0.14.2 version of the upstream project.
Previously, the ExternalDNS Operator could not deploy operands on HCP clusters. With this release, the Operator deploys operands in a running and ready state. (OCPBUGS-37059)
Previously, the ExternalDNS Operator was not using RHEL 9 as its building or base images. With this release, RHEL9 is the base. (OCPBUGS-41683)
Previously, the godoc had a broken link for Infoblox provider. With this release, the godoc is revised for accuracy. Some links are removed while some other are replaced with GitHub permalinks. (OCPBUGS-36797)
The following advisory is available for the External DNS Operator version 1.2.0:
The External DNS Operator now supports AWS shared VPC. For more information, see Creating DNS records in a different AWS Account using a shared VPC.
The update strategy for the operand changed from Rolling to Recreate. (OCPBUGS-3630)
The following advisory is available for the External DNS Operator version 1.1.1:
This release included a rebase of the operand from the upstream project version 0.13.1. The following advisory is available for the External DNS Operator version 1.1.0:
Previously, the ExternalDNS Operator enforced an empty defaultMode value for volumes, which caused constant updates due to a conflict with the OpenShift API. Now, the defaultMode value is not enforced and operand deployment does not update constantly. (OCPBUGS-2793)
The following advisory is available for the External DNS Operator version 1.0.1:
The following advisory is available for the External DNS Operator version 1.0.0:
Previously, the External DNS Operator issued a warning about the violation of the restricted SCC policy during ExternalDNS operand pod deployments. This issue has been resolved. (BZ#2086408)