Description of problem:
(copy and pasted from https://issues.redhat.com/browse/NE-226)
on Azure currently we use DNSZone resource with type `Private` to store the DNS records private to the cluster.
There are certain shortcomings with this resource when using type `Private`
1) This has been deprecated by Azure for Private DNS Zones preview
2) This does not allow attaching itself to pre-existing Virtual Networks
The new resource Private DNS Zone solves all the shortcoming of the previous generation and is required for Installing OpenShift in pre-exisiting VNets in Azure.
The ingress-operator will need to support the `.spec.privateZone.id` to be either of the 2 resources.
The long-term goal is to migrate 4.2 clusters to new resource, but for 4.3 we are only required to support the install time choice, i.e. the change of this ID in-cluster as day-2 does not need to be supported.
Migration epic is here https://docs.google.com/document/d/1j5pJbmAQ4-FVR2H0S5OWAaX7rImBcPP0RC-uLlM1WrE/edit#heading=h.9khfep37qdjo
PR for ingress operator: https://github.com/openshift/cluster-ingress-operator/pull/344
PR for installer: https://github.com/openshift/installer/pull/2825
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.