-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.13, 4.12, 4.11, 4.10, 4.14, 4.15, 4.16
-
Low
-
No
-
False
-
-
Release Note Not Required
-
In Progress
Description of problem
The DNS Operator documentation describes how to configure the log level for CoreDNS but does not tell how to get the logs.
Version-Release number of selected component (if applicable)
4.16 through 4.10. The capability and documentation for customizing the CoreDNS log level were added in OCP 4.10.
How reproducible
100%.
Steps to Reproduce
1. Read <https://docs.openshift.com/container-platform/4.12/networking/dns-operator.html#nw-dns-loglevel_dns-operator> or the corresponding documentation for any of the affected OpenShift releases.
Actual results
The documentation explains how to set the log level, but not how to read the logs.
Expected results
The documentation should explain how to read the logs. For example:
You can view CoreDNS logs by using the `oc logs` command. .Procedure * To view the logs of a specific CoreDNS pod, enter the following command: [source,terminal] ---- $ oc -n openshift-dns logs -c dns dns-default-s58l9 ---- * To follow the logs of all CoreDNS pods, enter the following command: [source,terminal] ---- $ oc -n openshift-dns logs -c dns -l dns.operator.openshift.io/daemonset-dns=default -f --max-log-requests=6 <1> ---- <1> Specifies maximum number of DNS pods to stream logs from.