Updating containers digests references

[OlivierCazade]

Description

Dependencies

n/a

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.

• 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 labeled 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]

[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 assign jotak for approval. For more information see the 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:

• hack/nudging/OWNERS

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

[memodi]

@OlivierCazade how do you pick those digest references? for instance I see these builds are not yet completed and they seem to be for unmerged PRs/commits.

[OlivierCazade]

I picked them from the last release snapshot on the konflux snapshot.

Are you sure they correspond to unmerged builds ? Only build from main branch should trigger new snapshot.

[memodi]

for instance for consolePlugin is from PR #763

[jotak]

I think @OlivierCazade is correct.
This konflux UI view is a bit misleading, what it shows in the left column is the last image built from the HEAD commit (ie. things that are merged) and on the right column is the last build, including unmerged builds. So the image on the left doesn't necessarily correspond to the build on the right.
You can verify that because PR image tags are prefixed with "on-pr-", like this one:

quay.io/redhat-user-workloads/ocp-network-observab-tenant/netobserv-operator/network-observability-operator-bundle:on-pr-867f4a431c4c231acc5c68752fcd4c1a7ff3edf0

[jotak]

Moreover the fact that the images come from the release snapshot should be sufficient to be trusted, there's no way release snapshot could contained unmerged stuff, unless the whole thing being totally screwed up :-)

[memodi]

This konflux UI view is a bit misleading, what it shows in the left column is the last image built from the HEAD commit (ie. things that are merged) and on the right column is the last build, including unmerged builds.

ah, thanks!

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 62.71%. Comparing base (ae4d2b4) to head (26f08f4).
Report is 3 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1273      +/-   ##
==========================================
+ Coverage   62.66%   62.71%   +0.04%     
==========================================
  Files          76       76              
  Lines       11599    11599              
==========================================
+ Hits         7269     7274       +5     
+ Misses       3865     3861       -4     
+ Partials      465      464       -1     

Flag	Coverage Δ
unittests	62.71% <ø> (+0.04%)	⬆️

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

see 1 file with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[jotak]

/lgtm

[jotak]

This one has changed since your PR :-)

Suggested change

	export OPERATOR_IMAGE_PULLSPEC='registry.redhat.io/network-observability/network-observability-rhel9-operator@sha256:e059192784283385687011b9fa4bb87094783d4530aa66b79168777666a6e2a0'
	export OPERATOR_IMAGE_PULLSPEC='registry.redhat.io/network-observability/network-observability-rhel9-operator@sha256:d8ff9f17ebbf1190632571aab60a7c9fbc7373acec63876e178ae09292805645'