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
+106Lines changed: 106 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -13,6 +13,112 @@ The following are the highlights and main changes of Logging operator 5.4. For a
13
13
- You can [disable mounting the `/var/log` volume]({{< relref "/docs/configuration/crds/v1beta1/fluentbit_types.md#fluentbitspec-disablevarlog" >}}) in Fluent Bit. This is useful when you're not permitted to mount host volumes, and collect host logs some other way.
14
14
- Initial basic implementation of the upcoming [AxoSyslog custom resource]({{< relref "/docs/configuration/crds/v1beta1/axosyslog_types.md" >}}).
15
15
16
+
### Upcoming deprecations and breaking changes
17
+
18
+
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.)
19
+
20
+
#### NodeAgent CRD and inline NodeAgents in the Logging resource
21
+
22
+
[NodeAgents]({{< relref "/docs/configuration/crds/v1beta1/node_agent_types.md" >}}) 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.
23
+
24
+
Last year we've introduced [Telemetry Controller](https://github.com/kube-logging/telemetry-controller) as a replacement for the NodeAgent and FluentbitAgent resources, with additional multi-tenant capabilities and more flexible agent-side log selection.
25
+
26
+
- 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.
27
+
- 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" >}}).
28
+
29
+
#### hostTailer in the Helm chart
30
+
31
+
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:
32
+
33
+
- Old configuration:
34
+
35
+
```yaml
36
+
hostTailer:
37
+
# -- HostTailer
38
+
enabled: false
39
+
# -- name of HostTailer
40
+
name: hosttailer
41
+
image:
42
+
# -- repository of eventTailer image
43
+
repository:
44
+
# -- tag of eventTailer image
45
+
tag:
46
+
# -- pullPolicy of eventTailer image
47
+
pullPolicy:
48
+
# -- imagePullSecrets of eventTailer image
49
+
imagePullSecrets: []
50
+
# -- workloadMetaOverrides of HostTailer
51
+
workloadMetaOverrides:
52
+
# -- workloadOverrides of HostTailer
53
+
workloadOverrides:
54
+
# -- configure fileTailers of HostTailer
55
+
# example:
56
+
# - name: sample-file
57
+
# path: /var/log/sample-file
58
+
# disabled: false
59
+
# buffer_max_size:
60
+
# buffer_chunk_size:
61
+
# skip_long_lines:
62
+
# read_from_head: false
63
+
# containerOverrides:
64
+
# image:
65
+
fileTailers: []
66
+
# -- configure systemdTailers of HostTailer
67
+
# example:
68
+
# - name: system-sample
69
+
# disabled: false
70
+
# systemdFilter: kubelet.service
71
+
# maxEntries: 20
72
+
# containerOverrides:
73
+
# image:
74
+
systemdTailers: **[]**
75
+
```
76
+
77
+
- The new configuration will be similar to this:
78
+
79
+
```yaml
80
+
hostTailers:
81
+
# -- Enable all hostTailers
82
+
enabled: false
83
+
# -- List of hostTailers configurations
84
+
instances: []
85
+
# - name: hosttailer
86
+
# -- Enable hostTailer
87
+
# enabled: true
88
+
# image:
89
+
# -- repository of eventTailer image
90
+
# repository:
91
+
# -- tag of eventTailer image
92
+
# tag:
93
+
# -- pullPolicy of eventTailer image
94
+
# pullPolicy:
95
+
# -- imagePullSecrets of eventTailer image
96
+
# imagePullSecrets: []
97
+
# -- workloadMetaOverrides of HostTailer
98
+
# workloadMetaOverrides: {}
99
+
# -- workloadOverrides of HostTailer
100
+
# workloadOverrides: {}
101
+
# -- configure fileTailers of HostTailer
102
+
# fileTailers:
103
+
# - name: sample-file
104
+
# path: /var/log/sample-file
105
+
# disabled: false
106
+
# buffer_max_size:
107
+
# buffer_chunk_size:
108
+
# skip_long_lines:
109
+
# read_from_head: false
110
+
# containerOverrides:
111
+
# image:
112
+
# -- configure systemdTailers of HostTailer
113
+
# systemdTailers:
114
+
# - name: system-sample
115
+
# disabled: false
116
+
# systemdFilter: kubelet.service
117
+
# maxEntries: 20
118
+
# containerOverrides:
119
+
# image:
120
+
```
121
+
16
122
## Version 5.3
17
123
18
124
The following are the highlights and main changes of Logging operator 5.3. For a complete list of changes and bugfixes, see the [Logging operator 5.3 releases page](https://github.com/kube-logging/logging-operator/releases/tag/5.3.0).
0 commit comments