Description of problem:
Deleting a ClusterIngress using the Cloud highAvailability type (e.g. the default router) orphans any corresponding wildcard DNS records in the cluster's public and private zones.
Version-Release number of selected component (if applicable):
Create a new cluster and `oc delete -n openshift-ingress-operator clusteringresses/default`
Wildcard DNS records for the ingress domain still exist in the Route53 public and private zones for the cluster.
The wildcard DNS records should be deleted when the clusteringress is deleted.
verified with 4.0.0-0.nightly-2019-02-20-194410 and the issue has been fixed.
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.