Repository navigation
OCPNETUI-114: Add network topology view - #561
openshift-merge-bot[bot] merged 1 commit into
Conversation
|
Pipeline controller notification For optional jobs, comment This repository is configured in: LGTM mode |
|
@pcbailey: This pull request references OCPNETUI-114 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 "5.1.0" version, but no target version was set. DetailsIn 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. |
|
Skipping CI for Draft Pull Request. |
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
|
1959456 to
6184f16
Compare
1afddf7 to
fd4bea1
Compare
5b3061b to
94fc7ad
Compare
|
/lgtm |
|
Scheduling required tests: |
94fc7ad to
9cbefc2
Compare
|
/lgtm |
|
Scheduling required tests: |
9cbefc2 to
abfb6d6
Compare
abfb6d6 to
b3da163
Compare
b3da163 to
a163c7d
Compare
|
/retest |
a163c7d to
b1ce4f9
Compare
|
/lgtm |
|
Scheduling required tests: |
| " See more details in: <3></3>.": " Ver más detalles en: <3></3>.", | ||
| "(all nodes): ": "(todos los nodos): ", | ||
| "{{count}} annotation_one": "{{count}} anotación", | ||
| " See more details in: <3></3>": " See more details in: <3></3>", |
There was a problem hiding this comment.
it seems that non-English translations got overridden. Please revert.
| "@patternfly/react-styles": "6.6.1", | ||
| "@patternfly/react-table": "6.6.2", | ||
| "@patternfly/react-tokens": "6.6.1", | ||
| "@patternfly/react-topology": "^6.6.0", |
There was a problem hiding this comment.
In order to match the versions used in the Console we need to pin the version here..
You can also run npm run shared-modules:sync -- release-5.1 which should automatically sync the correct versions.
| return false; | ||
| } | ||
|
|
||
| if (isClusterUDN(udn)) { |
There was a problem hiding this comment.
to be fully accurate we need to check namespaceSelector
| */ | ||
| export const podUsesUDN = (pod: IoK8sApiCoreV1Pod, udn: UDNResource): boolean => { | ||
| const udnNamespace = getNamespace(udn); | ||
| const nadCandidates = getUDNNADNameCandidates(udn); |
There was a problem hiding this comment.
is it safe to assume certain naming patterns as done in getUDNNADNameCandidates ?
| /** | ||
| * Check if a Pod uses a UDN or ClusterUDN | ||
| */ | ||
| export const podUsesUDN = (pod: IoK8sApiCoreV1Pod, udn: UDNResource): boolean => { |
There was a problem hiding this comment.
how do we handle primary UDN path? do we need similar logic as in vmUsesUDN()?
| // For namespace-scoped primary UDNs, VM must be in the same namespace | ||
| if (udnNamespace && vmNamespace === udnNamespace) { | ||
| // Check if VM has a pod network (which would use the primary UDN) | ||
| const hasPodNetwork = networks.some((network) => Boolean(network.pod)); |
There was a problem hiding this comment.
as per work-in-progress docs the use of autoattached pod network with UDN is discouraged but not impossible. At minimum we should test if the case is handled gracefully.
| export const vmHasSecondaryNetworks = (vm: V1VirtualMachine): boolean => { | ||
| // TODO Check logic | ||
| // const networks = getNetworks(vm); | ||
| // return networks.some((network) => network.multus?.networkName); |
There was a problem hiding this comment.
note that although exotic it's possible to have a multus network as the default pod network
a795b40 to
2f881b0
Compare
rszwajko
left a comment
There was a problem hiding this comment.
Thank you for addressing the issue with translations. We can discuss other points in follow-ups.
|
Scheduling required tests: |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: pcbailey, rszwajko The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
2f881b0 to
1434f71
Compare
|
/lgtm |
|
Scheduling required tests: |
|
@pcbailey: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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. |
This PR adds the initial network configuration topology view.
Jira: https://redhat.atlassian.net/browse/OCPNETUI-114
Demo:
initial-topology-view--2026-10-23-11-38-37.mp4