-
Epic
-
Resolution: Done
-
Major
-
None
-
None
-
Update Control Plane readiness to include DNS readiness
-
False
-
None
-
False
-
Yellow
-
To Do
-
0% To Do, 0% In Progress, 100% Done
-
needed early January. OCM team needs time to test and change implementation on OCM. The OCM work must be completed by Feb 11 so this must be completed early Jan
-
0
-
0
-
0
-
Approved
Currently, HyperShift relies on the External DNS operator and an annotation to perform a "fire and forget" DNS configuration. The HyperShift operator makes the assumption that External DNS is working correctly, and considers a Hosted Cluster as ready without any regard to the existence or validity of the DNS records.
The HyperShift operator should include DNS record checks in its logic for readiness.
- relates to
-
OCPBUGS-8241 Cherry pick external DNS health condition to 4.12
- Closed
- links to
There are no Sub-Tasks for this issue.