OCPBUGS-47535: use pf v5 variables and table component

[jgbernalp]

This PR:

• Replaces all usages of patternfly variables and classes of V4 with V5
• Updates the patternfly table from V4 to V5
• Upgrades patternfly react table and charts packages

Smoke tested with openshift/console#14615

[openshift-ci-robot]

@jgbernalp: This pull request references Jira Issue OCPBUGS-47535, which is invalid:

• expected the bug to target the "4.19.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

This PR:

• Replaces all usages of patternfly V4 with V5
• Updates the patternfly table from V4 to V5
• Upgrades patternfly react table and charts packages

Smoke tested with openshift/console#14615

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]

/jira refresh

[openshift-ci-robot]

@jgbernalp: This pull request references Jira Issue OCPBUGS-47535, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.19.0) matches configured target version for branch (4.19.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @juzhao

In response to this:

This PR:

• Replaces all usages of patternfly variables and classes of V4 with V5
• Updates the patternfly table from V4 to V5
• Upgrades patternfly react table and charts packages

Smoke tested with openshift/console#14615

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]

@jgbernalp: This pull request references Jira Issue OCPBUGS-47535, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.19.0) matches configured target version for branch (4.19.0)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @juzhao

In response to this:

/jira refresh

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]

@jgbernalp This PR is going to run into some conflicts with both #306 and #304. We should decide which order we want to merge the items in (I believe this PR can come first) and then rebase the others PR's on top of that one.

Not really relevant, but this situation would be a lovely place for using something like PR stacking

[jgbernalp]

/retest

[jgbernalp]

/hold until we cut the release branch for COO as this will support older OCP versions

[PeterYurkovich]

/lgtm

[jgbernalp]

/retest

[PeterYurkovich]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

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

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]

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

[jgbernalp]

/retest

[PeterYurkovich]

/retest

[juzhao]

/retest-required

[openshift-ci]

@jgbernalp: 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.

[juzhao]

tested with PR, issue is fixed, see bug comment
/label qe-approved

[openshift-ci-robot]

@jgbernalp: This pull request references Jira Issue OCPBUGS-47535, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.19.0) matches configured target version for branch (4.19.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @juzhao

In response to this:

This PR:

• Replaces all usages of patternfly variables and classes of V4 with V5
• Updates the patternfly table from V4 to V5
• Upgrades patternfly react table and charts packages

Smoke tested with openshift/console#14615

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]

/unhold

[openshift-ci-robot]

@jgbernalp: Jira Issue OCPBUGS-47535: All pull requests linked via external trackers have merged:

• openshift/monitoring-plugin#307

Jira Issue OCPBUGS-47535 has been moved to the MODIFIED state.

In response to this:

This PR:

• Replaces all usages of patternfly variables and classes of V4 with V5
• Updates the patternfly table from V4 to V5
• Upgrades patternfly react table and charts packages

Smoke tested with openshift/console#14615

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-bot]

[ART PR BUILD NOTIFIER]

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