OU-594: [Incidents] UI is not embedded in the Alerting section

[zhuje]

JIRA

https://issues.redhat.com/browse/OU-594

Notes

This PR will only work if the Cluster Monitoring Operator and Monitoring Plugin are installed and viewed in the Administrator perspective.

Screen Capture

Screen.Recording.2025-07-16.at.1.11.54.AM.mov

[openshift-ci-robot]

@zhuje: This pull request references OU-594 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 bug to target the "4.20.0" version, but no target version was set.

In response to this:

JIRA

https://issues.redhat.com/browse/OU-594

Screen Capture

Screen.Recording.2025-07-16.at.12.26.29.AM.mov

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]

@zhuje: This pull request references OU-594 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 bug to target the "4.20.0" version, but no target version was set.

In response to this:

JIRA

https://issues.redhat.com/browse/OU-594

Screen Capture

Screen.Recording.2025-07-16.at.1.11.54.AM.mov

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.

[jgbernalp]

@zhuje @etmurasaki we need to test this also when there is no MCO in the cluster.

[zhuje]

/hold

Hold until this PR is merged NO-JIRA: Convert incidents to typescript then rebase.

[openshift-ci-robot]

@zhuje: This pull request references OU-594 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 bug to target the "4.20.0" version, but no target version was set.

In response to this:

JIRA

https://issues.redhat.com/browse/OU-594

Notes

This PR will only work if the Cluster Monitoring Operator and Monitoring Plugin are installed and viewed in the Administrator perspective.

Screen Capture

Screen.Recording.2025-07-16.at.1.11.54.AM.mov

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.

[zhuje]

/unhold

[PeterYurkovich]

/lgtm

[etmurasaki]

/label qe-approved
tested after Peter's fixes on:

• Virtualization was showing Incidents tab and it shouldn't
• Alerting pages on Virtualization, ACM were not working correctly
  It is working fine

[openshift-ci-robot]

@zhuje: This pull request references OU-594 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 bug to target the "4.20.0" version, but no target version was set.

In response to this:

JIRA

https://issues.redhat.com/browse/OU-594

Notes

This PR will only work if the Cluster Monitoring Operator and Monitoring Plugin are installed and viewed in the Administrator perspective.

Screen Capture

Screen.Recording.2025-07-16.at.1.11.54.AM.mov

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.

[PeterYurkovich]

/label ux-approved
This change was driven by UX

[openshift-ci]

@zhuje: all tests passed!

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

[jgbernalp]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jgbernalp, PeterYurkovich, zhuje

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [PeterYurkovich,jgbernalp,zhuje]

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

[jgbernalp]

/cherry-pick release-coo-0.5

[openshift-cherrypick-robot]

@jgbernalp: #465 failed to apply on top of branch "release-coo-0.5":

Applying: use HoritzontalNav for Observe > Alerting Tabs so we can inject incidents
Using index info to reconstruct a base tree...
M	web/package-lock.json
M	web/package.json
M	web/src/components/MetricsPage.tsx
Falling back to patching base and 3-way merge...
Auto-merging web/src/components/MetricsPage.tsx
Auto-merging web/package.json
Auto-merging web/package-lock.json
CONFLICT (content): Merge conflict in web/package-lock.json
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 use HoritzontalNav for Observe > Alerting Tabs so we can inject incidents

In response to this:

/cherry-pick release-coo-0.5

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.

[jgbernalp]

/cherry-pick release-4.19

[openshift-cherrypick-robot]

@jgbernalp: #465 failed to apply on top of branch "release-4.19":

Applying: use HoritzontalNav for Observe > Alerting Tabs so we can inject incidents
Using index info to reconstruct a base tree...
M	web/package-lock.json
M	web/package.json
M	web/src/components/Incidents/IncidentsPage.jsx
Falling back to patching base and 3-way merge...
Auto-merging web/src/components/Incidents/IncidentsPage.jsx
CONFLICT (content): Merge conflict in web/src/components/Incidents/IncidentsPage.jsx
Auto-merging web/package.json
Auto-merging web/package-lock.json
CONFLICT (content): Merge conflict in web/package-lock.json
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 use HoritzontalNav for Observe > Alerting Tabs so we can inject incidents

In response to this:

/cherry-pick release-4.19

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.

[openshift-bot]

[ART PR BUILD NOTIFIER]

Distgit: monitoring-plugin
This PR has been included in build monitoring-plugin-container-v4.20.0-202507230546.p0.g087dfd7.assembly.stream.el9.
All builds following this will include this PR.