-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.13, 4.12, 4.14, 4.15, 4.16, 4.17, 4.18
-
Low
-
None
-
Rejected
-
False
-
-
Release Note Not Required
-
In Progress
Description of problem:
The current "description" annotation of the CoreDNSErrorsHigh alert doesn't provide much context about what's happening and what to do next.
Version-Release number of selected component (if applicable):
4.14.39
How reproducible:
always
Steps to Reproduce:
Deploy OCP and use unhealthy nameservers as upstream for CoreDNS ! Or control DNS pods placement without complying with the standard architecture...
Actual results:
CoreDNSErrorsHigh but the description annotation doesn't provide lots of information about what to do next.
Expected results:
Detailed instructions.
Additional info:
https://access.redhat.com/solutions/5917331
- blocks
-
-
- New
-
- is blocked by
-
-
- New
-
-
-
- Verified
-
- is related to
-
-
- Verified
-
- links to
