Network Observability 1.7 Release Notes

[skrthomas]

Version(s):

Merge only to no-1.7. On GA 10/21/24, Sara will open a branch to integrate no-1.7 with main, and that branch will go to 4.12+.

For technical reviewers: 1.6.1 and 1.6.2 are live on docs.openshift.com but because they are on the main docs branch, they have not yet been rebased with this no-1.7 branch, so you won't see them on this preview.
Issue:

FIPS compliance: https://issues.redhat.com/browse/OSDOCS-11078
Link to docs preview:

https://81551--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/network_observability/network-observability-operator-release-notes.html#network-observability-operator-1.7.0-features-enhancements_network-observability-operator-release-notes-v0
QE review:

• QE has approved this change.

Additional information:

[ocpdocs-previewbot]

🤖 Sat Oct 19 21:24:42 - Prow CI generated the docs preview:

https://81551--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/network_observability/network-observability-operator-release-notes.html

[jotak]

I would rather say "to limit the volume of packets processed by the eBPF program", because there's more than caching, and I guess readers don't have to know about the internal details

Suggested change

You can now use the `tcpFlags` filter to control the volume of packets cached in the eBPF flow table. For more information, see xref:../../observability/network_observability/observing-network-traffic.adoc#network-observability-flowcollector-flowfilter-parameters_nw-observe-network-traffic[Flow filter configuration parameters] and xref:../../observability/network_observability/observing-network-traffic.adoc#network-observability-ebpf-flow-rule-filter_nw-observe-network-traffic[eBPF flow rule filter].

You can now use the `tcpFlags` filter to limit the volume of packets processed by the eBPF program. For more information, see xref:../../observability/network_observability/observing-network-traffic.adoc#network-observability-flowcollector-flowfilter-parameters_nw-observe-network-traffic[Flow filter configuration parameters] and xref:../../observability/network_observability/observing-network-traffic.adoc#network-observability-ebpf-flow-rule-filter_nw-observe-network-traffic[eBPF flow rule filter].

[OlivierCazade]

Thanks!

[memodi]

@skrthomas the current notes LGTM
do we also specify known issues as part of RN? I pulled list using JIRA:

project=netobserv and affectedVersion = netobserv-1.7-candidate and status != closed

don't think all in that list needs a call out but some of them may, for e.g.: NETOBSERV-1933, NETOBSERV-1830 , NETOBSERV-1890

[Amoghrd]

LGTM

[skrthomas]

@memodi thanks for calling out these known issues. We do specify known issues, but I was only aware of the bugs that were listed in the errata. I will add these known issues. Some of them don't have text, so I will follow up in the Jiras about what to write for these.

[ocpdocs-vale-bot]

🤖 [error] AsciiDoc.ClosedIdQuotes: Quoted ID value is not closed.

[ocpdocs-vale-bot]

🤖 [error] RedHat.CaseSensitiveTerms: Use 'Kubernetes' rather than 'k8s'. For more information, see RedHat.CaseSensitiveTerms.

[skrthomas]

n/a since this is part of the yaml

[stleerh]

This doesn't sound right.  Suggest:
If the DNS service maps to a different port than 53, you can specify this DNS tracking port.

[memodi]

/label qe-approved

[lahinson]

A few nits for your consideration!

[openshift-ci]

@skrthomas: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.