Skip to content

Changed default Docker driver in Release Notes per BZ #10282

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

Changed default Docker driver in Release Notes per BZ #10282

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions release_notes/ocp_3_7_release_notes.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1029,6 +1029,23 @@ openshift_checks_output_dir=/tmp/checks
[[ocp-37-metrics-and-logging]]
=== Metrics and Logging

[[ocp-37-journald-system-logs]]
==== Journald for System Logs and JSON File for Container Logs

Docker log driver is set to `journald` as the default for all nodes. Docker
`log-driver` can be set to `json-file`. Note that 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
from journald and also *_/var/log/containers_* (if `log-driver` is set to
`json-file`). Fluentd will no longer read from *_/var/log/messages_*.

See
xref:../install_config/aggregate_logging.adoc#install-config-aggregate-logging[Aggregating
Container Logs] for more information.

[[ocp-37-docker-events-and-api-calls-aggregated-to-efk-as-logs]]
==== Docker Events and API Calls Aggregated to EFK as Logs

Expand Down