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: CHANGELOG.md
+12Lines changed: 12 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,17 @@
1
1
# Change Log
2
2
3
+
# 2025-06-17
4
+
### Added
5
+
- Introduced a new DaemonSet that uses eBPF (Extended Berkeley Packet Filter) to capture TCP connection logs and builds application/network topology representing workload to workload relationships within the Kubernetes cluster.
6
+
- To be able to run the required eBPF program, the pods needs to run in privileged mode but restricting to CAP_BPF capability only.
7
+
- New helm variable to control the resource limits at individual logan workloads.
8
+
- Enables OKE infra discovery and service logs collection (default)
9
+
- OCI Console integration supporting new features:
10
+
- Topology : New Views (Infra and Network) along with Platform.
11
+
- View Insights for Workloads including capabilities to view the detailed spec of a workload, monitor the changes to the spec of a workload, create in-line labels for issues etc.
12
+
13
+
### Changed
14
+
-`kubernetesClusterID` (in the Helm chart) is now a mandatory field. *(This is not backward compatible.)*
For changes in this release, refer to [CHANGELOG.md](CHANGELOG.md)
373
+
374
+
##### Upgrade instructions
375
+
376
+
1. Update IAM Policies:
377
+
* This version requires additional policy statements for infrastructure discovery.
378
+
* See the pre-requisites section in the [README](../README.md#0-pre-requisites) for details.
379
+
380
+
1. As mentioned in the change log, this version introduces a new DaemonSet that uses eBPF (Extended Berkeley Packet Filter) to capture TCP connection logs and builds application/network topology representing workload to workload relationships within the Kubernetes cluster.
381
+
* To be able to run the required eBPF program, the pods needs to run in privileged mode but restricting to CAP_BPF capability only.
382
+
* In your environment, if you have any restrictions with respect to running pods in privileged mode, you may need to adjust your cluster configuration accordingly.
383
+
384
+
2. Upgrade the Helm chart:
385
+
386
+
```sh
387
+
# fetch latest (4.x) helm repo for oci
388
+
helm repo update oci-onm
389
+
390
+
# fetch the current release configuration
391
+
helm get values <release-name> -n <namespace> > override_values.yaml
One of the major changes introduced in 3.0.0 is refactoring of helm chart where major features of the solution got split into separate sub-charts. 2.x has only support for logs and objects collection using Fluentd and OCI Logging Analytics and this is now moved into a separate chart oci-onm-logan and included as a sub-chart to the main chart oci-onm. This is a breaking change w.r.t the values.yaml and any customisations that you might have done on top of it. There is no breaking change w.r.t functionality offered in 2.x. For full list of changes in 3.x, refer to [changelog](CHANGELOG.md).
0 commit comments