-
Notifications
You must be signed in to change notification settings - Fork 1.8k
OSDOCS-10882 [NETOBSERV] bpfman Support TP #92963
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: no-1.9
Are you sure you want to change the base?
Conversation
🤖 Tue Jun 03 17:05:18 - Prow CI generated the docs preview: |
...erts_tutorials/cloud-experts-getting-started/cloud-experts-getting-started-admin-rights.adoc
Outdated
Show resolved
Hide resolved
63a8b2d
to
4d44d5e
Compare
…nce it is in Networking and not Observbaility (Squash)
:_mod-docs-content-type: PROCEDURE | ||
[id="network-observability-ebpf-manager_{context}"] | ||
= Working with eBPF manager | ||
The eBPF manager is a separate operator that reduces the attack surface, and ensures compliance, security, and conflict prevention by managing all eBPF programs. Network observability uses eBPF manager to load hooks. This eliminates the need to provide the eBPF Agent with privileged mode or additional Linux capabilities like `CAP_BPF` and `CAP_PERFMON`. The eBPF manager with network observability is only supported on 64-bit AMD architecture. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The eBPF manager with network observability is only supported on 64-bit AMD architecture.
@frobware Is this still true?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
According to the blog post https://netobserv.io/posts/what-s-new-in-network-observability-1-8/ .... but ... that was for Developer Preview ...
Since privileged mode is no longer required for NetObserv 1.9, maybe it is supported on other architectures... Will wait for a response, and update accordingly.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah its in the blog, but for 1.8. So just want to confirm with the dev if it still holds true😅
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @frobware ,
For NetObserv 1.9, is this statement still true: "The eBPF manager with network observability is only supported on 64-bit AMD architecture."
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Per Slack, keeping as is until further notice.
/assign @frobware |
:_mod-docs-content-type: PROCEDURE | ||
[id="network-observability-ebpf-manager_{context}"] | ||
= Working with eBPF Manager Operator | ||
The eBPF Manager is a separate operator that reduces the attack surface, and ensures compliance, security, and conflict prevention by managing all eBPF programs. Network observability uses eBPF Manager to load hooks. This eliminates the need to provide the eBPF Agent with privileged mode or additional Linux capabilities like `CAP_BPF` and `CAP_PERFMON`. The eBPF Manager with network observability is only supported on 64-bit AMD architecture. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The eBPF Manager is a separate operator that reduces the attack surface, and ensures compliance, security, and conflict prevention by managing all eBPF programs. Network observability uses eBPF Manager to load hooks. This eliminates the need to provide the eBPF Agent with privileged mode or additional Linux capabilities like `CAP_BPF` and `CAP_PERFMON`. The eBPF Manager with network observability is only supported on 64-bit AMD architecture. | |
The eBPF Manager is a separate operator that reduces the attack surface, and ensures compliance, security, and conflict prevention by managing all eBPF programs. Network observability can use eBPF Manager to load hooks. This eliminates the need to provide the eBPF Agent with privileged mode or additional Linux capabilities like `CAP_BPF` and `CAP_PERFMON`. The eBPF Manager with network observability is only supported on 64-bit AMD architecture. |
@gwynnemonahan: 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. |
https://issues.redhat.com/browse/OSDOCS-10882 [NETOBSERV] bpfman Support TP
Version(s):
Merge to only the no-1.9 branch - no cherrypicks are required.
I will open one PR against main to incorporate all of the NetObserv content just before its GA.
Issue:
https://issues.redhat.com/browse/OSDOCS-10882
Link to docs preview:
https://92963--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/network_observability/observing-network-traffic.html#network-observability-ebpf-manager_nw-observe-network-traffic
QE review:
Additional information:
05/02/2025: Initial PR creation resulted in automagically adding 171 commits from
main
thatno-1.9
wasn't aware of which resulted in a flurry of ocpdocs-vale-bot-related comments for a flurry of errors. Those comments have been resolved as a proper rebase ofno-1.9
resolved all the things.