Skip to content

Conversation

@jpinsonneau
Copy link
Contributor

@jpinsonneau jpinsonneau commented Jan 8, 2026

Description

  • react icons library
  • custom svgs from kubernetes official icons
image image image image image image image

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 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
Copy link
Collaborator

openshift-ci-robot commented Jan 8, 2026

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

Details

In response to this:

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 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
Copy link

openshift-ci bot commented Jan 8, 2026

[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 mffiedler for approval. For more information see the Code Review Process.

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

Details Needs approval from an approver in each of these files:

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

@openshift-ci-robot
Copy link
Collaborator

openshift-ci-robot commented Jan 8, 2026

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

Details

In response to this:

Description

  • react icons library
  • custom svgs from kubernetes official icons
image

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 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-robot
Copy link
Collaborator

openshift-ci-robot commented Jan 8, 2026

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

Details

In response to this:

Description

  • react icons library
  • custom svgs from kubernetes official icons
image image image image image image image

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 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.

@jpinsonneau jpinsonneau added the ok-to-test To set manually when a PR is safe to test. Triggers image build on PR. label Jan 8, 2026
@github-actions
Copy link

github-actions bot commented Jan 8, 2026

New image:
quay.io/netobserv/network-observability-console-plugin:a08ad5d

It will expire after two weeks.

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

USER=netobserv VERSION=a08ad5d make set-plugin-image

@github-actions github-actions bot removed the ok-to-test To set manually when a PR is safe to test. Triggers image build on PR. label Jan 12, 2026
Copy link
Contributor

@leandroberetta leandroberetta left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jpinsonneau thanks for the PR, looks good to me although I have some small comments to discuss.

render() {
const { size, className, style } = this.props;
const sizeValue = typeof size === 'number' ? size : parseFloat(size as string) || 18;
return <IconWrapper icon={GrGateway} size={sizeValue} className={className} style={style} />;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The gateway icon changed, I think I like the previous one, is it possible to use the patternfly one?. Also, it seems to have a black background:

Image

Previous one was GlobeRouteIcon:

Image

Also, is that the icon for deployments or should be different? I think we can look for a similar one to the existing today? What do you thinnk?

Copy link
Contributor Author

@jpinsonneau jpinsonneau Jan 12, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know why it's so dark in your screen. It was supposed to render like that:
image

Anyways if you prefer the previous icon I can rollback for sure 👌

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@codecov
Copy link

codecov bot commented Jan 12, 2026

Codecov Report

❌ Patch coverage is 29.50820% with 129 lines in your changes missing coverage. Please review.
✅ Project coverage is 52.48%. Comparing base (e5a439c) to head (0881543).
⚠️ Report is 7 commits behind head on main.

Files with missing lines Patch % Lines
web/src/components/icons/kubernetes-icons.tsx 10.00% 90 Missing ⚠️
pkg/handler/lokiclientmock/loki_client_mock.go 0.00% 24 Missing ⚠️
web/src/components/icons/react-icons.tsx 75.00% 7 Missing ⚠️
...ents/tabs/netflow-topology/2d/styles/styleNode.tsx 46.15% 7 Missing ⚠️
web/src/components/dropdowns/match-dropdown.tsx 50.00% 1 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1189      +/-   ##
==========================================
- Coverage   52.95%   52.48%   -0.48%     
==========================================
  Files         209      214       +5     
  Lines       10950    11154     +204     
  Branches     1391     1413      +22     
==========================================
+ Hits         5799     5854      +55     
- Misses       4602     4749     +147     
- Partials      549      551       +2     
Flag Coverage Δ
uitests 54.58% <33.96%> (-0.37%) ⬇️
unittests 46.47% <0.00%> (-0.81%) ⬇️

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

Files with missing lines Coverage Δ
web/src/components/drawer/record/record-field.tsx 49.73% <100.00%> (+0.26%) ⬆️
web/src/components/icons/index.ts 100.00% <100.00%> (ø)
web/src/components/icons/react-icons-wrapper.tsx 100.00% <100.00%> (ø)
...ents/query-summary/flows-query-summary-content.tsx 100.00% <100.00%> (ø)
...c/components/query-summary/flows-query-summary.tsx 80.00% <ø> (ø)
...ts/query-summary/metrics-query-summary-content.tsx 61.53% <100.00%> (+0.60%) ⬆️
...components/query-summary/metrics-query-summary.tsx 100.00% <ø> (ø)
...nts/tabs/netflow-topology/2d/styles/styleGroup.tsx 45.45% <100.00%> (ø)
...b/src/components/toolbar/filters/filters-chips.tsx 48.81% <100.00%> (+0.40%) ⬆️
...b/src/components/toolbar/filters/quick-filters.tsx 19.04% <100.00%> (ø)
... and 5 more

... and 11 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link
Contributor

@leandroberetta leandroberetta left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@Amoghrd
Copy link
Member

Amoghrd commented Jan 13, 2026

/ok-to-test

@openshift-ci openshift-ci bot added the ok-to-test To set manually when a PR is safe to test. Triggers image build on PR. label Jan 13, 2026
@github-actions
Copy link

New image:
quay.io/netobserv/network-observability-console-plugin:d3f82ca

It will expire after two weeks.

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

USER=netobserv VERSION=d3f82ca make set-plugin-image

@Amoghrd
Copy link
Member

Amoghrd commented Jan 13, 2026

Comments:

  • The summary fields are not in the same line
Screenshot 2026-01-13 at 2 41 20 PM
  • The icon for namespace can be something else other than dotted boxes or is that the norm?

It also would be good for the icons to be reviewed all members to see if they are apt/look good

@Amoghrd
Copy link
Member

Amoghrd commented Jan 13, 2026

Also tested for network and VM icons, both are still ?
Screenshot 2026-01-13 at 4 48 26 PM

Screenshot 2026-01-13 at 4 49 20 PM

@jpinsonneau
Copy link
Contributor Author

Comments:

  • The summary fields are not in the same line
Screenshot 2026-01-13 at 2 41 20 PM

Sure, let me fix that

  • The icon for namespace can be something else other than dotted boxes or is that the norm?

It also would be good for the icons to be reviewed all members to see if they are apt/look good

It could be anything we want. I just took it from the svgs in https://github.com/kubernetes/community/tree/master/icons/svg/resources/unlabeled

Also tested for network and VM icons, both are still ? Screenshot 2026-01-13 at 4 48 26 PM

Screenshot 2026-01-13 at 4 49 20 PM

Yeah I'm not sure why I didn't found those implemented already 🤔
I thought it was ! I'll fix that in the same PR

Thanks for your feedback !

@openshift-ci openshift-ci bot removed the lgtm label Jan 14, 2026
@openshift-ci
Copy link

openshift-ci bot commented Jan 14, 2026

New changes are detected. LGTM label has been removed.

@github-actions github-actions bot removed the ok-to-test To set manually when a PR is safe to test. Triggers image build on PR. label Jan 14, 2026
@jpinsonneau
Copy link
Contributor Author

Added the missing icons and fixed alignment: 3fc9829

@jpinsonneau
Copy link
Contributor Author

jpinsonneau commented Jan 14, 2026

Added the missing icons and fixed alignment: 0881543

image image image image image image

Also updated the mocks so everybody can have a quick look 😸

@Amoghrd
Copy link
Member

Amoghrd commented Jan 14, 2026

/ok-to-test

@openshift-ci openshift-ci bot added the ok-to-test To set manually when a PR is safe to test. Triggers image build on PR. label Jan 14, 2026
@github-actions
Copy link

New image:
quay.io/netobserv/network-observability-console-plugin:8741167

It will expire after two weeks.

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

USER=netobserv VERSION=8741167 make set-plugin-image

@Amoghrd
Copy link
Member

Amoghrd commented Jan 14, 2026

Alignment looks good now. VM's and network have icons too now.
I added a comment on slack about having different icons for some fields though

@jpinsonneau
Copy link
Contributor Author

Alignment looks good now. VM's and network have icons too now. I added a comment on slack about having different icons for some fields though

yeah let's grab more feedback and merge when we agree. Thanks @Amoghrd !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

jira/valid-reference ok-to-test To set manually when a PR is safe to test. Triggers image build on PR.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants