|
| 1 | +:_mod-docs-content-type: ASSEMBLY |
| 2 | +include::_attributes/common-attributes.adoc[] |
| 3 | +[id="logging-release-notes-6-0"] |
| 4 | += Release notes |
| 5 | +:context: logging-release-notes-6-0 |
| 6 | + |
| 7 | +toc::[] |
| 8 | + |
| 9 | +include::modules/logging-release-notes-6-0-7.adoc[leveloffset=+1] |
| 10 | + |
| 11 | +include::modules/logging-release-notes-6-0-6.adoc[leveloffset=+1] |
| 12 | + |
| 13 | +include::modules/logging-release-notes-6-0-5.adoc[leveloffset=+1] |
| 14 | + |
| 15 | +include::modules/logging-release-notes-6-0-4.adoc[leveloffset=+1] |
| 16 | + |
| 17 | +include::modules/logging-release-notes-6-0-3.adoc[leveloffset=+1] |
| 18 | + |
| 19 | +include::modules/logging-release-notes-6-0-2.adoc[leveloffset=+1] |
| 20 | + |
| 21 | +include::modules/logging-release-notes-6-0-1.adoc[leveloffset=+1] |
| 22 | + |
| 23 | +[id="log6x0-release-notes"] |
| 24 | +== Logging 6.0.0 |
| 25 | +This release includes link:https://access.redhat.com/errata/RHBA-2024:6693[{logging-uc} {for} Bug Fix Release 6.0.0] |
| 26 | + |
| 27 | +include::snippets/logging-compatibility-snip.adoc[] |
| 28 | + |
| 29 | +.Upstream component versions |
| 30 | +[options="header"] |
| 31 | +|=== |
| 32 | + |
| 33 | +| {logging} Version 6+| Component Version |
| 34 | + |
| 35 | +| Operator | `eventrouter` | `logfilemetricexporter` | `loki` | `lokistack-gateway` | `opa-openshift` | `vector` |
| 36 | + |
| 37 | +|6.0 | 0.4 | 1.1 | 3.1.0 | 0.1 | 0.1 | 0.37.1 |
| 38 | + |
| 39 | +|=== |
| 40 | + |
| 41 | +[id="log6x-release-notes-6-0-0-removal-notice"] |
| 42 | +== Removal notice |
| 43 | + |
| 44 | +* With this release, {logging} no longer supports the `ClusterLogging.logging.openshift.io` and `ClusterLogForwarder.logging.openshift.io` custom resources. Refer to the product documentation for details on the replacement features. (link:https://issues.redhat.com/browse/LOG-5803[LOG-5803]) |
| 45 | + |
| 46 | +* With this release, {logging} no longer manages or deploys log storage (such as Elasticsearch), visualization (such as Kibana), or Fluentd-based log collectors. (link:https://issues.redhat.com/browse/LOG-5368[LOG-5368]) |
| 47 | + |
| 48 | +[NOTE] |
| 49 | +==== |
| 50 | +In order to continue to use Elasticsearch and Kibana managed by the elasticsearch-operator, the administrator must modify those object's ownerRefs before deleting the ClusterLogging resource. |
| 51 | +==== |
| 52 | + |
| 53 | +[id="log6x-release-notes-6-0-0-enhancements"] |
| 54 | +== New features and enhancements |
| 55 | + |
| 56 | +* This feature introduces a new architecture for {logging} {for} by shifting component responsibilities to their relevant Operators, such as for storage, visualization, and collection. It introduces the `ClusterLogForwarder.observability.openshift.io` API for log collection and forwarding. Support for the `ClusterLogging.logging.openshift.io` and `ClusterLogForwarder.logging.openshift.io` APIs, along with the Red Hat managed Elastic stack (Elasticsearch and Kibana), is removed. Users are encouraged to migrate to the Red Hat `LokiStack` for log storage. Existing managed Elasticsearch deployments can be used for a limited time. Automated migration for log collection is not provided, so administrators need to create a new ClusterLogForwarder.observability.openshift.io specification to replace their previous custom resources. Refer to the official product documentation for more details. (link:https://issues.redhat.com/browse/LOG-3493[LOG-3493]) |
| 57 | + |
| 58 | +* With this release, the responsibility for deploying the {logging} view plugin shifts from the {clo} to the {coo-first}. For new log storage installations that need visualization, the {coo-full} and the associated UIPlugin resource must be deployed. Refer to the link:https://docs.openshift.com/container-platform/latest/observability/cluster_observability_operator/cluster-observability-operator-overview.html#cluster-observability-operator-overview[Cluster Observability Operator Overview] product documentation for more details. (link:https://issues.redhat.com/browse/LOG-5461[LOG-5461]) |
| 59 | + |
| 60 | +* This enhancement sets default requests and limits for Vector collector deployments' memory and CPU usage based on Vector documentation recommendations. (link:https://issues.redhat.com/browse/LOG-4745[LOG-4745]) |
| 61 | + |
| 62 | +* This enhancement updates Vector to align with the upstream version v0.37.1. (link:https://issues.redhat.com/browse/LOG-5296[LOG-5296]) |
| 63 | + |
| 64 | +* This enhancement introduces an alert that triggers when log collectors buffer logs to a node's file system and use over 15% of the available space, indicating potential back pressure issues. (link:https://issues.redhat.com/browse/LOG-5381[LOG-5381]) |
| 65 | + |
| 66 | +* This enhancement updates the selectors for all components to use common Kubernetes labels. (link:https://issues.redhat.com/browse/LOG-5906[LOG-5906]) |
| 67 | + |
| 68 | +* This enhancement changes the collector configuration to deploy as a ConfigMap instead of a secret, allowing users to view and edit the configuration when the ClusterLogForwarder is set to Unmanaged. (link:https://issues.redhat.com/browse/LOG-5599[LOG-5599]) |
| 69 | + |
| 70 | +* This enhancement adds the ability to configure the Vector collector log level using an annotation on the ClusterLogForwarder, with options including trace, debug, info, warn, error, or off. (link:https://issues.redhat.com/browse/LOG-5372[LOG-5372]) |
| 71 | + |
| 72 | +* This enhancement adds validation to reject configurations where Amazon CloudWatch outputs use multiple AWS roles, preventing incorrect log routing. (link:https://issues.redhat.com/browse/LOG-5640[LOG-5640]) |
| 73 | +* This enhancement removes the Log Bytes Collected and Log Bytes Sent graphs from the metrics dashboard. (link:https://issues.redhat.com/browse/LOG-5964[LOG-5964]) |
| 74 | + |
| 75 | +* This enhancement updates the must-gather functionality to only capture information for inspecting Logging 6.0 components, including Vector deployments from ClusterLogForwarder.observability.openshift.io resources and the Red Hat managed LokiStack. (link:https://issues.redhat.com/browse/LOG-5949[LOG-5949]) |
| 76 | + |
| 77 | +* This enhancement improves Azure storage secret validation by providing early warnings for specific error conditions. (link:https://issues.redhat.com/browse/LOG-4571[LOG-4571]) |
| 78 | + |
| 79 | +* This enhancement updates the `ClusterLogForwarder` API to follow the Kubernetes standards. (link:https://issues.redhat.com/browse/LOG-5977[LOG-5977]) |
| 80 | ++ |
| 81 | +.Example of a new configuration in the `ClusterLogForwarder` custom resource for the updated API |
| 82 | +[source,yaml] |
| 83 | +---- |
| 84 | +apiVersion: observability.openshift.io/v1 |
| 85 | +kind: ClusterLogForwarder |
| 86 | +metadata: |
| 87 | + name: <name> |
| 88 | +spec: |
| 89 | + outputs: |
| 90 | + - name: <output_name> |
| 91 | + type: <output_type> |
| 92 | + <output_type>: |
| 93 | + tuning: |
| 94 | + deliveryMode: AtMostOnce |
| 95 | +---- |
| 96 | + |
| 97 | +[id="log6x-release-notes-6-0-0-technology-preview-features"] |
| 98 | +== Technology Preview features |
| 99 | + |
| 100 | +* This release introduces a Technology Preview feature for log forwarding using OpenTelemetry. A new output type,` OTLP`, allows sending JSON-encoded log records using the OpenTelemetry data model and resource semantic conventions. (link:https://issues.redhat.com/browse/LOG-4225[LOG-4225]) |
| 101 | + |
| 102 | +[id="log6x-release-notes-6-0-0-bug-fixes"] |
| 103 | +== Bug fixes |
| 104 | + |
| 105 | +* Before this update, the `CollectorHighErrorRate` and `CollectorVeryHighErrorRate` alerts were still present. With this update, both alerts are removed in the {logging} 6.0 release but might return in a future release. (link:https://issues.redhat.com/browse/LOG-3432[LOG-3432]) |
| 106 | + |
| 107 | +[id="log6x-release-notes-6-0-0-CVEs"] |
| 108 | +== CVEs |
| 109 | + |
| 110 | +* link:https://access.redhat.com/security/cve/CVE-2024-34397[CVE-2024-34397] |
0 commit comments