RHDEVDOCS-4080 - RNs with 5.5.1 v6

Author: libander

logging/cluster-logging-release-notes.adoc

@@ -2,7 +2,68 @@
 //cluster-logging-loki.adoc
 :_content-type: REFERENCE
 [id="logging-feature-ref_{context}"]
-= Collector features
+id="cluster-logging-about-vector"]
+= About Vector
+Vector is a log collector offered as an alternative to Fluentd for the {logging}.
+
+The following outputs are supported:
+
+* `elasticsearch`. An external Elasticsearch instance. The `elasticsearch` output can use a TLS connection.
+
+* `kafka`. A Kafka broker. The `kafka` output can use an unsecured or TLS connection.
+
+* `loki`. Loki, a horizontally scalable, highly available, multitenant log aggregation system.
+
+
+[id="cluster-logging-vector-enable_{context}"]
+== Enabling Vector
+Vector is not enabled by default. Use the following steps to enable Vector on your {product-title} cluster.
+
+[IMPORTANT]
+====
+Vector does not support FIPS Enabled Clusters.
+====
+
+.Prerequisites
+
+* {product-title}: 4.11
+* {logging-title-uc}: 5.4
+* FIPS disabled
+
+.Procedure
+
+. Edit the `ClusterLogging` custom resource (CR) in the `openshift-logging` project:
++
+[source,terminal]
+----
+$ oc -n openshift-logging edit ClusterLogging instance
+----
+
+. Add a `logging.openshift.io/preview-vector-collector: enabled` annotation to the `ClusterLogging` custom resource (CR).
+
+. Add `vector` as a collection type to the `ClusterLogging` custom resource (CR).
+
+[source,yaml]
+----
+  apiVersion: "logging.openshift.io/v1"
+  kind: "ClusterLogging"
+  metadata:
+    name: "instance"
+    namespace: "openshift-logging"
+    annotations:
+      logging.openshift.io/preview-vector-collector: enabled
+  spec:
+    collection:
+    logs:
+      type: "vector"
+      vector: {}
+----
+
+[role="_additional-resources"]
+.Additional resources
+* link:https://vector.dev/docs/about/what-is-vector/[Vector Documentation]
+
+== Collector features
 
 .Log Sources
 [options="header"]

modules/cluster-logging-feature-reference.adoc

@@ -124,5 +124,5 @@ oc apply -f cr-lokistack.yaml
 
 [NOTE]
 ====
-This plugin is only available on {product-title} 4.10 and later. {product-title}
+This plug-in is only available on {product-title} 4.10 and later.
 ====

modules/cluster-logging-loki-deploy.adoc

@@ -0,0 +1,20 @@
+//module included in cluster-logging-release-notes.adoc
+:_content-type: REFERENCE
+[id="cluster-logging-release-notes-5-3-11_{context}"]
+= Logging 5.5.1
+This release includes link:https://access.redhat.com/errata/RHSA-2022:6182[OpenShift Logging Bug Fix Release 5.3.11].
+
+[id="openshift-logging-5-3-11-bug-fixes_{context}"]
+== Bug fixes
+* Before this update, the Operator did not ensure that the pod was ready, which caused the cluster to reach an inoperable state during a cluster restart. With this update, the Operator marks new pods as ready before continuing to a new pod during a restart, which resolves the issue. (link:https://issues.redhat.com/browse/LOG-2871[LOG-2871])
+
+[id="openshift-logging-5-3-11-cves_{context}"]
+== CVEs
+* link:https://access.redhat.com/security/cve/CVE-2022-1292[CVE-2022-1292]
+* link:https://access.redhat.com/security/cve/CVE-2022-1586[CVE-2022-1586]
+* link:https://access.redhat.com/security/cve/CVE-2022-1785[CVE-2022-1785]
+* link:https://access.redhat.com/security/cve/CVE-2022-1897[CVE-2022-1897]
+* link:https://access.redhat.com/security/cve/CVE-2022-1927[CVE-2022-1927]
+* link:https://access.redhat.com/security/cve/CVE-2022-2068[CVE-2022-2068]
+* link:https://access.redhat.com/security/cve/CVE-2022-2097[CVE-2022-2097]
+* link:https://access.redhat.com/security/cve/CVE-2022-30631[CVE-2022-30631]

modules/cluster-logging-rn-5.3.11.adoc

@@ -0,0 +1,26 @@
+//module included in cluster-logging-release-notes.adoc
+:_content-type: REFERENCE
+[id="cluster-logging-release-notes-5-4-5_{context}"]
+= Logging 5.5.1
+This release includes link:https://access.redhat.com/errata/RHSA-2022:6183[RHSA-2022:6183-OpenShift Logging Bug Fix Release 5.4.5].
+
+[id="openshift-logging-5-4-5-bug-fixes_{context}"]
+== Bug fixes
+* Before this update, the Operator did not ensure that the pod was ready, which caused the cluster to reach an inoperable state during a cluster restart. With this update, the Operator marks new pods as ready before continuing to a new pod during a restart, which resolves the issue. (link:https://issues.redhat.com/browse/LOG-2881[LOG-2881])
+
+* Before this update, the addition of multi-line error detection caused internal routing to change and forward records to the wrong destination. With this update, the internal routing is correct. (link:https://issues.redhat.com/browse/LOG-2946[LOG-2946])
+
+* Before this update, the Operator could not decode index setting JSON responses with a quoted Boolean value and would result in an error. With this update, the Operator can properly decode this JSON response. (link:https://issues.redhat.com/browse/LOG-3009[LOG-3009])
+
+* Before this update, Elasticsearch index templates defined the fields for labels with the wrong types. This change updates those templates to match the expected types forwarded by the log collector. (link:https://issues.redhat.com/browse/LOG-2972[LOG-2972])
+
+[id="openshift-logging-5-4-5-cves_{context}"]
+== CVEs
+* link:https://access.redhat.com/security/cve/CVE-2022-1292[CVE-2022-1292]
+* link:https://access.redhat.com/security/cve/CVE-2022-1586[CVE-2022-1586]
+* link:https://access.redhat.com/security/cve/CVE-2022-1785[CVE-2022-1785]
+* link:https://access.redhat.com/security/cve/CVE-2022-1897[CVE-2022-1897]
+* link:https://access.redhat.com/security/cve/CVE-2022-1927[CVE-2022-1927]
+* link:https://access.redhat.com/security/cve/CVE-2022-2068[CVE-2022-2068]
+* link:https://access.redhat.com/security/cve/CVE-2022-2097[CVE-2022-2097]
+* link:https://access.redhat.com/security/cve/CVE-2022-30631[CVE-2022-30631]

modules/cluster-logging-rn-5.4.5.adoc

@@ -4,7 +4,6 @@
 = Logging 5.5
 The following advisories are available for Logging 5.5:link:https://access.redhat.com/errata/RHSA-2022:6051[Release 5.5]
 
-
 [id="openshift-logging-5-5-0-enhancements"]
 == Enhancements
 * With this update, you can forward structured logs from different containers within the same pod to different indices. To use this feature, you must configure the pipeline with multi-container support and annotate the pods. (link:https://issues.redhat.com/browse/LOG-1296[LOG-1296])
@@ -18,7 +17,7 @@ JSON formatting of logs varies by application. Because creating too many indices
 
 * With this update, clusters with AWS Security Token Service (STS) enabled may use STS authentication to forward logs to Amazon CloudWatch. (link:https://issues.redhat.com/browse/LOG-1976[LOG-1976])
 
-* With this update, the 'LokiOperator' Operator moves from Technical Preview to General Availability. Full feature parity with prior releases are pending, and some APIs remain Technical Previews. See the *Logging with the LokiStack* section for details.
+* With this update, the 'LokiOperator' Operator and Vector collector move from Technical Preview to General Availability. Full feature parity with prior releases are pending, and some APIs remain Technical Previews. See the *Logging with the LokiStack* section for details.
 
 [id="openshift-logging-5-5-0-bug-fixes"]
 == Bug fixes