From b58b1153864d200914b7ed92e6cc08a414f50025 Mon Sep 17 00:00:00 2001 From: ahardin-rh Date: Wed, 29 Nov 2017 17:59:40 -0500 Subject: [PATCH] Fixed journald typo --- release_notes/ocp_3_7_release_notes.adoc | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/release_notes/ocp_3_7_release_notes.adoc b/release_notes/ocp_3_7_release_notes.adoc index 359576253806..5163e7d17ee8 100644 --- a/release_notes/ocp_3_7_release_notes.adoc +++ b/release_notes/ocp_3_7_release_notes.adoc @@ -958,7 +958,7 @@ You can also automate the configuration of the provider to point to multiple Ope [NOTE] ==== The *_/tmp/cp.yml_* file requires some manual configurations to create and use -it correctly. +it correctly. //// Commenting out this section till CFME merges See Multiple Container Providers for more information. @@ -1023,9 +1023,9 @@ openshift_checks_output_dir=/tmp/checks ==== Jourald for System Logs and JSON File for Container Logs Docker log driver is set to `json-file` as the default for all nodes. Docker -`log-driver` can be set to `journal`, but there is no log rate throttling with -journal driver. So, there is always a risk for denial-of-service attacks from -rogue containers. +`log-driver` can be set to `journald`, but there is no log rate throttling with +the journald driver. So, there is always a risk for denial-of-service attacks +from rogue containers. Fluentd will automatically determine which log driver (`journald` or `json-file`) the container runtime is using. Fluentd will now always read logs