WIP: NETOBSERV-1675: ovs monitoring update ebpf agent dependency

[msherif1234]

Description

ebpf agent dependency update

Dependencies

netobserv/netobserv-ebpf-agent#286

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.

• Will this change affect NetObserv / Network Observability operator? If not, you can ignore the rest of this checklist.
• Is this PR backed with a JIRA ticket? If so, make sure it is written as a title prefix (in general, PRs affecting the NetObserv/Network Observability product should be backed with a JIRA ticket - especially if they bring user facing changes).
• Does this PR require product documentation?
  • If so, make sure the JIRA epic is labelled with "documentation" and provides a description relevant for doc writers, such as use cases or scenarios. Any required step to activate or configure the feature should be documented there, such as new CRD knobs.
• Does this PR require a product release notes entry?
  • If so, fill in "Release Note Text" in the JIRA.
• Is there anything else the QE team should know before testing? E.g: configuration changes, environment setup, etc.
  • If so, make sure it is described in the JIRA ticket.
• QE requirements (check 1 from the list):
  • Standard QE validation, with pre-merge tests unless stated otherwise.
  • Regression tests only (e.g. refactoring with no user-facing change).
  • No QE (e.g. trivial change with high reviewer's confidence, or per agreement with the QE team).

[openshift-ci-robot]

@msherif1234: This pull request references NETOBSERV-1675 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.17.0" version, but no target version was set.

In response to this:

Description

ebpf agent dependency update

Dependencies

netobserv/netobserv-ebpf-agent#286

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.

• Will this change affect NetObserv / Network Observability operator? If not, you can ignore the rest of this checklist.
• Is this PR backed with a JIRA ticket? If so, make sure it is written as a title prefix (in general, PRs affecting the NetObserv/Network Observability product should be backed with a JIRA ticket - especially if they bring user facing changes).
• Does this PR require product documentation?
• If so, make sure the JIRA epic is labelled with "documentation" and provides a description relevant for doc writers, such as use cases or scenarios. Any required step to activate or configure the feature should be documented there, such as new CRD knobs.
• Does this PR require a product release notes entry?
• If so, fill in "Release Note Text" in the JIRA.
• Is there anything else the QE team should know before testing? E.g: configuration changes, environment setup, etc.
• If so, make sure it is described in the JIRA ticket.
• QE requirements (check 1 from the list):
• Standard QE validation, with pre-merge tests unless stated otherwise.
• Regression tests only (e.g. refactoring with no user-facing change).
• No QE (e.g. trivial change with high reviewer's confidence, or per agreement with the QE team).

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.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from msherif1234. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[msherif1234]

/ok-to-test

[msherif1234]

/ok-to-test

[github-actions]

New image:
quay.io/netobserv/flowlogs-pipeline:536b9f0

It will expire after two weeks.

To deploy this build, run from the operator repo, assuming the operator is running:

USER=netobserv VERSION=536b9f0 make set-flp-image

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 65.33%. Comparing base (b010e85) to head (fb8cb82).

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #669      +/-   ##
==========================================
- Coverage   65.36%   65.33%   -0.03%     
==========================================
  Files         107      107              
  Lines        6874     6874              
==========================================
- Hits         4493     4491       -2     
- Misses       2071     2072       +1     
- Partials      310      311       +1     

Flag	Coverage Δ
unittests	65.33% <ø> (-0.03%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

see 1 file with indirect coverage changes

[msherif1234]

/ok-to-test

[github-actions]

New image:
quay.io/netobserv/flowlogs-pipeline:c0e4cec

It will expire after two weeks.

To deploy this build, run from the operator repo, assuming the operator is running:

USER=netobserv VERSION=c0e4cec make set-flp-image

[msherif1234]

/ok-to-test

[github-actions]

New image:
quay.io/netobserv/flowlogs-pipeline:b3da349

It will expire after two weeks.

To deploy this build, run from the operator repo, assuming the operator is running:

USER=netobserv VERSION=b3da349 make set-flp-image

[msherif1234]

/ok-to-test

[github-actions]

New image:
quay.io/netobserv/flowlogs-pipeline:ca4c243

It will expire after two weeks.

To deploy this build, run from the operator repo, assuming the operator is running:

USER=netobserv VERSION=ca4c243 make set-flp-image

[msherif1234]

/ok-to-test

[github-actions]

New image:
quay.io/netobserv/flowlogs-pipeline:7b6db1d

It will expire after two weeks.

To deploy this build, run from the operator repo, assuming the operator is running:

USER=netobserv VERSION=7b6db1d make set-flp-image

[msherif1234]

/ok-to-test

[github-actions]

New image:
quay.io/netobserv/flowlogs-pipeline:d67bb65

It will expire after two weeks.

To deploy this build, run from the operator repo, assuming the operator is running:

USER=netobserv VERSION=d67bb65 make set-flp-image

[msherif1234]

/ok-to-test

[msherif1234]

/ok-to-test

[github-actions]

New image:
quay.io/netobserv/flowlogs-pipeline:d67bb65

It will expire after two weeks.

To deploy this build, run from the operator repo, assuming the operator is running:

USER=netobserv VERSION=d67bb65 make set-flp-image

[msherif1234]

/ok-to-test

[github-actions]

New image:
quay.io/netobserv/flowlogs-pipeline:d534458

It will expire after two weeks.

To deploy this build, run from the operator repo, assuming the operator is running:

USER=netobserv VERSION=d534458 make set-flp-image

[msherif1234]

/ok-to-test

[github-actions]

New image:
quay.io/netobserv/flowlogs-pipeline:92216c2

It will expire after two weeks.

To deploy this build, run from the operator repo, assuming the operator is running:

USER=netobserv VERSION=92216c2 make set-flp-image

[msherif1234]

/ok-to-test

[github-actions]

New image:
quay.io/netobserv/flowlogs-pipeline:6465b47

It will expire after two weeks.

To deploy this build, run from the operator repo, assuming the operator is running:

USER=netobserv VERSION=6465b47 make set-flp-image