Skip to content

Commit 6a932ac

Browse files
Merge pull request #833 from lance5890/update_readme_log_level
NO-JIRA: readme: describe mapping between logLevel and log level
2 parents 9a7a572 + 01cdb57 commit 6a932ac

File tree

1 file changed

+32
-0
lines changed

1 file changed

+32
-0
lines changed

README.md

+32
Original file line numberDiff line numberDiff line change
@@ -46,6 +46,38 @@ spec:
4646
managementState: Managed
4747
...
4848
```
49+
The log level of individual kube-controller-manager instances can be increased by setting `.spec.logLevel` field:
50+
```
51+
$ oc explain KubeControllerManager.spec.logLevel
52+
KIND: KubeControllerManager
53+
VERSION: operator.openshift.io/v1
54+
FIELD: logLevel <string>
55+
DESCRIPTION:
56+
logLevel is an intent based logging for an overall component. It does not
57+
give fine grained control, but it is a simple way to manage coarse grained
58+
logging choices that operators have to interpret for their operands. Valid
59+
values are: "Normal", "Debug", "Trace", "TraceAll". Defaults to "Normal".
60+
```
61+
For example:
62+
```yaml
63+
apiVersion: operator.openshift.io/v1
64+
kind: KubeControllerManager
65+
metadata:
66+
name: cluster
67+
spec:
68+
logLevel: Debug
69+
...
70+
```
71+
72+
Currently the log levels correspond to:
73+
74+
| logLevel | log level |
75+
| -------- | --------- |
76+
| Normal | 2 |
77+
| Debug | 4 |
78+
| Trace | 6 |
79+
| TraceAll | 10 |
80+
4981
```
5082
$ oc explain kubecontrollermanager
5183
```

0 commit comments

Comments
 (0)