Skip to content

Commit

Permalink
avoid logging
Browse files Browse the repository at this point in the history
Signed-off-by: Stanislav Knot <[email protected]>
  • Loading branch information
sknot-rh committed Aug 4, 2020
1 parent 276ae0a commit 961c674
Show file tree
Hide file tree
Showing 7 changed files with 12 additions and 10 deletions.
14 changes: 8 additions & 6 deletions documentation/modules/ref-operator-cluster.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -119,19 +119,21 @@ The DNS domain name is added to the Kafka broker certificates used for hostname
If you are using a different DNS domain name suffix in your cluster, change the `KUBERNETES_SERVICE_DNS_DOMAIN` environment variable from the default to the one you are using in order to establish a connection with the Kafka brokers.

[discrete]
== Logging configuration
== Configuration by ConfigMap

Currently only Cluster Operator logging can be configured by ConfigMap.

A `ConfigMap` containing logging configuration is created when installing the Cluster Operator.
This `ConfigMap` is described in the file `install/cluster-operator/050-ConfigMap-strimzi-cluster-operator-logging.yaml`.
You configure Cluster Operator logging by changing the `ConfigMap`.
This `ConfigMap` is described in the file `install/cluster-operator/050-ConfigMap-strimzi-cluster-operator.yaml`.
You configure Cluster Operator logging by changing the data field `log4j2.properties` in this `ConfigMap`.

To update the logging configuration, you can edit the `050-ConfigMap-strimzi-cluster-operator-logging.yaml` file and then run the following command:
To update the logging configuration, you can edit the `050-ConfigMap-strimzi-cluster-operator.yaml` file and then run the following command:
[source,shell,subs=+quotes]
kubectl apply -f _install/cluster-operator/050-ConfigMap-strimzi-cluster-operator-logging.yaml_
kubectl apply -f _install/cluster-operator/050-ConfigMap-strimzi-cluster-operator.yaml_

Alternatively, edit the `ConfigMap` directly:
[source,shell,subs=+quotes]
kubectl edit cm strimzi-cluster-operator-logging
kubectl edit cm strimzi-cluster-operator

To change the frequency of the reload interval, set a time in seconds in the monitorInterval option in the created ConfigMap.

Expand Down
2 changes: 1 addition & 1 deletion helm-charts/helm2/strimzi-kafka-operator/values.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ image:
name: operator
tag: latest
logVolume: cluster-operator-logging-volume
logConfigMap: strimzi-cluster-operator-logging
logConfigMap: strimzi-cluster-operator
fullReconciliationIntervalMs: 120000
operationTimeoutMs: 300000
kubernetesServiceDnsDomain: cluster.local
Expand Down
2 changes: 1 addition & 1 deletion helm-charts/helm3/strimzi-kafka-operator/values.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ image:
name: operator
tag: latest
logVolume: co-logging-volume
logConfigMap: strimzi-cluster-operator-logging
logConfigMap: strimzi-cluster-operator
fullReconciliationIntervalMs: 120000
operationTimeoutMs: 300000
kubernetesServiceDnsDomain: cluster.local
Expand Down
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
kind: ConfigMap
apiVersion: v1
metadata:
name: strimzi-cluster-operator-logging
name: strimzi-cluster-operator
labels:
app: strimzi
data:
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ spec:
volumes:
- name: co-logging-volume
configMap:
name: strimzi-cluster-operator-logging
name: strimzi-cluster-operator
containers:
- name: strimzi-cluster-operator
image: strimzi/operator:latest
Expand Down

0 comments on commit 961c674

Please sign in to comment.