-
Notifications
You must be signed in to change notification settings - Fork 34
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
SDN-5393: eBPF agent intg with bpfman for ebpf progs life cycle mgmts #443
base: main
Are you sure you want to change the base?
Conversation
@msherif1234: This pull request references SDN-5393 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.18.0" version, but no target version was set. In response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #443 +/- ##
==========================================
- Coverage 29.71% 29.23% -0.48%
==========================================
Files 50 50
Lines 4877 4959 +82
==========================================
+ Hits 1449 1450 +1
- Misses 3322 3403 +81
Partials 106 106
Flags with carried forward coverage won't be shown. Click here to find out more.
|
@msherif1234: This pull request references SDN-5393 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.18.0" version, but no target version was set. In response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
eed3217
to
7b5953d
Compare
/ok-to-test |
New image: It will expire after two weeks. To deploy this build, run from the operator repo, assuming the operator is running: USER=netobserv VERSION=af27118 make set-agent-image |
39beda6
to
ad1d559
Compare
ad1d559
to
5fe4499
Compare
/ok-to-test |
New image: It will expire after two weeks. To deploy this build, run from the operator repo, assuming the operator is running: USER=netobserv VERSION=dc5079c make set-agent-image |
5fe4499
to
3ff24fb
Compare
3ff24fb
to
d62af9a
Compare
/ok-to-test |
New image: It will expire after two weeks. To deploy this build, run from the operator repo, assuming the operator is running: USER=netobserv VERSION=b04ad60 make set-agent-image |
d62af9a
to
194fef5
Compare
/ok-to-test |
New image: It will expire after two weeks. To deploy this build, run from the operator repo, assuming the operator is running: USER=netobserv VERSION=4b53105 make set-agent-image |
194fef5
to
98d2749
Compare
New image: It will expire after two weeks. To deploy this build, run from the operator repo, assuming the operator is running: USER=netobserv VERSION=469ccb5 make set-agent-image |
93faa21
to
92c66f1
Compare
/ok-to-test |
New image: It will expire after two weeks. To deploy this build, run from the operator repo, assuming the operator is running: USER=netobserv VERSION=194fdb1 make set-agent-image |
92c66f1
to
1d7134f
Compare
/ok-to-test |
New image: It will expire after two weeks. To deploy this build, run from the operator repo, assuming the operator is running: USER=netobserv VERSION=4ab660f make set-agent-image |
1d7134f
to
1b6d926
Compare
1b6d926
to
83ebdfb
Compare
/ok-to-test |
New image: It will expire after two weeks. To deploy this build, run from the operator repo, assuming the operator is running: USER=netobserv VERSION=3ca4ab3 make set-agent-image |
e2e/cluster/base/04-agent.yml
Outdated
@@ -40,4 +40,4 @@ spec: | |||
- name: bpf-kernel-debug | |||
hostPath: | |||
path: /sys/kernel/debug | |||
type: Directory | |||
type: Directory |
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.
Was there a reason to change this file and remove the linefeed char?
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.
no reason I was just doing some changes there but reverted once found a way to work in none privileged mode will revert the whitespace changes
e2e/kafka/manifests/30-agent.yml
Outdated
@@ -38,4 +38,4 @@ spec: | |||
- name: bpf-kernel-debug | |||
hostPath: | |||
path: /sys/kernel/debug | |||
type: Directory | |||
type: Directory |
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.
Same here
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.
same
\"kfree_skb\":\"tracepoint\",\ | ||
\"rh_network_events_monitoring\":\"kprobe\"\ | ||
}" | ||
|
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.
This could be a lot more readable if you remove all backslashes and use a single quote around the entire string like this:
PROGRAMS='{
"tcx_ingress_flow_parse":"tcx",
"tcx_egress_flow_parse":"tcx",
"tc_ingress_flow_parse":"tc",
"tc_egress_flow_parse":"tc",
"tcx_ingress_pca_parse":"tcx",
"tcx_egress_pca_parse":"tcx",
"tc_ingress_pca_parse":"tc",
"tc_egress_pca_parse":"tc",
"tcp_rcv_fentry":"fentry",
"tcp_rcv_kprobe":"kprobe",
"kfree_skb":"tracepoint",
"rh_network_events_monitoring":"kprobe"
}'
Note: Each new line does add a space and the only way to get rid of that is to put it all on the same line, which is undesirable. Most likely, the spaces won't matter if you quote the variable like "$PROGRAM".
hack/build-bytecode-images-multi.sh
Outdated
\"dns_flows\":\"hash\",\ | ||
\"global_counters\":\"per_cpu_array\",\ | ||
\"filter_map\":\"lpm_trie\"\ | ||
}" |
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.
Similar to above.
MAPS='{
"direct_flows":"ringbuf",
"aggregated_flows":"per_cpu_hash",
"packets_record":"perf_event_array",
"dns_flows":"hash",
"global_counters":"per_cpu_array",
"filter_map":"lpm_trie"
}'
pkg/tracer/tracer.go
Outdated
if !cfg.UseEbpfManager { | ||
if err := rlimit.RemoveMemlock(); err != nil { | ||
log.WithError(err). | ||
Warn("can't remove mem lock. The agent could not be able to start eBPF programs") |
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.
I know this was existing code. I think the message is suppose to say:
The agent might not be able to start the eBPF programs.
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 agent will not be able to start the eBPF programs.
WDYT?
Signed-off-by: Mohamed Mahmoud <mmahmoud@redhat.com>
83ebdfb
to
9bd714a
Compare
/ok-to-test |
New image: It will expire after two weeks. To deploy this build, run from the operator repo, assuming the operator is running: USER=netobserv VERSION=cb970b1 make set-agent-image |
PR needs rebase. 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. |
Description
prepare ebpf agent to use bpfman to manage netobserv ebpf programs
Dependencies
netobserv/network-observability-operator#829
Checklist
If you are not familiar with our processes or don't know what to answer in the list below, let us know in a comment: the maintainers will take care of that.