You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/docs/whats-new/_index.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,8 +9,8 @@ weight: 50
9
9
10
10
As announced in the 5.4 release notes, the 6.0 release includes the following breaking changes:
11
11
12
-
- NodeAgent CRD and inline NodeAgents in the Logging resource have been removed
13
-
- hostTailer cannot be configured from the Helm chart anymore.
12
+
- NodeAgent CRD and inline NodeAgents in the Logging resource have been removed. See [migration tips](#nodeagent-migration).
13
+
- hostTailer cannot be configured from the Helm chart anymore, [use hosttailers instead](#hosttailer-migration).
14
14
15
15
For details, see the [deprecation notice for 5.4](#upcoming-deprecations-and-breaking-changes). Note that 5.4.0 remains officially supported until October 6. (If needed, patch releases from community contributions for version 5.4.0 will be supported even after 6th of October.)
16
16
@@ -28,7 +28,7 @@ The following are the highlights and main changes of Logging operator 5.4. For a
28
28
29
29
We are planning on deprecating the following components in the next major release. These breaking changes will be part of version 6.0.0 (scheduled for July 14), while 5.4.0 remains officially supported until October 6. (If needed, patch releases from community contributions for version 5.4.0 will be supported even after 6th of October.)
30
30
31
-
#### NodeAgent CRD and inline NodeAgents in the Logging resource
31
+
#### NodeAgent CRD and inline NodeAgents in the Logging resource {#nodeagent-migration}
32
32
33
33
NodeAgents were an attempt to generalize log agents configuration, but it never got out PoC status, with the main feature of running Fluent Bit on Windows hosts. The code hasn't been updated recently, and the original FluentbitSpec (in the Logging resource and in the separate FluentbitAgent resource) and the features behind it have significantly diverged.
34
34
@@ -37,7 +37,7 @@ Last year we've introduced [Telemetry Controller](https://github.com/kube-loggin
37
37
- If you're using NodeAgent on Windows, get in touch with us (the Logging operator maintainers) over the [community channels]({{< relref "/docs/community.md" >}}), so we can help you find a viable path forward using the Telemetry Controller.
38
38
- Non-windows users should either migrate to [FluentbitAgent]({{< relref "/docs/configuration/crds/v1beta1/fluentbit_types.md" >}}), or to the [Telemetry Controller](https://github.com/kube-logging/telemetry-controller). In case you need help with either case, [feel free to contact us]({{< relref "/docs/community.md" >}}).
39
39
40
-
#### hostTailer in the Helm chart
40
+
#### hostTailer in the Helm chart {#hosttailer-migration}
41
41
42
42
Configuring a hostTailer in the [Logging operator Helm chart](https://github.com/kube-logging/logging-operator/tree/master/charts/logging-operator) is deprecated in favor of using hostTailers. Migrate your hostTailer configuration like this:
0 commit comments